Chris,
I'm calling wsdl2java with ant(build.xml) the only parameters I'm passing are
-osrc for the location of ouput.
With type=xsd1:ExceptionContent ExceptionContent.java is generated,
OutageRequestWebServiceException.java is generated, and
OutageRequestWebService.java(below). Notice that the
Sorry I ran the last test with genned files from previous test. I re-ran wsdl
with 1.1 and got the following.
The following is accurate:
With type=xsd1:ExceptionContent:
1. ExceptionContent.java is generated.
2. OutageRequestWebServiceException.java is NOT generated.
3.
on your code.
Rey.
- Original Message -
From: mark pope [EMAIL PROTECTED]
Date: Mon, 23 Jun 2003 08:52:18 -0700 (PDT)
To: [EMAIL PROTECTED]
Subject: Re: WSDL2Java bug? or my misunderstanding
Sorry I ran the last test with genned files from previous test. I re-ran wsdl
with 1.1 and got
Mark -
When testing the wsdl (and uncommenting the part) wsdl2java is properly parsing the
file. i'm using a nightly build.
can you provide the exact command line that you are using?
thanks,
/Chris
-- Original Message --
From: mark pope [EMAIL
Attached is a very simple example of a WSDL file that fails(produces undesired
behavior in my opinion) when parsed with WSDL2Java and Sun's JWSDP_1.1
wscompile.
Basically I want to define a fault message that contains a part that is of
complextype like this:
wsdl:message
