[
http://issues.apache.org/jira/browse/AXIS2-464?page=comments#action_12368653 ]
Deepal Jayasinghe commented on AXIS2-464:
-----------------------------------------
Well , first it is not a bug :)
This is how it should be;
You can specify default message receivers for your services in services.xml
with mep and message receiver as follows (juts example).
<messageReceivers>
<messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-only";
class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
<messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out";
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
</messageReceivers>
and then if you have operation with above mep , then the message receiver of
thet operation will be the message receivers specified above.
Anyway I will modify the code so that when you are adding operation (which does
not have message receiver) to AxisService it will set the correct message
receiver that you have added to AxisService.
> Setting message reciever on service does not seem to be picked up by
> operations
> -------------------------------------------------------------------------------
>
> Key: AXIS2-464
> URL: http://issues.apache.org/jira/browse/AXIS2-464
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core
> Versions: 0.94
> Environment: All
> Reporter: Rick Rineholt
> Priority: Minor
>
> Initially I set my messgage receiver on my Axis service object .. but
> received a NPE on AxisEngine receive round line 348
> receiver.receive(msgContext);
> seems the receiver was null
> I don't see on AxisOperation.getMessageReceiver logic that if it's null to
> check if the message receiver is set on the Service
> Is this a miss understanding on my part ? If yes what is the pupose for the
> message receiver on the Service?
> BTW setting on the operation did work. :-)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
