Re: [Axis2] - upgrading from [Axis1.3]
The Axis2 Code Generation Tool Reference has a sample WSDL using soap 1.1 and doc / lit . http://ws.apache.org/axis2/CodegenToolReference.html AFAIK, your choices are 'rpc literal' and 'doc literal' using axis2 at the present time, ie, not rpc encoded. HTH, iksrazal Em Sexta 09 Dezembro 2005 04:26, o Simon McMahon escreveu: Hi, Looks to me like Axis2 is geared more for message passing than RPC which Axis 1.x handled very well. Axis2 obviously has other features that Axis 1.3 doesn't but my existing services work best as RPC. Well, at least I could get it to work. It also looks like you need to know AXIOM pretty well to use Axis 2. I think I have to wait for some more Axis2 examples and 1.x backwards compatibility before I can migrate successfully. Thanks, Simon. Simon McMahon Work: (07) 31311420 Mobile: (043) 2294180 [EMAIL PROTECTED] 12/08/05 03:38pm Forwarding to the list. It was my fault to hit reply and send only to Simon. I am not sure of the Java2WSDL satus right now. May be ajith would know better. Chathura On 12/8/05, Simon McMahon [EMAIL PROTECTED] wrote: Thanks for your time to look into it. I thought my change to the wsdl was too dumb to work but if I keep hacking my wsdl file without understanding what I am doing I am most likely going to wreck it. In the schema section I changed the soapens:string to xsd:string but I dont know how to convert the array types. Is there more documentation that I should be looking into or some other way? The only wsdl sample is Axis2SampleDocLit.wsdl. As I understand there is no Java2WSDL for Axis2 (yet). Sorry to keep with new questions but I'm a bit lost with what to try next... Surely people dont create wsdl by hand so where do Axis2 compliant wsdls come from? How do I start from just a class (.java) and build the wsdl, server client for Axis2 like I did with Axis 1.3 (1.2 when I started)? If Web Services are to be interoperable - i.e. a Axis2 client using an Axis 1.3 server - how come the WSDL doesn't work as is? Is this just a question of time to finish Axis2 ? Regards, Simon. Simon McMahon Work: (07) 31311420 Mobile: (043) 2294180 Chathura Herath [EMAIL PROTECTED] 12/08/05 02:39pm I am sorry that wouldnt work. You need to get rid of all the soapenc: types in the schema section. We use xml beans for databingding it cannot handle soap encoding. Though you have simply change the use from thm encoded to literal the semantic description of your data in schema is still SOAP encoded. Chathura On 12/7/05, Simon McMahon [EMAIL PROTECTED] wrote: Original WSDL and edited are attached. The original was generated by Axis 1.3. All I did was substitute encoded for literal and changed nothing else. My understanding of all this is pretty limited although I got my Axis 1.3 service and client to work OK. Your help is most appreciated. Cheers, Simon. Simon McMahon Work: (07) 31311420 Mobile: (043) 2294180 [EMAIL PROTECTED] 12/08/05 01:56pm Doesn't seem right. Pls attach the edited WSDL. Literal means the type is fully described by schema: Encoded mean the semantics of encoding applies. If its SOAP encoding then the semantics of SOAP encoding is used other than xsd type. Chathura On 12/7/05, Simon McMahon [EMAIL PROTECTED] wrote: Hi again, I hacked up my Axis 1.3 generated wsdl and changed all wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=urn:qh use=encoded/ to wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=urn:qh use=literal/ based on the WSDL2Java error : java.lang.RuntimeException: The use 'encoded' is not supported! I have no idea what that means but now WSDL2Java runs to completion and generates a whole bunch of files. What is the difference between encoded and literal? Why is all the standard 'databinding' source plugged into my package ? Surely this will bloat the size of every web service. Also, my original Service method: public Provider[] getProvider(String name, String providerId, String orgName, String locationId, int maxResults) throws Exception became: /** * Auto generated method signatures * @param param68 */ public org.apache.axis2.om.OMElement getProvider( org.apache.axis2.om.OMElement param68) throws java.rmi.RemoteException; The only bit that stayed the same is the method name. How can the stub/skeleton for the same web service be so different? Is there more I need to do to the WSDL to make it generate a proper interface and skeleton service?
Re: [Axis2] - upgrading from [Axis1.3]
Hi Chathura and all; I have done java2wsdl stuff using JAM (rather than using Java repletion directly do generate XML schema), but I have to test that well before releasing any way that there in o.a.a.w.a package. Thanks, Deepal ~Future is Open~ - Original Message - From: Chathura Herath [EMAIL PROTECTED] To: axis-user@ws.apache.org; Ajith Ranabahu [EMAIL PROTECTED] Sent: Thursday, December 08, 2005 11:38 AM Subject: Re: [Axis2] - upgrading from [Axis1.3] Forwarding to the list. It was my fault to hit reply and send only to Simon. I am not sure of the Java2WSDL satus right now. May be ajith would know better. Chathura On 12/8/05, Simon McMahon [EMAIL PROTECTED] wrote: Thanks for your time to look into it. I thought my change to the wsdl was too dumb to work but if I keep hacking my wsdl file without understanding what I am doing I am most likely going to wreck it. In the schema section I changed the soapens:string to xsd:string but I dont know how to convert the array types. Is there more documentation that I should be looking into or some other way? The only wsdl sample is Axis2SampleDocLit.wsdl. As I understand there is no Java2WSDL for Axis2 (yet). Sorry to keep with new questions but I'm a bit lost with what to try next... Surely people dont create wsdl by hand so where do Axis2 compliant wsdls come from? How do I start from just a class (.java) and build the wsdl, server client for Axis2 like I did with Axis 1.3 (1.2 when I started)? If Web Services are to be interoperable - i.e. a Axis2 client using an Axis 1.3 server - how come the WSDL doesn't work as is? Is this just a question of time to finish Axis2 ? Regards, Simon. Simon McMahon Work: (07) 31311420 Mobile: (043) 2294180 Chathura Herath [EMAIL PROTECTED] 12/08/05 02:39pm I am sorry that wouldnt work. You need to get rid of all the soapenc: types in the schema section. We use xml beans for databingding it cannot handle soap encoding. Though you have simply change the use from thm encoded to literal the semantic description of your data in schema is still SOAP encoded. Chathura On 12/7/05, Simon McMahon [EMAIL PROTECTED] wrote: Original WSDL and edited are attached. The original was generated by Axis 1.3. All I did was substitute encoded for literal and changed nothing else. My understanding of all this is pretty limited although I got my Axis 1.3 service and client to work OK. Your help is most appreciated. Cheers, Simon. Simon McMahon Work: (07) 31311420 Mobile: (043) 2294180 [EMAIL PROTECTED] 12/08/05 01:56pm Doesn't seem right. Pls attach the edited WSDL. Literal means the type is fully described by schema: Encoded mean the semantics of encoding applies. If its SOAP encoding then the semantics of SOAP encoding is used other than xsd type. Chathura On 12/7/05, Simon McMahon [EMAIL PROTECTED] wrote: Hi again, I hacked up my Axis 1.3 generated wsdl and changed all wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=urn:qh use=encoded/ to wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=urn:qh use=literal/ based on the WSDL2Java error : java.lang.RuntimeException: The use 'encoded' is not supported! I have no idea what that means but now WSDL2Java runs to completion and generates a whole bunch of files. What is the difference between encoded and literal? Why is all the standard 'databinding' source plugged into my package ? Surely this will bloat the size of every web service. Also, my original Service method: public Provider[] getProvider(String name, String providerId, String orgName, String locationId, int maxResults) throws Exception became: /** * Auto generated method signatures * @param param68 */ public org.apache.axis2.om.OMElement getProvider( org.apache.axis2.om.OMElement param68) throws java.rmi.RemoteException; The only bit that stayed the same is the method name. How can the stub/skeleton for the same web service be so different? Is there more I need to do to the WSDL to make it generate a proper interface and skeleton service? Regards, Simon. Simon McMahon Work: (07) 31311420 Mobile: (043) 2294180 [EMAIL PROTECTED] 12/07/05 04:29pm That would be it - all the samples use services.xml. The documentation is correct on this too. Must just have been M2 that got it wrong (or just me :). Blind guess. Check whether the dir of the aar name is META-INF. meta-inf might not work Chathura This was also correct - meta-inf did not work either. It was tough to get right because WinZip shows all UPPERCASE names in lowercase by default. The Axis2 Exception does not include the META-INF part of the name that is obviously significant
Re: [Axis2] - upgrading from [Axis1.3]
Hi, Looks to me like Axis2 is geared more for message passing than RPC which Axis 1.x handled very well. Axis2 obviously has other features that Axis 1.3 doesn't but my existing services work best as RPC. Well, at least I could get it to work. It also looks like you need to know AXIOM pretty well to use Axis 2. I think I have to wait for some more Axis2 examples and 1.x backwards compatibility before I can migrate successfully. Thanks, Simon. Simon McMahon Work: (07) 31311420 Mobile: (043) 2294180 [EMAIL PROTECTED] 12/08/05 03:38pm Forwarding to the list. It was my fault to hit reply and send only to Simon. I am not sure of the Java2WSDL satus right now. May be ajith would know better. Chathura On 12/8/05, Simon McMahon [EMAIL PROTECTED] wrote: Thanks for your time to look into it. I thought my change to the wsdl was too dumb to work but if I keep hacking my wsdl file without understanding what I am doing I am most likely going to wreck it. In the schema section I changed the soapens:string to xsd:string but I dont know how to convert the array types. Is there more documentation that I should be looking into or some other way? The only wsdl sample is Axis2SampleDocLit.wsdl. As I understand there is no Java2WSDL for Axis2 (yet). Sorry to keep with new questions but I'm a bit lost with what to try next... Surely people dont create wsdl by hand so where do Axis2 compliant wsdls come from? How do I start from just a class (.java) and build the wsdl, server client for Axis2 like I did with Axis 1.3 (1.2 when I started)? If Web Services are to be interoperable - i.e. a Axis2 client using an Axis 1.3 server - how come the WSDL doesn't work as is? Is this just a question of time to finish Axis2 ? Regards, Simon. Simon McMahon Work: (07) 31311420 Mobile: (043) 2294180 Chathura Herath [EMAIL PROTECTED] 12/08/05 02:39pm I am sorry that wouldnt work. You need to get rid of all the soapenc: types in the schema section. We use xml beans for databingding it cannot handle soap encoding. Though you have simply change the use from thm encoded to literal the semantic description of your data in schema is still SOAP encoded. Chathura On 12/7/05, Simon McMahon [EMAIL PROTECTED] wrote: Original WSDL and edited are attached. The original was generated by Axis 1.3. All I did was substitute encoded for literal and changed nothing else. My understanding of all this is pretty limited although I got my Axis 1.3 service and client to work OK. Your help is most appreciated. Cheers, Simon. Simon McMahon Work: (07) 31311420 Mobile: (043) 2294180 [EMAIL PROTECTED] 12/08/05 01:56pm Doesn't seem right. Pls attach the edited WSDL. Literal means the type is fully described by schema: Encoded mean the semantics of encoding applies. If its SOAP encoding then the semantics of SOAP encoding is used other than xsd type. Chathura On 12/7/05, Simon McMahon [EMAIL PROTECTED] wrote: Hi again, I hacked up my Axis 1.3 generated wsdl and changed all wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=urn:qh use=encoded/ to wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=urn:qh use=literal/ based on the WSDL2Java error : java.lang.RuntimeException: The use 'encoded' is not supported! I have no idea what that means but now WSDL2Java runs to completion and generates a whole bunch of files. What is the difference between encoded and literal? Why is all the standard 'databinding' source plugged into my package ? Surely this will bloat the size of every web service. Also, my original Service method: public Provider[] getProvider(String name, String providerId, String orgName, String locationId, int maxResults) throws Exception became: /** * Auto generated method signatures * @param param68 */ public org.apache.axis2.om.OMElement getProvider( org.apache.axis2.om.OMElement param68) throws java.rmi.RemoteException; The only bit that stayed the same is the method name. How can the stub/skeleton for the same web service be so different? Is there more I need to do to the WSDL to make it generate a proper interface and skeleton service? Regards, Simon. Simon McMahon Work: (07) 31311420 Mobile: (043) 2294180 [EMAIL PROTECTED] 12/07/05 04:29pm That would be it - all the samples use services.xml. The documentation is correct on this too. Must just have been M2 that got it wrong (or just me :). Blind guess. Check whether the dir of the aar name is META-INF. meta-inf might not work Chathura This was also correct - meta-inf did not work either. It was tough to get right because WinZip shows all UPPERCASE names in
