axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonas Rathert <>
Subject WSDL2Java changes in v1.2 wrt xs:import
Date Mon, 25 Jul 2005 09:47:43 GMT

I have a problem to understand the behavior of WSDL2Java when it comes
to includes.

I have a WSDL-file which contains an import of types from an xsd-file:

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions ...>
      <xs:schema xmlns:xs=""

        <xs:import namespace=""

        <xs:complexType name="Foo">
            <xs:element name="Bar" type="st:Bar"/>
    <!-- ... messages etc. -->

In my xsd, I only define a very simple type:

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="" ...>
    <xs:simpleType name="Bar">
      <xs:restriction base="xs:string">
        <xs:minLength value="1"/>
        <xs:maxLength value="16"/>
        <xs:pattern value="ABC|DEF|GHI"/>

WSDL2Java in Axis v1.1 created the following files:


no matter if I created client stubs or server files. contained
a class with a Bar member that only contains a java.lang.String value -
as expected.

With WSDL2Java in Axis v1.2 this has changed - I only get


where the Bar member is of type java.lang.String.

Can somebody explain this change to me and tell me if there is any issue
   with interoperability between an Axis 1.2 server and an Axis 1.1
client based on my WSDL? I actually found that everything just works if
I accept and use the classes that are generated, I am jut curious why
the "extra classes" disappeared in v1.2 and if and how I can get them
created by WSDL2Java.

Kind regards,


   Note: 96.31% of all statistics are fiction.

View raw message