From: <ste...@jb...> - 2005-07-28 04:16:26
|
So coded up this solution and it seems to be working fine. However, I did run into one thing I found initially puzzling, but which might actually be problematic later. So first I need to point out that I am running my initial tests using a locally modified HARDeployer, which simply never injects a "HarUrl". Maybe what I am seeing is a result of that, and all will be good once I switch over to allowing the other deployers to pick this up. Anyway... My testsuite deployment is an ear that looks like: | test.ear/ | test-ejb.jar | test.har | So given this, the classpath entries my code is checking are: 1) the ear itself 2) the har 3) the har file's hibernate-service.xml 4) the ejb-jar The potentially problematic piece is say that I have two SARs bundled into the same top-level deployable, each defining a Hibernate MBean. So basically, each of the two session factories will know about all the classes from his SAR but also about all the classes from the other SAR. Envision a scenario where an enterprise app needs to talk to two different databases. In Hibernate that explicitly means two seperate session factories, which means I'll need two different mbeans defined. The problem is that there is no way to segment which portions of deployment pertain to DB1 access vs which pertain to DB2 access, because it's just a classpath. Thoughts? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886973#3886973 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886973 |