axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prabhat Jha (JIRA)" <>
Subject [jira] Commented: (AXIS-2396) two operations with same input/output type not getting invoked correctly
Date Wed, 08 Feb 2006 23:15:00 GMT
    [ ] 

Prabhat Jha commented on AXIS-2396:

I found out after looking into the that it does not match SOAP URN while
figuring out which method to invoke. In this case, it found CrateReservation and it called
this everytime. 

The work around( I am not sure it's a work around or that's way you have to do it in Axis--I
could not find the documentation) is that your operation name has to match it's input message
name. For example:

<wsdl:operation name="CreateReservation">
			<wsdl:input message="r-ws:CreateReservation"/>
			<wsdl:output message="r-ws:CreateReservationResponse"/>

Do the same for other operations and it works. I am not sure why AXIS team decided to go this
way. I need some insight into this and I would appreciate if anybody can.


> two operations with same input/output type not getting invoked correctly
> ------------------------------------------------------------------------
>          Key: AXIS-2396
>          URL:
>      Project: Apache Axis
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.3
>  Environment: OS-Windows XP
> Container-Weblogic(8.1 sp4)
> java:1.4.2
>     Reporter: Prabhat Jha
>     Priority: Critical

> I used WSDL2Java to generate web services stub and classes. It correctly generated three
> public MyResponse createReservation(Reservation body);
> public MyResponse adjustReservation(Reservation body);
> public AnotherRespose checkAvailability(Status body);
> When I invoked the adjustReservation web service using Axis Client, createReservation
gets executed. I have debugged it in eclipse and for some reason, RPCProvider invokes createReservation
eventhough MessageContext has correct SoapActionURI which is AdjustReservation.
> checkAvailability operation gets called correctly.
> It seems to be a bug for it can not handle methods with different names but same input/output

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message