axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Fremantle" <>
Subject Re: AXIS2 Generated WSDL not correct
Date Wed, 09 Apr 2008 15:25:53 GMT

Please can you try a nightly build. I know a lot of work has gone in
since the 1.3 release, and we are very close to a 1.4 release
candidate, so its quite possible that the situation is better with the
latest builds.

As a workaround, what you can do is edit the WSDL to conform to the
schema that you want, and then add the WSDL into the AAR file. Using
the useOriginalWSDL setting in the services.xml ought to allow you to
get Axis2 to serve up exactly what you want.

<parameter name="useOrignalWSDL">true</parameter>


On Wed, Apr 9, 2008 at 3:58 PM, Glen Verran <> wrote:
> Hi folks,
> It doesn't seem that anybody can answer my question below and I'd like to
> know if there are other more active forums and mailing lists that would be
> able to give me an answer to my question below.  Can you please advise?
> Thanks
> ~Glen
>  ________________________________
>  From: Glen Verran []
> Sent: 08 April 2008 13:57
> To:
> Subject: AXIS2 Generated WSDL not correct
> Hi folks,
> I am very new to AXIS and web services and since I find it extremely
> difficult to find a solution via Google, I am hoping that somebody can
> answer my very simple question.
> I am using Axis2 1.3, Tomcat 5.5 and Java 6_04.
> I created a POJO with one method.  The method's parameter accepts a JAXB2.1
> generated object class RetrieveConfigurationDataRequest and returns a
> JAXB2.1 generated class called RetrieveConfigurationDataResponse.  I
> deployed the web service into Tomcat with the Eclipse plugin.
> When a navigate to the URL of the web service including ?wsdl to get the
> generated WSDL, I see that the elements within the complexTypes for both the
> RetrieveConfigurationDataRequest  and RetrieveConfigurationDataResponse are
> in alphabetical order and not in the order as they appear in the class.  I
> also noticed that AXIS 2 is not taking the annocations into account when
> generating the WSDL since all the elemetns are minOccurs="0" when one of
> them are marked as "required" by the @XmlElement annocation in the JAXB 2.1
> generated classes.
> I am expecting to see the WSDL to reflect as close to the XSD's that
> generated the JAXB 2.1 classes as far as possible and the jaxb generated
> classes contain enough information for Axis 2 to do that.
> Can somebody please let me know how I can fix this so that the WSDL conforms
> to the objects 100%?
> Thanks in advance
> ~Glen Verran

Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair


"Oxygenating the Web Service Platform",

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message