[ 
https://issues.apache.org/jira/browse/AXIS-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIS-1964:
----------------------------------

    Labels: javax.xml.rpc.Service  (was: )
    
> Axis can't recognize method from port type operations on JDK5
> -------------------------------------------------------------
>
>                 Key: AXIS-1964
>                 URL: https://issues.apache.org/jira/browse/AXIS-1964
>             Project: Axis
>          Issue Type: Bug
>    Affects Versions: 1.2RC3
>         Environment: JDK5 build 1.5.0_02-b09
>            Reporter: Jason Carreira
>            Priority: Critical
>              Labels: javax.xml.rpc.Service
>
> When running client code created using WSDL2Java it cannot recognize the 
> method to execute. The problem is in this code snippet starting with line 
> 1338 in org.apache.axis.client.Call:
>         for ( int i = 0 ; i < operations.size() ; i++, op=null ) {
>             op = (Operation) operations.get( i );
>             if ( opName.equals( op.getName() ) ) {
>                 break ;
>             }
>         }
> The problem is that opName is the name of the method from the generated stub 
> interface: "getWeatherInfo". The op.getName is returning "GetWeatherInfo".
> This problem is fixed by replacing that code with this:
>         for ( int i = 0 ; i < operations.size() ; i++, op=null ) {
>             op = (Operation) operations.get( i );
>             if ( opName.equals( JavaUtils.xmlNameToJava( op.getName() ) ) ) {
>                 break ;
>             }
>         }
> But then it fails to find the BindingOperation a few lines later when it does 
> this:
>         BindingOperation bop = binding.getBindingOperation(opName, null, 
> null);
> But replacing this with the following line lets it get through the Call 
> method (and on to another bug):
>         BindingOperation bop = binding.getBindingOperation(op.getName(), 
> null, null);
> by looking at the op.getName() instead of opName which, as we saw above, are 
> not equal in this case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to