Removing public SlideTokenWrapper(SlideToken token, boolean forceStoreEnlistment)

[Oliver Zeigermann]

As I described before there is a problem with the the frequent usage of 
SlideTokenWrapper to have code executed outside the current transaction. 
   Security code does this all the time. However, this only works 
because of flaws in all current XAResource implementations that match 
this bug. I wanted to fix this flaw to have the implementations more 
spec compliant. This is mandatory for the external transaction stuff I 
am currently working on.

To avoid frequent usage of the SlideTokenWrapper to have code executed 
outside the current transaction I opt for removing constructor

public SlideTokenWrapper(SlideToken token, boolean forceStoreEnlistment)
and only having
public SlideTokenWrapper(SlideToken token)
This would of course require lots of changes in the code, but I would be 
willing to do so.

If someone really knows what he does and wants code to be executed 
outside of the current transaction you could still call 
setForceStoreEnlistment after the ctor. This will for example be done in 
the check if a requested URI is a collection before a transaction is 
even started in the GET and POST methods.

If I do not hear any objections I will do it the way described.
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]