[jira] Closed: (DAYTRADER-53) Remove EJB 2.1 components from Daytrader 2.0

["Christopher James Blythe (JIRA)" <de...@geronimo.apache.org>]

     [ https://issues.apache.org/jira/browse/DAYTRADER-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher James Blythe closed DAYTRADER-53.
---------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0
         Assignee: Christopher James Blythe

> Remove EJB 2.1 components from Daytrader 2.0
> --------------------------------------------
>
>                 Key: DAYTRADER-53
>                 URL: https://issues.apache.org/jira/browse/DAYTRADER-53
>             Project: DayTrader
>          Issue Type: Task
>          Components: EJB Tier, J2EE Application Clients, Web Tier
>    Affects Versions: 2.0
>            Reporter: Christopher James Blythe
>            Assignee: Christopher James Blythe
>             Fix For: 2.0
>
>
> A while back I started some discussion around whether or not the old EJB 2.1 components should continue to be maintained in DayTrader 2.0. Their are arguments for and against; however, I still feel removing the legacy components is the best option.
> The only argument for leaving the EJB 2.1 components in is that you can easily switch between 2.1 and 3.0 without restarting the server or installing another app. In my opinion, this is far out-weighed by the cons which include the following factors...
> - complexity
> - maintainability
> - portability
> Removing the EJB 2.1 components simplifies the application considerably since two versions of the components no longer have to be maintained in the same application. Furthermore, it highlights the "usability" factor that was a major focus for EJB 3. For instance, if I remove the 2.1 components, I no longer need to place anything in the ejb-jar.xml DD. That's a far cry from the EJB 2.1 days...
> The EJB 2.1 components should be maintained for comparison purposes; however, they should reside in DayTrader 1.2.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.