My take on it is this :
with servlet endpoints that are mere adapters to the ejb (stateless and Message ) issues like transaction begin ,commit , rollback require to be understood by the adapter , then as the moderator pointed out , the adapter in turn can get the transaction context and propagate the transaction.
You could wrap the logic of detection of transaction related stuff into a template
pattern , but that it will get used by any one else except your group I doubt.
The issue I see in this is : the fact that the developer is coding the plumbing , a business developer should not be doing this becuase that means changes in standards requires changes in the code .
on the other hand if you go with the ejb endpoint , the work is done by the app server , changes in standards , means upgrading your app server , and not your code thro out the enterprise .
K.P.Thottam (K.P.T)<br /> <br />Sun Certified Enterprise Architect,TOGAF 8 Certified,Certified Information System security Professional (CISSP),SCJDWS,SCWCD,SCJP,MCP