So if I have two different versions of my application, I have to use a totally different packaging mechanism to get them both to deploy?
Right now, this is what I have: EAR1 EAR2 Both contain *similar* ejb-jars. The ejb-jars contain classes with the same names and similar packaging, but different contents. Both EARs use different ejb-names, different JNDI names, and different web app contexts. They are still conflicting, as JBoss only sees the first copy of the class file that is deployed. So, just to be crystal clear, my choices are: 1. repackage ejb-jar, use different names for the classes, etc... 2. run multiple copies of JBoss I don't like the first option since the ejb-jars are almost the same, and one is just a CVS branch off the trunk. This would make diffing between the two branches really hard. >From the recent discussion on the dev list, running multiple copies seems to still be a little problematic? Anyway, this is something I'm going to have to do often since customers request modifications to our standard code-base all the time. Each mod version will require another instance of JBoss? Was it Dain that suggested that there be a config switch for people who don't need visibility between deployed EARs? I can see how that feature is powerful and useful for some, I think making that optional would be a great thing, since for people like me (and ISPs that could easily run into the same problem), this is a tough problem to solve. Hunter > From: David Jencks <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Date: Thu, 16 May 2002 19:42:38 -0400 > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Does JBoss3 have Problems Deploying Similar ejb-jars > in Different EARs > > On 2002.05.16 19:05:43 -0400 Hunter Hillegas wrote: >> Whoah... Really? > > yup >> >> So I can't have two ejb-jars with classes that are named the same, in >> different ears? >> >> Hmmmm... >> >> We have a content management system with EJBs that we need to deploy in >> several different customer instance EARs. Are you saying we can't do that >> without changing the classnames or packaging? >> >> For some reason I thought that each deployed EAR had its own namespace >> and >> you could do this... >> >> Did I misunderstand you? > > nope. > > You can have lots of copies of the same ejb class deployed under different > ejb name and jndi names. Just be sure to only deploy one copy of the > class. You might want to deploy the classes before any of the dd's, and > separate all the dd's from any classes. > > You can't have 2 versions of the same class. They will interfere, as you > discovered. > > Basically we decided that we would initially support visibility between > deployment packages with hot-redeploy, since this is a feature previously > unavailable anywhere as far as I know. Once this is thoroughly stable and > well tested we will consider whether it is really advisable to have several > of these sets of UnifiedClassLoaders at once in one vm. For now, you > should run several jboss servers in different vms. > > david jencks > >> >> Hunter >> >>> From: David Jencks <[EMAIL PROTECTED]> >>> Reply-To: [EMAIL PROTECTED] >>> Date: Thu, 16 May 2002 18:59:18 -0400 >>> To: [EMAIL PROTECTED] >>> Subject: Re: [JBoss-user] Does JBoss3 have Problems Deploying Similar >> ejb-jars >>> in Different EARs >>> >>> JBoss 3 doesnt' support having 2 classes with the same name, no matter >> how >>> you package them. It does support classes in one ear seeing the >> classes in >>> the other ear(s). >>> >>> david jencks >>> >>> On 2002.05.16 18:03:07 -0400 Hunter Hillegas wrote: >>>> I'm trying to get this damn EAR to deploy and I started wondering if >>>> JBoss3 >>>> has trouble deploying an EAR if another EAR has a similar ejb-jar... >>>> >>>> Basically I have two versions of an ejb-jar. One has a bean with one >>>> extra >>>> CMP variable. >>>> >>>> The first archive deploys just fine. The second one deploys okay if >> the >>>> first is not deployed. If the first one is deployed and I try to >> deploy >>>> the >>>> second then I get a message that the bean class doesn't contain an >>>> accessor >>>> for the extra variable that exists in the second ejb-jar... >>>> >>>> Any ideas? >>>> >>>> Hunter >>>> >>>> >>>> _______________________________________________________________ >>>> >>>> Have big pipes? SourceForge.net is looking for download mirrors. We >>>> supply >>>> the hardware. You get the recognition. Email Us: >>>> [EMAIL PROTECTED] >>>> _______________________________________________ >>>> JBoss-user mailing list >>>> [EMAIL PROTECTED] >>>> https://lists.sourceforge.net/lists/listinfo/jboss-user >>>> >>>> >>> >>> _______________________________________________________________ >>> >>> Have big pipes? SourceForge.net is looking for download mirrors. We >> supply >>> the hardware. You get the recognition. Email Us: >> [EMAIL PROTECTED] >>> _______________________________________________ >>> JBoss-user mailing list >>> [EMAIL PROTECTED] >>> https://lists.sourceforge.net/lists/listinfo/jboss-user >> >> >> _______________________________________________________________ >> >> Have big pipes? SourceForge.net is looking for download mirrors. We >> supply >> the hardware. You get the recognition. Email Us: >> [EMAIL PROTECTED] >> _______________________________________________ >> JBoss-user mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/jboss-user >> >> > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
