Hello all,

I have a question about 66.html it was stated that



Is this still the case? Do we need to still place the common classes into a sperate jar file?

Thanks,
Jason

I certainly am doing it that way, but it depends on your deployment configuration. I remember from your previous posts that you are using the Hibernate MBean, Tomcat and MySql. Are you using WARs, EARs?


Sherman

currently i am just using pojo's in a war.
i want to get the basics right before i move on to ejb's

also i want to set up some junit tests for hibernate do you know of any pitfalls to watch out for?

thank you very much for the help, schemaexport works perfectly now

regards,

jason

Glad to hear that SchemaExport is working for you.


The Hibernate POJO classes need to be accessible by the MBean SAR and your WAR. As indicated in the documentation on the Hibernate web site, I have a separate JAR containing those classes in my EAR, and refer to that JAR in my application.xml. You could test having the WAR and the MBean SAR with the classes in it just in the deploy directory, and see whether that flies.


In the junit side, I do not deal directly with Hibernate testing, but instead use httpunit to drive traffic to my application web site, which in turn does Hibernate work. If you are testing something outside of your app, there are plenty of examples in the Hibernate source distribution.


Cheers,


Sherman

I did get jUnit to work, I modified the TestCase in the distribution for use. Works like a dream, I would check out jUnit saves a lot of time before pushing code up for stress testing.

thanks for the help

jason