[ http://issues.apache.org/jira/browse/AXIS2-597?page=comments#action_12375981 ]
Frank Cornelis commented on AXIS2-597: -------------------------------------- I've attached an equivalent example WSDL and XSD. After using the codegen Ant task and deploying the JAR (AAR) in Axis2, the generated ?WSDL shows me some weird things: - The xs:schema targetNamespace is 'http://be.frankcornelis.axis2._1._0.test.types/xsd' instead of 'urn:be:frankcornelis:axis2:1.0:test:types' as specified in the WSDL and XSD. - The soap:operation soapAction has value 'urn:Echo' while the original WSDL specifies just 'Echo'. > "argument type mismatch" on result = (OMElement) method.invoke(obj, args); > -------------------------------------------------------------------------- > > Key: AXIS2-597 > URL: http://issues.apache.org/jira/browse/AXIS2-597 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Reporter: Frank Cornelis > > I'm using the SVN version of Axis2. > I have a simple doc/lit WSDL. Using a JAX-WS service with JAX-WS client works > just fine. > An Axis2 service with the JAX-WS client gives me an "argument type mismatch" > on > result = (OMElement) method.invoke(obj, args); > within RawXMLINOutMessageReceiver.java (line 100). > I assume this is the last step before entering my implementation class... so > it would be cool if it got fixed. :) > The targetNamespace is of format "urn:xxx:yyy", the external schema has a > namespace "urn:xxx:yyy:types". For the rest it's a normal doc/lit WSDL. > BTW: great work... most of the bugs I reported so far got fixed somehow. > Frank. -- 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
