Glen Please raise a JIRA report on the problems (http://issues.apache.org/jira).
Regards, Paul On Wed, Apr 9, 2008 at 5:18 PM, Glen Verran <[EMAIL PROTECTED]> wrote: > Hi Paul, > > I've just tried the latest nightly build (9th April) and my WSDL is > still ordering the elements in alphabetical order. I am aware of the > workaround, but at the end of the day, I don't want to write a WSDL, but > let Axis generate one for me when I query the web service with ?wsdl. > > Another problem that I found is that my RetrieveConfigurationDataRequest > class extends another class called JaxbInternalMsg which has 2 > getter/setter methods. These methods are being exposed by the WSDL > which I don't want exposed at all. I am using @XmlTransient annotation > so that JAXB 2.1.6 does not expose this class, but it doesn't seem to > work under Axis 2. > > Another problem I am getting is that JAXB 2.1.6 generates "is" methods > for boolean xsd types and not "getters". The "redirect" value is > accessed via an isRedirect method and not a getRedirect method and Axis > 2 is not happy that it could not find a "get" method. A Fault is > generated from the web service as below. > > Exception in thread "main" org.apache.axis2.AxisFault: > org.apache.axis2.AxisFault: can not find read method for : redirect > at > org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java > :486) > at > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(Out > InAxisOperation.java:343) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper > ation.java:389) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA > xisOperation.java:211) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 > ) > at > com.traderoot.webservices.configurationdistribwebservice.ConfigurationDi > stribWebServiceStub.retrieveConfigurationData(ConfigurationDistribWebSer > viceStub.java:172) > at Test.main(Test.java:23) > > Paul, what is the best and quickest way to get these issues addressed in > Axis2 by the developers? > > Thanks > ~Glen > > > > -----Original Message----- > From: Paul Fremantle [mailto:[EMAIL PROTECTED] > Sent: 09 April 2008 17:26 > To: [email protected] > > > Subject: Re: AXIS2 Generated WSDL not correct > > Glen > > 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> > > Paul > > On Wed, Apr 9, 2008 at 3:58 PM, Glen Verran <[EMAIL PROTECTED]> > 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 [mailto:[EMAIL PROTECTED] > > Sent: 08 April 2008 13:57 > > To: [email protected] > > 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 > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > 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] > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
