You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org> on 2005/08/09 13:24:36 UTC

[jira] Resolved: (AXIS2-130) Two operations refering to same message

     [ http://issues.apache.org/jira/browse/AXIS2-130?page=all ]
     
Ajith Harshana Ranabahu resolved AXIS2-130:
-------------------------------------------

    Fix Version: 0.91
     Resolution: Fixed

The real problem is that the same operation name is used twice. The data bind supporter name is formed using the operation name and two operations with the same name (across different port types) causes one to be overridden.
Now the data bind supporter class name has the portype name also (assuming porttype names are unique).

> Two operations refering to same message
> ---------------------------------------
>
>          Key: AXIS2-130
>          URL: http://issues.apache.org/jira/browse/AXIS2-130
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: databinding
>     Reporter: Thilina Gunarathne
>     Assignee: Ajith Harshana Ranabahu
>      Fix For: 0.91

>
> I have a WSDL which uses the same message in two operations. In one operation it used it as a Input Message (Async One way operation) and in the other it is used it as a Output message (sync request response operation)
> I tried to codegen for that wsdl and ended up having the generated class corresponding to the above message lacking some methods. It does not generate the "toOM" method in the Data Binding supporter class. Which makes it impossible to use with the output message scenario.... It seems the class generating for the Input message replaces the class generated for the output message.

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