David, Thanks for your suggestions. I agree with you that it was an extraordinarily intrusive adaptation--that's why I'm trying to find something better right now. :-)
I'm not sure about the external vendor plans that you mentioned. We are running Weblogic 8.1 SP3 which only supports J2EE 1.3, so I'm not sure if that's an option; I'll have to do some research. And, unfortunately, packaging the client applications into the EAR isn't possible, as we have many different clients accessing those EJBs (some of which are written by other development teams entirely). Jason -----Original Message----- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Fri 4/29/2005 5:13 PM To: Maven Users List Subject: Re: Deployment-specific builds: parameters? subprojects? Renaming your ejbs seems like an extraordinarily intrusive adaptation to make to deploy more than one application instance on a server instance. Are you sure there aren't less intrusive approaches available? Some simple examples... If your app server supports j2ee application clients and your clients can be written as app clients then the app server should take care of hooking up ejb-links from the app client to the ejbs in the same ear. J2ee 1.4 app servers support external vendor plans. In Geronimo, the only one I am familiar with, you can "name" the entire application in the vendor application plan (this would let you deploy several instances of the app on the same server) and you can specify "external" jndi names for ejbs (in case you can't use an app client). This would let you use the same application for all instances, only substituting some names in the vendor plan. Does your app server offer anything like this? thanks david jencks On Apr 29, 2005, at 1:03 PM, Jason Horne wrote: > They have the same structure, yes, but the data in them might be > different, and access to the databases doesn't happen exclusively > through my EJBs. > > The EJBs in question must be named differently because: > > 1) The EJBs in question handle one aspect of an ordering system. > There are other parts of the ordering system that interact with both > these EJBs and other tables in the database, through different means. > The client application needs to be certain that data being written > through our EJBs is going to the same database as the other database > access methods, so they simply select the EJBs they want by name. > > 2) As I mentioned, we may need to deploy the same EJBs more than once > in the same application server, for different database instances. For > example, we have multiple databases used for "development". Different > client applications use different development databases, yet all of my > EJBs are deployed on our development-level application server. If the > EJBs aren't named differently, there will be JNDI collisions, and the > world will asplode. > > Jason > > > -----Original Message----- > From: Arik Kfir [mailto:[EMAIL PROTECTED] > Sent: Friday, April 29, 2005 4:50 PM > To: Maven Users List > Subject: Re: Deployment-specific builds: parameters? subprojects? > > I still don't understand. Do the databases share the same structure, > and the difference being one is intended for production and one for > development? > > If so, why name the EJB differently? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
