Handling transaction roll-back in RequestFactory service implementations

Some background: I'm using Hibernate on the server side to implement
data retrieval/update operations, with RequestFactory service methods
to handle interaction between the client and server.

Suppose that an error condition is encountered during a service
implementation, and to handle that error a database transaction is
rolled back. If I do this, then calls to the Locator's "find" method
fail, after my service method completes, due to the Hibernate session
being closed . I think that the RF framework is trying to load the
objects that were sent as parameters to my service method, in order to
determine if they have changed or not. RF encounters exceptions
starting at line 268 of SimpleRequestProcessor (in method
createReturnOperations).

I think that I can work around this by starting a new transaction in
my service method after rolling back the one that failed, but I'm
wondering if there is a better way to handle this. Since my service
doesn't have any way to communicate with the RF framework, I think the
answer is no, but I thought I would check.

Thanks!
Ryan

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.