axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Butek" <bu...@us.ibm.com>
Subject Re: [jsr110-eg-disc] Code updates...
Date Tue, 04 Dec 2001 20:19:45 GMT
First, Matt, I'll echo Sam's comment.  Thanks for the quick turnaround!

Yes, I've tried both versions in the past and both have worked.  We just
happen to have the one version in our tests.

Russell Butek
butek@us.ibm.com


Matthew Duftler/Watson/IBM@IBMUS on 12/04/2001 01:47:37 PM

Please respond to axis-dev@xml.apache.org

To:   jsr110-eg-disc@yahoogroups.com
cc:   axis-dev@xml.apache.org
Subject:  Re: [jsr110-eg-disc] Code updates...




Hi Russell,

I believe both styles conform to the specification. WSDL4J should be able
to handle either one. The choice of which style to use probably depends on
how you plan on accessing the <schema> elements. If you change the imported
document to be a WSDL document, then the <schema> element can be navigated
to from the WSDL4J interfaces (go from the Definition to the Imports, to
the UnknownExtensibilityElement which wraps the org.w3c.dom.Element). If
you leave it the way it is, which appears to be valid with respect to the
WSDL spec, the WSDL4J code will not link the actual ".xsd" document, it
will only create the Import with the locationURI.

Thanks,
-Matt



                    Sam
                    Ruby/Raleigh/I       To:
jsr110-eg-disc@yahoogroups.com
                    BM@IBMUS             cc:
                                         Subject:     Re: [jsr110-eg-disc]
Code updates...
                    12/04/2001
                    10:02 AM
                    Please respond
                    to
                    jsr110-eg-disc





---------------------- Forwarded by Sam Ruby/Raleigh/IBM on 12/04/2001
09:55 AM ---------------------------

From: "Russell Butek" <butek@us.ibm.com>
Subject: Re: [jsr110-eg-disc] Code updates...
To: axis-dev@xml.apache.org
Cc: jsr110-eg-disc@yahoogroups.com

The 'offending' file is Import.xsd.  It is imported by ImportMessages.wsdl.
Import.xsd contains only XML schema types, no WSDL.  This follows an
example in the WSDL spec, section 2.1.2 Authoring Style.  If Import.xsd is
wrong, then the spec is wrong.

Import.xsd looks like:

<schema>
...
</schema>

If I change it to look like:

<definitions...>
  <types>
    <schema>
      ...
    </schema>
  </types>
</definitions>

then it works.  But I want to know whether we (and WSDL4J) should follow
the spec or whether we should follow WSDL4J before I commit this change.

Russell Butek
butek@us.ibm.com


Sam Ruby/Raleigh/IBM@IBMUS on 12/03/2001 08:40:26 PM

Please respond to axis-dev@xml.apache.org

To:   jsr110-eg-disc@yahoogroups.com
cc:   axis-dev@xml.apache.org
Subject:  Re: [jsr110-eg-disc] Code updates...



Axis has a wsdl definition that could be read by WSDL4J yesterday, but
fails now.  Can I get somebody to take a look at it to see if there is
something wrong with the WSDL or if WSD4J should in fact be able to process
it?

Simple test case is included in the zip.  To compile and run, simply:

   javac wsdl.java
   java wsdl test/import_/Import.wsdl

The output currently produced is:

WSDLException (at /definitions/import[1]): faultCode=INVALID_WSDL: Expected
element 'http://schemas.xmlsoap.org/wsdl/:definitions'.:
        at com.ibm.wsdl.xml.WSDLReaderImpl.checkElementName(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at wsdl.main(wsdl.java:10)
Exception in thread "main"

- Sam Ruby

(See attached file: wsdl4j-test.zip)









To unsubscribe from this group, send an email to:
jsr110-eg-disc-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/









Mime
View raw message