marc fleury <[EMAIL PROTECTED]> wrote:
>Following the wars and all...
>
>I did the 2 stage factorization but.... It all boiled down to the fact that
>the old architecture did not really distinguish between a CMP Persistence
>manager and a BMP persistence manager. (they were final plugins as in Jaws
>and BMP). And this was reason why 2tier seemed simpler than 3tier.
>
>As Dan and juha advocated the 3 tier solution acknowledges the difference
>between "store" and "persistence manager". The CMP PM is the "container
>persistence manager" and it takes care of ALL the callbacks to the instances
>before firing the pure "storing" operations. These operations are now in
>the PersistenceStore interface and CMPPersistenceManager (that both closely
>mimics the old EntityPersistennceStore) and JAWS and File are extensions.
>The factorization is done.
>
>The CMP persistence manager takes the return of create (previously void) as
>the key generated by the store. In clear the only thing that the store
>needs to do is return that primary key and the container deals with it.
>
>The "hookup" procedure is slightly changed in ContainerFactory.java
>
>Finally I would like to say that activate still reaches the store (even
>though it is pure EJB) to allow for the context setting by the plugin (jaws
>uses it for smart updates) so that it is a good place to do it.
I shall make the corresponding changes in the Command-based
implementation.
Given that JAWSPersistenceManager now implements EntityPersistenceStore,
should its name change to JAWSPersistenceStore?
What is the status of JAWS tests? If I can put my code through good
tests I'll be happy to put it in CVS. Otherwise, it's a choice between
waiting until I've developed tests myself, or putting it on a branch...
or inflicting it on everyone at a time when I know I can do some rapid
fixing...
--
Justin Forder
