Our use case involves SLSBs calling other SLSBs exposed as webservices. We want distributed transactions.

@Stateless
public class ClientBean implements Client {

 @TransactionAttribute(REQUIRES_NEW)
 public void doSomething() {
 Result result = service.performSomething(pojo);
 }
}

@Stateless
@WebService
public class ServiceBean implements Service {

 @WebMethod
 @TransactionAttribute(MANDATORY)
 public Result performSomething(Pojo pojo) {
 ...
 }
}

Is this way of doing things currently supported? We have tried the above scenario but an EJBTransactionRequiredException is thrown upon invoking the service indicating the transaction is not propagated to the webservice. We run on JBoss 4.2.1.GA with JBossWS 2.0.1.GA installed. Is additional configuration required to make the above work?

Are we correct in assuming transaction propagation would be handled transparantly by the application server for our use case? It seems the BasicClient example requires additional configuration to place the transaction context in a SOAP request. However, the BasicClient example does things quite different from the standard EJB3 way outlined above. What need to be done to get transaction propagation running