geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher James Blythe (JIRA)" <>
Subject [jira] Created: (DAYTRADER-47) Add full EJB 3 runtime mode (including EJB 3 based stateless session bean and MDBs)
Date Tue, 31 Jul 2007 02:55:52 GMT
Add full EJB 3 runtime mode (including EJB 3 based stateless session bean and MDBs)

                 Key: DAYTRADER-47
             Project: DayTrader
          Issue Type: New Feature
          Components: EJB Tier
    Affects Versions: 2.0
            Reporter: Christopher James Blythe
             Fix For: 2.0

This code was committed into trunk in revision 559535 on 7/25/07

The following information was posted to the dev list regarding the changes. Since this basically
replaces the existing TradeJPA implementation, I think  it should be removed (will address
this in another JIRA).  


As it currently stands, DayTrader 2.0 does not provide what I would consider a viable showcase
application for Java EE 5 technology. The JPA mode that was added uses EJB3/JPA based entities;
however, the mode still lacks a few key elements...

- EJB 3 based stateless session bean providing the business logic (current impl still uses
EJB 2.1 session beans)
- EJB 3 based MDBs for Quote streamer and async order processing
- Improvements to JPA mode to ensure data consistency and improve performance

I have added a new EJB3 runtime mode that exposes the following...
- TradeSLSBBean (new EJB 3 based session bean for business logic)
- DTBroker3MDB (new EJB 3 based MDB for async order processing)
- DTStreamer3MDB (new EJB 3 based MDB for quote streamer)

I have made these updates and plan to commit them shortly, I have left the existing TradeJPA
bean as is, in addition to the legacy Direct and EJB 2.1 modes. I have pulled yesterday's
build of Geronimo 2.0 and verified that the new EJB3 mode functionally works along with the
legacy modes. The next step is load testing, so stay tuned...



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

View raw message