axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bjorn Townsend (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-2396) two operations with same input/output type not getting invoked correctly
Date Wed, 15 Feb 2006 00:28:10 GMT
    [ http://issues.apache.org/jira/browse/AXIS-2396?page=comments#action_12366415 ] 

Bjorn Townsend commented on AXIS-2396:
--------------------------------------

I've checked the WSDL spec, and it clearly agrees with you (see section 2.3.5, at http://www.w3.org/TR/wsdl#_names
).  Furthermore, it looks like Axis agrees with you too! One of the examples in the Axis User
Guide shows an operation whose name attribute differs from the name attribute of the input
element as well.  

Since you, the WSDL spec and the Axis docs all seem to agree, I tried to reproduce this issue
on my own and wasn't able to.  Can you provide a reproduction/test case that shows the problem?

Thanks,
Bjorn

> two operations with same input/output type not getting invoked correctly
> ------------------------------------------------------------------------
>
>          Key: AXIS-2396
>          URL: http://issues.apache.org/jira/browse/AXIS-2396
>      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
methods
> 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
type.

-- 
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


Mime
View raw message