Beginner |
 |
Joined: Thu Sep 16, 2004 8:14 pm Posts: 27
|
I have a group of different webapps that are running in the same instance of JBoss and Tomcat. They all use the same business objects and look at the same database. I'm wondering what tried and true practices there are for deploying a .jar file of Hibernated business objects in such a way that many webapps deployed within the same Tomcat instance can make use of that same jar. What I'm trying to avoid is classloader weirdness that might cause different webapps to see stale views of the database. I'm thinking that if I included the .class files for those business objects in each webapp things would behave like multiple Java applications on different machines accessing a shared database.
Is this something that I even need to watch out for, or is it a non-issue?
Note that these webapps are not on virtual hosts. There may be some need for that in the future. Does that complicate the situation in any way?
Thanks,
-M@
|
|