geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevan Miller <>
Subject Re: What to do with legacy EJB 2.1 code in DayTrader?
Date Tue, 31 Jul 2007 12:01:41 GMT

On Jul 30, 2007, at 10:47 AM, Christopher Blythe wrote:

> I like having the 2.1 code around as well for the same reasons you  
> stated. I just don't like the idea of having the two  
> implementations inter-mingled in the same ear/jar. It makes  
> DayTrader's usefulness as a code sample for developers a lot harder  
> to swallow. I also have a hard time believing that there are going  
> to be a lot of production applications out there that use both EJB  
> 2.1 and 3.0 components in the same package.
> So, my original thinking was to, use DT 1.2 as the J2EE 1.4 based  
> sample and DT 2.0 as the EE 5 based sample.
> Another option I just thought of is to refactor the packaging such  
> that two ejb jar files can be created, one for the EJB 2.1 legacy  
> code and another for the new EJB 3.0 components. The pom files  
> could then be modified to create two ear files.
> Thoughts?

 From a usage perspective, it's great to have a single ear with  
multiple, selectable modes. If that's impractical, I'm ok with  
multiple ears.


View raw message