Am 20.06.2011 19:02, schrieb Timothy Ward:
My advice would be to only ever access a managed EntityManager from within a transaction context, then you can treat it as if it were thread safe.
Good to know - that's my default pattern anyway, so there's nothing to worry about :-)
As for OSGi services, OSGi only offers two ways to provide a service. One is as a singleton, one is as a single instance per bundle that uses it. We did discuss the concept of a "stateless" scope for blueprint beans (much like a pooled stateless session bean in Java EE), but I don't think we ever had time to implement it. If you'd like to add it to the code as a contribution then please be our guest!
Thanks, I think I may get back to you on that idea in a while - for now, I'm still busy learning more about Aries from the user perspective,
and I don't think I'm ready to contribute (yet). Regards, Harald
