Dain Sundstrom wrote:
> Bill,
>
> Thanks for the reply. I really need other people thinking about this,
> because I don't understand the rest of the container.
>
> Here's the deal. I delegate the actual storage of the other updated
> contexts to the their respective persistence storage managers, so they get
> stored by correct data source. I also get references to the other beans
> through their container's cache.
Errr. I was nervous enough about the persistence manager messing with
its own bean's cache, let along messing with other bean's caches.
>
> I think the biggest problem with this implementation is that my persistence
> store is directly calling store on other persistence stores, thus by passing
> all of the code that is supposed know the right way to do this.
Ya, this makes me nervous too - there's too much that can go wrong.
Really to get the store going you should be hooking into the transaction
(which is the job of the EntitySynchronizationInterceptor)
What about Bill's suggestion to go through the homes? That may not be
the best performance, but then you know that all the Right Things are
happening, even if (when) the definition of Right Thing changes. Short
circuiting the interceptor chain is bad, IMHO.
-danch
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
