Thanks Deepal,
I already made changes according to Chintaka. Now I have BPEL to Axis2
asynchronous echo service working, earlier when I was invoking BPEL process
as Callback from server, I was usning Axis2 client to make callback like
ServiceClient sender = new ServiceClient();
sender.engageModule(new QName(Constants.MODULE_ADDRESSING));
And this use to throw null pointer error, infact I don't need to engage
module b'cos my service and client both running on server side with globally
engage addressing module.
Since I was creating new service client instead from existing current
context like
ServiceClient sender = new
ServiceClient(msgContext.getConfigurationContext(),
msgContext.getAxisService());
And this take care of addressing in SOAP Header.
I still have some issue to fix
1) Specifying userdefined wsdl and let axis2 uses my custome wsdl instead of
generating new one( I did meta-inf/services.wsdl in service archive but same
result)
2) Getting error from WSDL2Java when importing ws-addressing schema in wsdl
<schema xmlns="http://www.w3.org/2001/XMLSchema";>
<import
namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing";
schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
</schema>
You can try yourself , I tried with Xmlbean and Jaxme
I am going to use AsyncMessageReceiver example from integration folder in
SVN to make call back to BPEL
process instead of using ServiceClient.
I am not sure it will work without making some changes , I will update the
result.
Thanks
Gopal
--
View this message in context:
http://www.nabble.com/-Axis2-1.0RC1-Problem-getting-MessageContext-in-ServiceImpl-class-t1423137.html#a3946331
Sent from the Axis - User forum at Nabble.com.
