Are you saying that this works for you?

I tried to do the same thing and it didn't work...

Two EARs, each with own Web contexts, similar ejb-jars, same class names,
same ejb-names, different JNDI names.

Hunter

> From: Dan Christopherson <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Fri, 17 May 2002 10:12:50 -0500
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] Does JBoss3 have Problems Deploying Similar ejb-
> jars in Different EARs
> 
> I've deployed test and production versions of an application on the same
> jboss instance. They're differentiated by the context path of the web
> app and the JNDI names of the ejbs. I need to have different deployment
> descriptors, of course, but I do anyway because security role names and
> datasources change. The advantage over running 2 instances: Apache proxy
> pass rules are simpler, less memory used.
> 
> -danch


_______________________________________________________________

Hundreds of nodes, one monster rendering program.
Now that�s a super model! Visit http://clustering.foundries.sf.net/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to