ws-kandula-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Dillon (ext. 944)" <>
Subject Invocing the TX Service without using WSDL ?
Date Wed, 21 Dec 2005 17:41:21 GMT

I have got a simple sample client working with Knadula using the WSDL
generators etc. However our existing code does not use WSDL generation when
sending Axis requests and instead build up the request using;

        org.apache.axis.client.Call soapSrv =
        soapSrv.setOperationName(new QName(soapSrvName,"testTransactionOp")

        soapSrv.addParameter("name",new QName("xsd:string"),
            new QName("ta:RequestContext"),javax.xml.rpc.ParameterMode.IN);
        soapSrv.setReturnType(new QName("xsd:string"));

        String retValue =(String) soapSrv.invoke(new Object[] {name,

This however results in the service code not knowing the transaction. I.e.
when the invocation arrives the below call returns null;

	Transaction tx= txMgr.getTransaction();

>From looking at the SOAP message it appears that I am missing the
coordination context. I presume I should be adding this on to the
axis.client.Call object using something like


Is this correct ? Is there any sample that invocats a transacted service
like this ?



The information contained in this e-mail is confidential, may be 
privileged and is intended only for the user of the recipient named above.  
If you are not the intended recipient or a representative of the intended 
recipient, you have received this e-mail in error and must not copy, use 
or disclose the contents of this e-mail to anybody else.  If you have 
received this e-mail in error, please notify the sender immediately 
by return e-mail and permanently delete the copy you received.  
This e-mail has been swept for computer viruses.  However, you should 
carry out your own virus checks. 
Registered in Ireland, No. 205721.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message