I have solved one of the problems (i.e.
arrays being generated in the "throws" clause) by adding a "-w" to the
wsdl2java command line options.
I have attached an example of a broken source file with an invalid
constructor super call because the superclass is java.lang.Object! I
think the problem is caused when an element extends a simple type with
an attribute. Is that what you mean by an "anonymous complex type"?
The following XSD reflects the attached broken code:
...
...
...
This XSD generate code fine with Axis 1.2 but I haven't thoroughly
tested a client...
Regards,
Terry
Franz Fehringer wrote:
Hello,
Out of curiosity:
Your WSDL contains multiple portTypes.
Is this supported with AXIS1JAVA?
Btw i work also with PegsTour (Singular Interface pertaining to PT
version 2.12.2), but i use the C++ implementation of Axis.
This one definitely cannot cope with multiple portTypes (i think even
for Axis2 this is a TODO yet, not quite sure however).
Furthermore Axis1 (both Java and C++) has problems with anonymous
complexTypes (this is much improved in AXISCPP nightly), so i am
slightly surprised to hear that you could successfully use Axis1 1.2
Greetings
Franz
Cantrell, Andrew schrieb:
OK – have
attached a version that I
think complies with your suggestions however we are still getting
compile errors
Regards
Andrew
From:
Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Okay
... just for
starters, your import statement is in error.
You are trying to import a schema definition (PegsTour.xsd) using
. may be used only to import
WSDL
descriptions, not schemas. Axis 1.2 was lax and permitted you to do
this, but
Axis 1.4 is more strict.
You must add a section to the document, define a
schema, and
use or to import/include the
schema. You
use to import a schema in a different namespace, and
you use
to include multiple schema files that define the
same
namespace.
Next, the PegsTour.xsd schema references a ton of components that are
not
defined in the schema file. My guess is that they are defined in all
the other
schema files that you supplied, but you don't them
into the
schema. Therefore, you can't reference them. You must add an
statement for each of the other schema files. I
haven't
looked at the other schema files, but if any of them reference
components
described in other schema files, you must also add
statements to those schemas.
Regards,
Anne
On
1/29/07, Cantrell,
Andrew <[EMAIL PROTECTED]>
wrote:
Please post the WSDL.
On 1/29/07, Terry Mueller
<[EMAIL PROTECTED]> wrote:
> I have tested WSDL2Java with our WSDL using Axis 1.2 without any
> problems. When I upgrade to Axis 1.4 (drop in new jars), the same
> command generates code with compile errors. There are three basic
> compilation problems: (1) in some constructors of simple types there is
> call to super(foo,bar) that doesn't exist (2) the "throws" clauses
> declaration contains an array and (3) the class in the "throws" clause
> does not extend
java.lang.Exception.
>
>
> I was having a play with Lisa test tool from
http://www.itko.com/ which
> uses Axis 1.4 so I can't upgrade to Axis 2 yet.
>
>
> Any ideas?
>
> -
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail:
[EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
--
Regards,
Terry
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
/**
* T_WarningDescription.java
*
* This file was auto-generated from WSDL
