You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Christopher James Blythe (JIRA)" <de...@geronimo.apache.org> on 2007/08/02 15:40:52 UTC

[jira] Closed: (DAYTRADER-48) Remove TradeJPA mode (replaced by full EJB 3 mode)

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

Christopher James Blythe closed DAYTRADER-48.
---------------------------------------------

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

Completed removal of TradeJPA

> Remove TradeJPA mode (replaced by full EJB 3 mode)
> --------------------------------------------------
>
>                 Key: DAYTRADER-48
>                 URL: https://issues.apache.org/jira/browse/DAYTRADER-48
>             Project: DayTrader
>          Issue Type: Task
>          Components: EJB Tier
>    Affects Versions: 2.0
>            Reporter: Christopher James Blythe
>            Assignee: Christopher James Blythe
>            Priority: Minor
>             Fix For: 2.0
>
>
> The EJB 3 code that was recently committed provides a full EJB 3 implementation of the DayTrader workload using EJB 3 entities, sessions and MDBs. This improves upon the original Trade JPA mode (from which the business logic was originally ported) that used EJB 2.1 based session and MDBs. Furthermore, minor modifications were made to improve data consistency and performance (via eager/lazy loading of the entities).
> I see no real need for the original JPA mode to stick around and feel it should be removed.
> Any objections?

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