[jbosstools-issues] [JBoss JIRA] (JBIDE-13527) [tester] freeze parsing wsdl

[Alessio Soldano (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753791#comment-12753791 ] 

Alessio Soldano edited comment on JBIDE-13527 at 2/12/13 5:42 PM:
------------------------------------------------------------------

Sorry for the previous post, this is indeed an example of a quite complex contract; I've looked again at the wsdls, I believe the following in your message:
{code}
<type:Register xmlns:type="http://types.complex.jaxws.ws.test.jboss.org/">
<comp:Customer xmlns:comp="http://complex.jaxws.ws.test.jboss.org/">
{code}
is invalid because the Register type is defined in the schema with targetNamespace "http://types.complex.jaxws.ws.test.jboss.org/" and that schema has elementFormDefault=qualified. So the first element of the sequence defined in the complex type Register has to be qualified and use the namespace of the type, which is still http://types.complex.jaxws.ws.test.jboss.org/ and not http://complex.jaxws.ws.test.jboss.org/. On the countrary, the contents of that element, which will be of type { http://complex.jaxws.ws.test.jboss.org/ }Customer, will of course use http://complex.jaxws.ws.test.jboss.org/ namespace.

As a side note, one of the reason why I moved to the jaxws tooling generation in Wise is exactly to avoid having to deal with this complex types namespace mess and rely on already tested, certified and interoperable wsdl parsing / message binding mechanisms.
                
      was (Author: asoldano):
    Sorry for the previous post, this is indeed an example of a quite complex contract; I've looked again at the wsdls, I believe the following in your message:
{code}
<type:Register xmlns:type="http://types.complex.jaxws.ws.test.jboss.org/">
<comp:Customer xmlns:comp="http://complex.jaxws.ws.test.jboss.org/">
{code}
is invalid because the Register type is defined in the schema with targetNamespace "http://types.complex.jaxws.ws.test.jboss.org/" and that schema has elementFormDefault=qualified. So the first element of the sequence defined in the complex type Register has to be qualified and use the namespace of the type, which is still http://types.complex.jaxws.ws.test.jboss.org/ and not http://complex.jaxws.ws.test.jboss.org/. On the countrary, the contents of that element, which will be of type {http://complex.jaxws.ws.test.jboss.org/}Customer, will of course use http://complex.jaxws.ws.test.jboss.org/ namespace.

As a side note, one of the reason why I moved to the jaxws tooling generation in Wise is exactly to avoid having to deal with this complex types namespace mess and rely on already tested, certified and interoperable wsdl parsing / message binding mechanisms.
                  
> [tester] freeze parsing wsdl
> ----------------------------
>
>                 Key: JBIDE-13527
>                 URL: https://issues.jboss.org/browse/JBIDE-13527
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Webservices
>    Affects Versions: 3.3.2
>            Reporter: Alessio Soldano
>            Assignee: Brian Fitzpatrick
>         Attachments: jaxws-complex.war, threaddump.txt
>
>
> JBT freezes when the ws tester is used to consume the wsdl contract for the jaxws-complex.war test deployment of JBossWS testsuite.

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