Dims, Thanks for the suggestion to use ADB and answering all my other questions. I already read in AIXS2 documentation that ADB is the most stable and the preferred data binding for Axis2. The reason I decided to stick with XMLBeans is the current codebase which I have to port to Axis2 contains couple of thousands lines of code and all of it uses XMLBeans. All this combined with I being new to Axis2 and having a tight deadline made XMLBeans the better choice for now. If time allows I will move everything to ADB later on.
Thanks, Stefan Davanum Srinivas wrote: > >>Stefan, >> >>Thanks for the summary. Regarding Axis2 v1.1.1, even though wsdl2java >>did not complain, the current client would have failed to interop with >>the generated service. Since the server-side code does not really >>support rpc/encoded. That's exactly the reason why we throw the >>exception in Axis2 1.2 so that people are not led down the garden path >>and then get to know the limitation in the end and get frustrated. >> >>Yes, it's better to use rpc/lit. Just make sure the client is not on >>.NET 1.x which does not support rpc/lit. XMLBeans is a bit slow under >>some circumstances. But if it works for you, just stick to it. >>Alternative is to use the ADB (which is the default data binding). >>I'd definitely run it under Tomcat. SimpleHTTPServer is getting there >>for production use, but i am more inclined to use tomcat for >>production purposes. Also FYI, If you decide to switch to ADB, we'd >>definitely back you up if you run into codegen issues or runtime >>issues as both are under our control. XMLBeans is a separate project >>as you know... >> >>thanks, >>dims > > On 5/5/07, stefan_dragnev <[EMAIL PROTECTED]> wrote: >> >> Dims, >> >> It is a service which currently runs on BEA Weblogic but we are migrating >> to >> open source. The plan was to >> migrate it to Axis2. Since Axis2 v1.1.1 was not throwing exceptions I was >> able to generate skeleton and stub files using WSDL with rpc/encoded >> bindings. Then I wrote, compiled and deployed a service using XMLBeans >> binding but when I deployed on the server I kept getting faults each time >> when I invoked the service. That's when I saw Axis 1.2 is already release >> and thought that it might solve the problem. It didn't as with 1.2 I >> could >> not even generate stubs and skeletons and that is when I wrote for first >> time to the email list. >> >> The WSDL which I inherited and is currently used in production is using >> rpc/encoded style. I have no control over the client side to make them >> change their code. But on Friday I modified the WSDL to use rpc/literal >> style and was able to run wsdl2java on it without any problems. Hopefully >> the client side will be willing to change their code to use rpc/literal >> style. >> >> I'm using XMLbeans as data binding. What is more efficient when it comes >> to >> speed - running a standalone Axis2 server or running it under Tomcat? Are >> there any advantages using one or the other? >> >> Thanks, >> Stefan >> >> >> Davanum Srinivas wrote: >> > >> >>Stefan, >> >> >> >>Is this an Axis2 based service in production? and you have a custom >> wsdl? >> >> >> >>-- dims >> >> >> > On 5/3/07, stefan_dragnev <[EMAIL PROTECTED]> wrote: >> >> >> >> Dims, >> >> >> >> I'm sure the wsdl uses rpc/encoded because it contains the following >> >> section: >> >> >> >> <binding name="WebServiceSoap" type="s0:WebServiceSoap"> >> >> <soap:binding transport="http://schemas.xmlsoap.org/soap/http"; >> >> style="document"/> >> >> <operation name="UpdateCategoriesReq"> >> >> <soap:operation >> >> soapAction="http://www.openuri.org/UpdateCategoriesReq"; style="rpc"/> >> >> <input> >> >> <soap:body use="encoded" namespace="http://www.openuri.org/"; >> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> >> >> </input> >> >> <output> >> >> <soap:body use="encoded" namespace="http://www.openuri.org/"; >> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> >> >> </output> >> >> </operation> >> >> <operation name="BPDataReq"> >> >> <soap:operation soapAction="http://www.openuri.org/BPDataReq"; >> >> style="rpc"/> >> >> <input> >> >> <soap:body use="encoded" namespace="http://www.openuri.org/"; >> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> >> >> </input> >> >> <output> >> >> <soap:body use="encoded" namespace="http://www.openuri.org/"; >> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> >> >> </output> >> >> </operation> >> >> ...... >> >> </binding> >> >> >> >> I know that rpc/encoded is not supported in WS-I basic profile but >> this >> >> WSDL >> >> was developed some time ago and is used in production so I'm not sure >> >> whether I will be allowed to modify. If I'm allowed to modify it what >> >> will >> >> be the best way to do it so Axis2 1.2's wsdl2java will not throw >> errors? >> >> >> >> Thanks. >> >> Stefan >> >> >> >> >> >> >I believe we are throwing better exceptions now...if you post the >> wsdl >> >> >in a bug report, we can take a look to confirm that it is indeed an >> >> >rpc/encoded wsdl which we don't support. >> >> > >> >> >thanks, >> >> >dims >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10312820 >> >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> > -- >> > Davanum Srinivas :: http://davanum.wordpress.com >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10341325 >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Davanum Srinivas :: http://davanum.wordpress.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10342010 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
