Hi Andreas, It seems like there is a small difference in the webservice response - with Axis 1.4 and Axis 1.0 With Axis 1.0 --
<webServiceApiReturn xsi:type="ns1:Element" xmlns:ns1="http://xml.apache.org/xml-soap";> In this one I can see full formatted output from the SoapUI application With Axis 1.4 -- <webServiceApiReturn xmlns="http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes";> In this one I see full XML just as one line output, not a formatted XML. Also, with Axis 1.4, if see the message detail from tcpmon(axis adminUI), and explicitly select XML option then I see full XML. But SOAP UI does not show it as XML. Is there anything I can tweak in the WSDL/XSD or the WSDD to get the desired output?? Thanks! Neelam -----Original Message----- From: Neelam Dharnidharka Sent: Wednesday, February 19, 2014 7:09 AM To: [email protected] Subject: RE: issues Axis 2/Axis1 Hi Andreas, I tried this option, but it gives me incompatible class issues. Is there any official patch available for axis1.0 with the wsdlFile path fix? Or, I can try axis 1.4, but is the issue of xml output in oneline is a known issue for axis 1.4? Appreciate your inputs! Thanks Neelam -----Original Message----- From: Andreas Veithen [mailto:[email protected]] Sent: Tuesday, February 18, 2014 12:35 AM To: java-dev Subject: Re: issues Axis 2/Axis1 Sorry, I meant org.apache.axis.handlers.soap.SOAPService#generateWSDL, not org.apache.axis.handlers.soap#generateWSDL. Andreas On Tue, Feb 18, 2014 at 12:22 AM, Neelam Dharnidharka < HYPERLINK "mailto:[email protected]"; [email protected]> wrote: > Hi Andreas > Could you pl clarify where to get the fix from? I mean which version of Axis? > I see its fixed in 1.4, but in 1.4 I don't see any class like generateWSDL. > > Appreciate your help in advance! > > Thanks > Neelam > > -----Original Message----- > From: Andreas Veithen [mailto:[email protected]] > Sent: Monday, February 17, 2014 2:32 PM > To: java-dev > Subject: Re: issues Axis 2/Axis1 > > The code responsible for this is in > org.apache.axis.handlers.soap#generateWSDL. You would have to do some > archeology to figure out when that method was modified to support loading the > WSDL from the classpath. > > Andreas > > On Mon, Feb 17, 2014 at 10:06 PM, Neelam Dharnidharka < HYPERLINK > "mailto:[email protected]"; [email protected]> wrote: >> >> Hi Andreas, >> >> I tried Axis 1.4; I can use wsdlFile tag and it reads file from >> the class path, but it shows the output XML in one line!! not the >> formatted XML >> >> If I use same wsdls/xsd in Axis 1.0, it shows correct format. >> >> If there is a know bug in axis 1.0 for the wsdlFile not reading from class >> path, can I get the fix? >> >> Else, what is the issue with Axis1.4 ? why it does not show output in the >> formatted XML? Is there known bug/fix for this ? >> >> The reason we are using Axis 1.0, as this is an old application, and >> in current project we are just adding more webservices to it, there >> is no plan to migrate to axis 2 at the moment; >> >> Thanks >> Neelam >> >> >> -----Original Message----- >> From: Andreas Veithen [mailto:[email protected]] >> Sent: Monday, February 17, 2014 12:17 PM >> To: java-dev >> Subject: Re: issues Axis 2/Axis1 >> >> Axis 1.4 can load the file specified by wsdlFile as a resource from the >> classpath. Any reason why you are using such an ancient Axis version? >> >> Andreas >> >> On Mon, Feb 17, 2014 at 9:05 PM, Neelam Dharnidharka < HYPERLINK >> "mailto:[email protected]"; [email protected]> >> wrote: >>> Thanks! Then is there a way to resolve <wsdlFile> - absolute path in the >>> axis 1? >>> As I mentioned earlier in Axis 1, if I add my custom wsdl as >>> <wsdlFile> tag, I have to give the absolute path, it does not pickup if I >>> keep the file in classes dir ? >>> >>> Is this a known bug with Axis 1.0? >>> Thanks >>> Neelam >>> >>> >>> -----Original Message----- >>> From: robertlazarski . [mailto:[email protected]] >>> Sent: Monday, February 17, 2014 12:02 PM >>> To: HYPERLINK "mailto:[email protected]"; [email protected] >>> Subject: Re: issues Axis 2/Axis1 >>> >>> On Mon, Feb 17, 2014 at 4:59 PM, Neelam Dharnidharka < HYPERLINK >>> "mailto:[email protected]"; [email protected]> >>> wrote: >>>> Can't we use *wsdd file with axis2? >>> >>> Nope! >>> >>> -------------------------------------------------------------------- >>> - To unsubscribe, e-mail: HYPERLINK >>> "mailto:[email protected]"; >>> [email protected] >>> For additional commands, e-mail: HYPERLINK >>> "mailto:[email protected]"; [email protected] >>> >>> >>> -------------------------------------------------------------------- >>> - To unsubscribe, e-mail: HYPERLINK >>> "mailto:[email protected]"; >>> [email protected] >>> For additional commands, e-mail: HYPERLINK >>> "mailto:[email protected]"; [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: HYPERLINK >> "mailto:[email protected]"; >> [email protected] >> For additional commands, e-mail: HYPERLINK >> "mailto:[email protected]"; [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: HYPERLINK >> "mailto:[email protected]"; >> [email protected] >> For additional commands, e-mail: HYPERLINK >> "mailto:[email protected]"; [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: HYPERLINK > "mailto:[email protected]"; > [email protected] > For additional commands, e-mail: HYPERLINK > "mailto:[email protected]"; [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: HYPERLINK > "mailto:[email protected]"; > [email protected] > For additional commands, e-mail: HYPERLINK > "mailto:[email protected]"; [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: HYPERLINK "mailto:[email protected]"; [email protected] For additional commands, e-mail: HYPERLINK "mailto:[email protected]"; [email protected]
