geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Blythe" <>
Subject Re: [jira] Closed: (DAYTRADER-16) JPA mode
Date Mon, 30 Oct 2006 23:09:19 GMT

Read through your notes late last week concerning the JPA mode additions and
figured I would add my comments here. We definitely need to add support for
JPA and EJB 3.0 into Daytrader; however, we also need to maintain the
existing JDBC and EJB 2.1 operating modes in some way shape of form for
functional/performance regression testing purposes.

What I would really like to see are continued enhancements to clean-up
Daytrader in it's existing form in the 1.2.X release stream. This would
include things like the SSB to JDBC mode that I submitted in DAYTRADER-15,
the Dojo interface in DAYTRADER-17, etc. This would leave Daytrader 1.2.X as
an excellent testcase for J2EE 1.4 functionality.

For the JPA, EJB 3.0 and other EE 5 related stuff, I feel like these should
go into a new version of Daytrader (perhaps Daytrader 2.0) where we can
completely replace the existing Direct and EJB modes with their JPA and EJB
3.0 equivalents. It would also be nice to add some additional complexity to
the Daytrader data model at this time. Just a few ideas that have been
floating around in my head include...

- batch order processing
- quote price and stock index histories
- configurable buy/sell orders

I'm not sure how this aligns with the Geronimo release plan in terms EE 5
support and Daytrader/Geronimo versioning.

Another idea I've been toying with is a pluggable model for the persistence
layer that would allow us to run Daytrader in a larger number of
configurations and environments. Currently, the Direct mode impl is packaged
inside the ejb jar. Consequently, you need a full EJB container just to run
Direct mode even though you could theoretically run Direct mode on base
Tomcat server. Anyway, I was thinking of something like...

- re-organizing some of the common code (data beans, config, etc.) into a
util jar
- use some form of factory pattern for detecting the available persistence
mechanisms (aka. JDBC, Session to JDBC, Session to Entity, JPA, EJB 3.0,
- provide separate ejb jars for each of these impls
- depending on which ejb jar is loaded with the application, provide the
available runtime option (use JNDI lookups to determine which modes are

The only reason I mention this here is because we could use something like
this to maintain the existing runtime modes and introduce the new runtime
modes offered by JPA and EJB 3.0.

I know that is a lot to consume and think about... but figured I should
start shoving the snowball.

Thoughts and comments?

On 10/30/06, David Jencks (JIRA) <> wrote:
>      [ ]
> David Jencks closed DAYTRADER-16.
> ---------------------------------
>     Resolution: Fixed
> Added in rev 469284.  Don't know if direct or ejb mode still work.
> > JPA mode
> > --------
> >
> >                 Key: DAYTRADER-16
> >                 URL:
> >             Project: DayTrader
> >          Issue Type: New Feature
> >          Components: EJB Tier
> >    Affects Versions: 1.2
> >            Reporter: David Jencks
> >         Assigned To: David Jencks
> >             Fix For: 1.2
> >
> >         Attachments: DAYTRADER-16.patch
> >
> >
> > Daytrader needs a JPA mode.  Simplest way is to make the XXXDataBeans
> enhanced.  This will make daytrader java 5 only: it won't compile on jdk
> 1.4.
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> -
> For more information on JIRA, see:

"I say never be complete, I say stop being perfect, I say let... lets
evolve, let the chips fall where they may." - Tyler Durden

View raw message