the life cycle of a request context?

[Elhanan]

it's just occured to me, that aside from the requestFactories on
method of creating requestContextes i have no way of handling their
resources, i mean assume that each service locator whould inject an
Entity Manager instance into the context, how would i close such an
entity manager once i'm done with it?

meaning can the implementation of a request context be statefull?

[Elhanan]

[Thomas Broyer]

On Sunday, June 26, 2011 8:38:10 PM UTC+2, Elhanan wrote:

it's just occured to me, that aside from the requestFactories on
method of creating requestContextes i have no way of handling their
resources, i mean assume that each service locator whould inject an
Entity Manager instance into the context, how would i close such an
entity manager once i'm done with it?

Do you mean RequestContexts (on the client-side) or how your requests (made with them) are processed on the server side?

For you EntityManager-s on the server, you should manage their lifecycle in a servlet filter.

See:

• http://code.google.com/p/google-web-toolkit/issues/detail?id=5389
  
• http://code.google.com/p/google-web-toolkit/issues/detail?id=5724
  
• http://code.google.com/p/google-web-toolkit/issues/detail?id=5776