Dasarath, Thanks, the client-conifg.wsdd that I was using had the j2ee.handler.TransactionHandler instead of the standalone handler enabled.
Thanks again, Brian -----Original Message----- From: Dasarath Weeratunge [mailto:[EMAIL PROTECTED] Sent: 21 December 2005 21:47 To: [email protected] Subject: Fwd: Re: Invocing the TX Service without using WSDL ? ----- Forwarded message from Dasarath Weeratunge <[EMAIL PROTECTED]> ----- Date: Wed, 21 Dec 2005 16:43:35 -0500 From: Dasarath Weeratunge <[EMAIL PROTECTED]> Reply-To: Dasarath Weeratunge <[EMAIL PROTECTED]> Subject: Re: Invocing the TX Service without using WSDL ? To: "Brian Dillon (ext. 944)" <[EMAIL PROTECTED]> Quoting "Brian Dillon (ext. 944)" <[EMAIL PROTECTED]>: > Hi, > > 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 = > getSOAPService(getServiceProperties().getServiceName()); > soapSrv.setOperationName(new > QName(soapSrvName,"testTransactionOp") > ); > > soapSrv.addParameter("name",new QName("xsd:string"), > javax.xml.rpc.ParameterMode.IN); > soapSrv.addParameter("requestContext", > new QName("ta:RequestContext"),javax.xml.rpc.ParameterMode.IN); > soapSrv.setReturnType(new QName("xsd:string")); > > String retValue =(String) soapSrv.invoke(new Object[] {name, > requestContext}); > > 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 > > soapSrv.addParameterAsHeader(...) > > Is this correct ? Is there any sample that invocats a transacted > service like this ? This shouldn't be required. I presume you are trying to retrieve the tx-object on the server side. If the coordination context is missing when the client side (j2ee or standalone) has a tx-context then it is a problem with the tx handler. Whenever there is an active tx-context at the time the service is invoked, the tx-handler automatically adds in the coordination context-- you do not have to add it in explicitly. Check whether all handlers are properly diployed: e.g. whether axis-engine is able to locate the *-config.wsdd etc. Further, as a result the method (DII/stubs...) you use to invoke the service has no bearing on Kandula. --dasarath > > Thanks, > > Brian > > ********************************************************************** > 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. http://www.FINEOS.com > ********************************************************************** > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ----- End forwarded message ----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
