Originally posted by Andrew Perepelytsya:
You can solve the problem by tunnelling your request through some facade. Stateless Session Bean is a nice candidate for this. So, you talk to your HTTP app (or web service, it doesn't matter) in one of its business methods.
So, let's supose that the bean in question calls a helper class - an ordinary java class. What exactly does happen there - if the helper throws that error - it will propagate to the bean and cause the transaction be rolled back, right?
and everything is fine this way?
One could implement a failsafe method, to try and check the remote system datastore for success after such a failure - is this some good?
Originally posted by Pamir Bahret:
I think the answer for problem two is compensating transactions. What do you think ?