NEW ISSUE: Transaction defaults are not optimal

[David Booz <booz@us.ibm.com>]

NOTE: This resolves action item 20071210-02



TARGET: OSOA Transaction Spec V1.0 (for editors only, SCA Policy FW working
draft 04)

[1]
http://www.oasis-open.org/committees/documents.php/26292/SCA_TransactionPolicy_V1.0.pdf



DESCRIPTION:

It is unfortunate to have to explicitly specify something when it is the
desired behavior in the vast majority of circumstances. In my opinion,
components that operate in global transactions should, by default, be able
to join in the transaction of the client. The more rare behavior of
suspending the transaction is what should be specified if you explicitly
don't want some operation to be able to join in the transaction of the
client.

I'm not sure you can wire from an @ProgagatesTransaction reference to a
component that is ManagedTransaction.global, if there is no interaction
intent on the component."
@ManagedTransaction("global")
public class FooImpl implements Foo { ...
}

public class client {
@ProgagatesTransaction
public Foo foo;
}

@ManagedTransaction("global")
@PropogatesTransaction <<<<<====this MUST be coded to get a normally
expected behavior
public class FooImpl implements Foo { ...
}

public class client {
@ProgagatesTransaction
public Foo foo;
}


Originally Issue SCA-259 from OSOA.

PROPOSAL: None




Dave Booz
STSM, SCA and WebSphere Architecture
Co-Chair OASIS SCA-Policy TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093  or  8-295-6093
e-mail:booz@us.ibm.com
http://washome.austin.ibm.com/xwiki/bin/view/SCA2Team/WebHome