[
https://issues.apache.org/jira/browse/AXIS2-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978287#action_12978287
]
Supun Malinga commented on AXIS2-4718:
--------------------------------------
Hi,
Found the actual problem. In the wsdl you have specified two schema elements.
Then the first schema element is referenced in the second schema. Here you have
to import the namespace of the first schema to the second one. Otherwise the
first schema element is not visible in the second schema.
thanks,
Supun Malinga
> Code generated by WSDL2JAVA is not compatible with original WSDL
> ----------------------------------------------------------------
>
> Key: AXIS2-4718
> URL: https://issues.apache.org/jira/browse/AXIS2-4718
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Windows XP / Solaris 10
> Reporter: Dmitriy
> Attachments: axis2-issue.zip
>
>
> There is a WSDL file given. When using wsdl2java utilitu to generate service
> skeleton and necessary support classes (ADB bindings), the resulting server
> does not follow the originally used WSDL. Specifically, additional layer of
> elements in the "in" and "out" messages is present in the service, so the
> clients generated using the original WSDL can not communicate with the
> service. In the provided example, the expected message structure is:
> <soap:Body>
> <dvk:mappedText>
> <xsd:mappedText>
> <xsd1:text>?</xsd1:text>
> </xsd:mappedText>
> </dvk:mappedText>
> </dvk:hello>
> </soap:Body>
> but the generated service skeleton expects the following:
> <soap:Body>
> <dvk:hello>
> <dvk:mappedText>
> <xsd:mappedText>
> <xsd1:text>?</xsd1:text>
> </xsd:mappedText>
> </dvk:mappedText>
> </dvk:hello>
> </soap:Body>
> There is an additional level of "wrapping" for the in/out messages (element
> dvk:hello) exists in the generated code preventing the client from
> communicating with the service. The same problem is observed using the
> clients using ADB and XMLBEANS bindings.
> I have small project demonstrating the problem which I will try to attach to
> this ticket.
> Note: I have been able to invoke the generated service using SUAPUI utility
> using the WSDL exported by AXIS under http://<url>?wsdl. The main problem is
> I seem to be unable to use "contract first" approach because the generated
> service is not compatible with originally designed contract.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
