axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Ruby" <>
Subject Re: WSDL4J import problem
Date Thu, 14 Mar 2002 14:04:14 GMT

- Sam Ruby

---------------------- Forwarded by Sam Ruby/Raleigh/IBM on 03/14/2002
09:02 AM ---------------------------

Sam Ruby
03/06/2002 09:16 AM

cc:    Francisco Curbera/Watson/IBM@IBMUS, Matthew
       Duftler/Watson/IBM@IBMUS, Sanjiva Weerawarana/Watson/IBM@IBMUS
From:  Sam Ruby/Raleigh/IBM@IBMUS
Subject:    Re: WSDL4J import problem  (Document link: Sam Ruby)

I definitely believe that there is a bug somewhere, though I will not
hazard a guess as to where the bug may be.

For context, take a look at
 .  It took me quite a while to find a set of definitions which I could use
to progressively disclose some of the concepts behind WSDL.  The first
thing to note is that the set of definitions described there actually work
with the current WSDL4J and WSDL2Java code base, as demonstrated by the
test described in that same essay.

Now move the import statement from binding.wsdl to immediately before the
import statement in tutorial.wsdl.  The result will be a
java.lang.NullPointerException.  Not good.

 - - - -

What I would like to see is for us to work together to address this.  Three

(1) Which, if any, of the above two sets of WSDLs (before and after the
moving of the import statement) are valid according to the spec?

(2) Given the answer to (1) above, how should WSDL4J handle both cases?

(3) Given the answer to (2) above, how should WSDL2Java handle both cases?

If necessary, lets iterate through these three until we end up with an
answer to #3 which either produces the expected results or meaningful error


- Sam Ruby

View raw message