No, I don't want JAX-RS to have a transaction model :)
One pattern I've seen in REST is how they solve distributed
transactions. The pattern seems to be
/transactions/{tx-id}/.../whatever/your/real/resources/are
So really the transaction resource is allowed to contain any resource
the server supports. (I hope you are following me, if not I'll expand).
So, how would you implement something like this? The transaction
processing is like a Subresource locator in that it processes the first
part of the request, but it doesn't do anything with the rest of the
request, and doesn't provide a Subresource.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com