I had something like this working at some point but it has been awhile. It seems I had problems because of the Universal Class Loader. There is a config somewhere that allows you to turn this off, and then each ear will have its own class loader and therefore 'see' the appropriate classes.
Like I said, I had it working, then it stopped. It occured to me later that it stopped about the time I upgraded jboss. I decided I needed to go verify the old config (that I had turned off the Univeral Class Loader) but I didn't have the requirement anymore, so I never got around to verifying this. Hopefully someone with more knowledge of such things can verify this and tell you where the config is, or let me know I dreamed the whole thing up, so I don't go that direction when the requirement pops up again.... BTW, Xdoclet will create util classes that handle the getting of interfaces for you. If you use the util class, it is already using the correct jndi name. I think you don't need #2. Alex -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stefan Groschupf Sent: Wednesday, October 15, 2003 1:04 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] ear & jndi & different databases. Hi, Please please help me!!! Since 3 days I try non stop to get 2 instances of the same project running in one jboss. I scan all web pages, forums, documentations about that and I’m sure the solution is very close, but I have a mistake I could not find. 1.) I use in each ejb dynamic xdoclet generated local jndi names. * @ejb.bean local-jndi-name="${site}/org.weta.tm.document.entity.thesaurus.Term" * name="Term" * primkey-field="uniqueSequence" * type="CMP" * cmp-version = "2.x" * view-type="local" * schema = "Term" 2.) I have a script that update <jndi-name>Term</jndi-name> to <jndi-name>Term_myName</jndi-name> 3.) My projects a separated in different ears 4.) I have 2 datasource.xml file in my deploy folder with different datasource names. 5.) I had setup the different datasources in jbosscmp-jdbc.xml Only the ejb names are the same, but as I hear that is not important. Anyways both projects are well deployed, without any exception but the second deployed project use the database of the first project. Looks like it use the ejbs of the first deployed project. Please can someone give me a hint how to solve this problem?! Thanks a lot!! Stefan ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
