Java2WSDL creates WSDLs that fail Eclipse validation
----------------------------------------------------

                 Key: AXIS2-3551
                 URL: https://issues.apache.org/jira/browse/AXIS2-3551
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: codegen, wsdl
    Affects Versions: 1.3
            Reporter: Paul Fremantle
             Fix For: 1.4


I recently used the Eclipse WebTools WSDL validator. It doesn't like
the way that Axis2 creates Schemas. If you look at the AddressBook
WSDL that gives you a good example.

   <wsdl:types>
       <xs:schema xmlns:ns="http://service.addressbook.sample";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://service.addressbook.sample";>
           <xs:element name="findEntry">
           .... wrapper elements here
       </xs:schema>
       <xs:schema xmlns:ax21="http://entry.addressbook.sample/xsd";
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://entry.addressbook.sample/xsd";>
           <xs:complexType name="Entry">
           .... data type elements here

The problem is that the wrapper elements refer to the data-type
complextypes, which are defined in two separate schema chunks. So the
Eclipse WSDL validator sees these as separate and cannot resolve the
cross references.

Now the reason - I'm guessing - that Axis2 generates these in separate
schema chunks, is because it wants to give them separate target
namespaces.

So either this needs to create a single Schema chunk or a link between them.

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

Reply via email to