RE: [Axis2] MessageReceiver is Null in Axis2 Operation using WS-RM

2007-05-02 Thread Ted Jones 
Hi Chamikara,
 
Upon further review, I don't believe this is a Sandesha2 issue. The
operation is generated without a CallbackReceiver value set in the ADB
generated stub. If I set a default CallbackReceiver in my client code,
everything works fine. Maybe the operation should have a default
instance of CallbackReceiver set on it OR the ADB generated stub code
should set one on the operation when it is created?
 
Thanks,
Ted



From: Chamikara Jayalath [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 01, 2007 10:51 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] MessageReceiver is Null in Axis2 Operation using
WS-RM


Hi Ted,

Could u please add JIRA (in Sandesha2) and attach whatever the files
necessary to reproduce the error. I just did a test with
Axis21.1.1/Sandesha2 1.1 and it ran without trouble.

Chamikara



On 5/2/07, Ted Jones [EMAIL PROTECTED] wrote: 

I am using Sandesha2 1.1 with Axis2 1.1.1 and am running into an
error where the MessageReceiver is null for the Axis operation and is
causing a NPE. The following code in the OutInAxisOperation class is
where the exception occurs:
 
 if (options.isUseSeparateListener()) {
CallbackReceiver callbackReceiver =
(CallbackReceiver) axisOp
.getMessageReceiver();
callbackReceiver.addCallback(mc.getMessageID(),
callback);
 
I have the message receivers defined in my client axis2.xml and
server axis.xml. I even have the message receivers defined in the
service.xml for good measure.
 
I have set the following options in the Axis2 client: 
 

clientOptions.setTransportInProtocol(org.apache.axis2.Constants.TRANSPOR
T_HTTP);

clientOptions.setProperty(AddressingConstants.WS_ADDRESSING_VERSION,org.
apache.axis2.addressing.AddressingConstants.Final.WSA_NAMESPACE );
clientOptions.setUseSeparateListener(true);
 
The client/service works without Sandesha2 since I am not using
a separate listener in that case.
 
Is there anything else I need to add the the Axis2.xml or client
code to get the receiver set on the operation?
 
TIA,
Ted

  




-- 
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs

Re: [Axis2] MessageReceiver is Null in Axis2 Operation using WS-RM

2007-05-01 Thread Chamikara Jayalath 

Hi Ted,

Could u please add JIRA (in Sandesha2) and attach whatever the files
necessary to reproduce the error. I just did a test with Axis21.1.1/Sandesha2
1.1 and it ran without trouble.

Chamikara


On 5/2/07, Ted Jones [EMAIL PROTECTED] wrote:


 I am using Sandesha2 1.1 with Axis2 1.1.1 and am running into an error
where the MessageReceiver is null for the Axis operation and is causing
a NPE. The following code in the OutInAxisOperation class is where the
exception occurs:

 if (options.isUseSeparateListener()) {
CallbackReceiver callbackReceiver = (CallbackReceiver) axisOp
.getMessageReceiver();
callbackReceiver.addCallback(mc.getMessageID(), callback);

I have the message receivers defined in my client axis2.xml and server
axis.xml. I even have the message receivers defined in the service.xml for
good measure.

I have set the following options in the Axis2 client:

clientOptions.setTransportInProtocol(
org.apache.axis2.Constants.TRANSPORT_HTTP);
clientOptions.setProperty(AddressingConstants.WS_ADDRESSING_VERSION,
org.apache.axis2.addressing.AddressingConstants.Final.WSA_NAMESPACE);
clientOptions.setUseSeparateListener(true);

The client/service works without Sandesha2 since I am not using a separate
listener in that case.

Is there anything else I need to add the the Axis2.xml or client code to
get the receiver set on the operation?

TIA,
Ted







--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs