Marc wrote:

> [ Justin wrote]

>> The fundamental problem here is that if the bean context is extensible,
>> the passivation/activation mechanisms must recognise any extension.
>
>which is why it should be done by jaws and not the container or the manager
>(PersistenceManager).. this is "store" specific, not "manager" specific.

OK - so how does JAWS get at the passivation store? (as opposed to the
persistent store, which JAWS *is* responsible for)

-- 
Justin Forder

Reply via email to