Just sent out an email about that... I think I may be leaning towards removing it ASAP. Let me know what you think...
Two additional changes need to be made once I drop in the code.
- remove the old TradeJPA
- add another Session-to-Direct mode that uses EJB 3.0 sessions
These should be fairly simple.
Most excellent. We should probably talk about deprecating the EJB
2.1 stuff in DT 2.1 and leave it behind. For 2.0 using it to allow a
baseline for transition makes sense. Work for you ?
On Jul 25, 2007, at 11:59 AM, Christopher Blythe wrote:
> 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
> 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
> "I say never be complete, I say stop being perfect, I say let...
> lets evolve, let the chips fall where they may." - Tyler Durden