Re: [AXIS2] Which binding framework should i use for complex xml handling
Thanks Anne. As Dims and you suggested, i was successful to write a wsdl, write a schema into the wsdl, then perform wsdl2java, then edit the skeleton to put businesslogic and finally i was able to call the service from a MS Excel Client. Thanks for your help towards this. But, now i have a issue as follows: 1. I have included the schema definition for my elements in wsdl as follows: xs:element name=CUSIP xs:simpleType xs:restriction base=xs:string xs:maxLength value=100/ /xs:restriction /xs:simpleType /xs:element Since im using the simpleType, wsdl2java ABD framework generates individual java classes for each such element. I have 190 + elements, so it creates 190+ java classes. I removed the simpletype for the above cusip and avoided restriction as follows: xs:element name=CUSIP type=xs:string/ Then i cannot see any class created by the wsdl2java for CUSIP. I could see the get/set methods in the parent element class itself. So, my question is: How to avoid creating multiple classes for each element, provided if i want to use restriction based validation? 2. Even though i had put restriction earlier and sent a CUSIP value 100 characters there was no validation fired at the wsdl level. Why is this? Why is that the Schema validation present inside the wsdl not firing? Am i doing something wrong anywhere in the implementation. I have attached the wsdl for reference (located at the end of this thread). Your help towards this would be much appreciable. Thanks, Kiran Kumar. http://www.nabble.com/file/6119/SecurityRequestV2.wsdl SecurityRequestV2.wsdl -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8716986 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Which binding framework should i use for complex xml handling
XML Schema validation is a very expensive process; therefore it is never performed automatically. If you want to validate your messages, you must route your message through an intermediary or module to do so. If you don't intend to validate your messages, then I suggest you remove the restrictions and just use native types. If you define custom types for each element, wsdl2java must create a different Java type for each one. As a general good practice, I encourage you to always name your types (i.e., define a type as a direct child of the schema component, not as a child of an element component.) Anne On 1/30/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Anne. As Dims and you suggested, i was successful to write a wsdl, write a schema into the wsdl, then perform wsdl2java, then edit the skeleton to put businesslogic and finally i was able to call the service from a MS Excel Client. Thanks for your help towards this. But, now i have a issue as follows: 1. I have included the schema definition for my elements in wsdl as follows: xs:element name=CUSIP xs:simpleType xs:restriction base=xs:string xs:maxLength value=100/ /xs:restriction /xs:simpleType /xs:element Since im using the simpleType, wsdl2java ABD framework generates individual java classes for each such element. I have 190 + elements, so it creates 190+ java classes. I removed the simpletype for the above cusip and avoided restriction as follows: xs:element name=CUSIP type=xs:string/ Then i cannot see any class created by the wsdl2java for CUSIP. I could see the get/set methods in the parent element class itself. So, my question is: How to avoid creating multiple classes for each element, provided if i want to use restriction based validation? 2. Even though i had put restriction earlier and sent a CUSIP value 100 characters there was no validation fired at the wsdl level. Why is this? Why is that the Schema validation present inside the wsdl not firing? Am i doing something wrong anywhere in the implementation. I have attached the wsdl for reference (located at the end of this thread). Your help towards this would be much appreciable. Thanks, Kiran Kumar. http://www.nabble.com/file/6119/SecurityRequestV2.wsdl SecurityRequestV2.wsdl -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8716986 Sent from the Axis - User mailing list archive at Nabble.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]
Re: [AXIS2] Which binding framework should i use for complex xml handling
I just looked at your WSDL and noticed a couple of things. Most of your elements are defined as restricted strings of lengths 20, 50, or 100. If you want to be able to support validation of these element, you could defining three simple types with these restrictions, then define the elements as the appropriate type. More more note: when using document style, your soap:body and soap12:body definitions in the binding MUST NOT include the namespace attribute. That attribute is used only with RPC style. They should look like this: soap:body use=literal/ soap12:body use=literal/ Anne On 1/30/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: XML Schema validation is a very expensive process; therefore it is never performed automatically. If you want to validate your messages, you must route your message through an intermediary or module to do so. If you don't intend to validate your messages, then I suggest you remove the restrictions and just use native types. If you define custom types for each element, wsdl2java must create a different Java type for each one. As a general good practice, I encourage you to always name your types (i.e., define a type as a direct child of the schema component, not as a child of an element component.) Anne On 1/30/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Anne. As Dims and you suggested, i was successful to write a wsdl, write a schema into the wsdl, then perform wsdl2java, then edit the skeleton to put businesslogic and finally i was able to call the service from a MS Excel Client. Thanks for your help towards this. But, now i have a issue as follows: 1. I have included the schema definition for my elements in wsdl as follows: xs:element name=CUSIP xs:simpleType xs:restriction base=xs:string xs:maxLength value=100/ /xs:restriction /xs:simpleType /xs:element Since im using the simpleType, wsdl2java ABD framework generates individual java classes for each such element. I have 190 + elements, so it creates 190+ java classes. I removed the simpletype for the above cusip and avoided restriction as follows: xs:element name=CUSIP type=xs:string/ Then i cannot see any class created by the wsdl2java for CUSIP. I could see the get/set methods in the parent element class itself. So, my question is: How to avoid creating multiple classes for each element, provided if i want to use restriction based validation? 2. Even though i had put restriction earlier and sent a CUSIP value 100 characters there was no validation fired at the wsdl level. Why is this? Why is that the Schema validation present inside the wsdl not firing? Am i doing something wrong anywhere in the implementation. I have attached the wsdl for reference (located at the end of this thread). Your help towards this would be much appreciable. Thanks, Kiran Kumar. http://www.nabble.com/file/6119/SecurityRequestV2.wsdl SecurityRequestV2.wsdl -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8716986 Sent from the Axis - User mailing list archive at Nabble.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]
Re: [AXIS2] Which binding framework should i use for complex xml handling
If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Which binding framework should i use for complex xml handling
Thanks Davanum Srinivas for your response. OK, you advise to start from WSDL rather than java/pojo's. I got two questions: 1. But, does that mean we have to prepare a WSDL on our own first and then start off. Sorry, if this question is silly. I am new to this axis world. 2. I would have a big xml data with complicated schema. So using xmlbeans would work fine means, which one is stable to use xmlbeans AXIS1.4 or AXIS2. Thanks, Kiran kumar. Davanum Srinivas wrote: If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8695199 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Which binding framework should i use for complex xml handling
#1) Yes. Start with Schema first (i use XMLSPY to write xsd's). Then follow instructions from Anne here to fill up the template WSDL. #2) Axis2 w/o a doubt. thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Davanum Srinivas for your response. OK, you advise to start from WSDL rather than java/pojo's. I got two questions: 1. But, does that mean we have to prepare a WSDL on our own first and then start off. Sorry, if this question is silly. I am new to this axis world. 2. I would have a big xml data with complicated schema. So using xmlbeans would work fine means, which one is stable to use xmlbeans AXIS1.4 or AXIS2. Thanks, Kiran kumar. Davanum Srinivas wrote: If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8695199 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Which binding framework should i use for complex xml handling
oops forgot the link: http://mail-archives.apache.org/mod_mbox/ws-axis-user/200609.mbox/[EMAIL PROTECTED] -- dims On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: #1) Yes. Start with Schema first (i use XMLSPY to write xsd's). Then follow instructions from Anne here to fill up the template WSDL. #2) Axis2 w/o a doubt. thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Davanum Srinivas for your response. OK, you advise to start from WSDL rather than java/pojo's. I got two questions: 1. But, does that mean we have to prepare a WSDL on our own first and then start off. Sorry, if this question is silly. I am new to this axis world. 2. I would have a big xml data with complicated schema. So using xmlbeans would work fine means, which one is stable to use xmlbeans AXIS1.4 or AXIS2. Thanks, Kiran kumar. Davanum Srinivas wrote: If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8695199 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://wso2.org/ :: Oxygen for Web Services Developers -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Which binding framework should i use for complex xml handling
As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). Sorry for chipping into this thread with an unrelated question, but wanted to know why you say that Is that because axis2 has less good features for pojo services? I had read some articles early on when I was jumping into this, that didnt advocate for either approach. Thanks, Sathija. oops forgot the link: http://mail-archives.apache.org/mod_mbox/ws-axis-user/200609.mbox/[EMAIL PROTECTED] -- dims On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: #1) Yes. Start with Schema first (i use XMLSPY to write xsd's). Then follow instructions from Anne here to fill up the template WSDL. #2) Axis2 w/o a doubt. thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Davanum Srinivas for your response. OK, you advise to start from WSDL rather than java/pojo's. I got two questions: 1. But, does that mean we have to prepare a WSDL on our own first and then start off. Sorry, if this question is silly. I am new to this axis world. 2. I would have a big xml data with complicated schema. So using xmlbeans would work fine means, which one is stable to use xmlbeans AXIS1.4 or AXIS2. Thanks, Kiran kumar. Davanum Srinivas wrote: If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8695199 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://wso2.org/ :: Oxygen for Web Services Developers -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - 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]
Re: [AXIS2] Which binding framework should i use for complex xml handling
That's the best practice i recommend from experience. Advice not related to whether you use Axis2 or not. thanks, dims On 1/29/07, Sathija Pavuluri [EMAIL PROTECTED] wrote: As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). Sorry for chipping into this thread with an unrelated question, but wanted to know why you say that Is that because axis2 has less good features for pojo services? I had read some articles early on when I was jumping into this, that didnt advocate for either approach. Thanks, Sathija. oops forgot the link: http://mail-archives.apache.org/mod_mbox/ws-axis-user/200609.mbox/[EMAIL PROTECTED] -- dims On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: #1) Yes. Start with Schema first (i use XMLSPY to write xsd's). Then follow instructions from Anne here to fill up the template WSDL. #2) Axis2 w/o a doubt. thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Davanum Srinivas for your response. OK, you advise to start from WSDL rather than java/pojo's. I got two questions: 1. But, does that mean we have to prepare a WSDL on our own first and then start off. Sorry, if this question is silly. I am new to this axis world. 2. I would have a big xml data with complicated schema. So using xmlbeans would work fine means, which one is stable to use xmlbeans AXIS1.4 or AXIS2. Thanks, Kiran kumar. Davanum Srinivas wrote: If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8695199 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://wso2.org/ :: Oxygen for Web Services Developers -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - 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] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Which binding framework should i use for complex xml handling
Davanum, This method of preparing a schema and then wsdl, then using ADB/XMLBEANS is Document/Literal only right. Also, i guess only Doc/Lit wrapped is interoperable to transfer huge amount of xml data inbuilt inside the soap body. Please correct me, if am wrong. Thanks. kiran. Davanum Srinivas wrote: oops forgot the link: http://mail-archives.apache.org/mod_mbox/ws-axis-user/200609.mbox/[EMAIL PROTECTED] -- dims On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: #1) Yes. Start with Schema first (i use XMLSPY to write xsd's). Then follow instructions from Anne here to fill up the template WSDL. #2) Axis2 w/o a doubt. thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Davanum Srinivas for your response. OK, you advise to start from WSDL rather than java/pojo's. I got two questions: 1. But, does that mean we have to prepare a WSDL on our own first and then start off. Sorry, if this question is silly. I am new to this axis world. 2. I would have a big xml data with complicated schema. So using xmlbeans would work fine means, which one is stable to use xmlbeans AXIS1.4 or AXIS2. Thanks, Kiran kumar. Davanum Srinivas wrote: If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8695199 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://wso2.org/ :: Oxygen for Web Services Developers -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8696783 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Which binding framework should i use for complex xml handling
Kiran, Please read this: http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html Wrapped is a convention used when writing doc/lit wsdl's. There is no difference in the amount of payload. thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Davanum, This method of preparing a schema and then wsdl, then using ADB/XMLBEANS is Document/Literal only right. Also, i guess only Doc/Lit wrapped is interoperable to transfer huge amount of xml data inbuilt inside the soap body. Please correct me, if am wrong. Thanks. kiran. Davanum Srinivas wrote: oops forgot the link: http://mail-archives.apache.org/mod_mbox/ws-axis-user/200609.mbox/[EMAIL PROTECTED] -- dims On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: #1) Yes. Start with Schema first (i use XMLSPY to write xsd's). Then follow instructions from Anne here to fill up the template WSDL. #2) Axis2 w/o a doubt. thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Davanum Srinivas for your response. OK, you advise to start from WSDL rather than java/pojo's. I got two questions: 1. But, does that mean we have to prepare a WSDL on our own first and then start off. Sorry, if this question is silly. I am new to this axis world. 2. I would have a big xml data with complicated schema. So using xmlbeans would work fine means, which one is stable to use xmlbeans AXIS1.4 or AXIS2. Thanks, Kiran kumar. Davanum Srinivas wrote: If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8695199 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://wso2.org/ :: Oxygen for Web Services Developers -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8696783 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Which binding framework should i use for complex xml handling
I heartily concur with Dims. If you plan to use the same framework on both client and server, then you will probably get by very well by following the code-first approach. But if you will ever have the need to interoperate with other frameworks, you'll do much better adopting a Schema-first approach. Also keep in mind that the code-first approach should be used only for application integration. It is not an appropriate means to achieve SOA. SOA is all about reuse. And it involve reuse not just of application functionality, but also of data structures. The fundamental unit of reuse is the XML types that your applications and services share. If you use the code-first approach, then you will generate a different set of XML types for every service. If you have two services that work with customer data, you will generate two incompatible customer types. That is absolutely what you don't want to do. Your organization should define a set of common shared types that represent your core information structures, and your service interfaces should share these structures. You should not generate these structures from code. Anne On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: That's the best practice i recommend from experience. Advice not related to whether you use Axis2 or not. thanks, dims On 1/29/07, Sathija Pavuluri [EMAIL PROTECTED] wrote: As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). Sorry for chipping into this thread with an unrelated question, but wanted to know why you say that Is that because axis2 has less good features for pojo services? I had read some articles early on when I was jumping into this, that didnt advocate for either approach. Thanks, Sathija. oops forgot the link: http://mail-archives.apache.org/mod_mbox/ws-axis-user/200609.mbox/[EMAIL PROTECTED] -- dims On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: #1) Yes. Start with Schema first (i use XMLSPY to write xsd's). Then follow instructions from Anne here to fill up the template WSDL. #2) Axis2 w/o a doubt. thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Davanum Srinivas for your response. OK, you advise to start from WSDL rather than java/pojo's. I got two questions: 1. But, does that mean we have to prepare a WSDL on our own first and then start off. Sorry, if this question is silly. I am new to this axis world. 2. I would have a big xml data with complicated schema. So using xmlbeans would work fine means, which one is stable to use xmlbeans AXIS1.4 or AXIS2. Thanks, Kiran kumar. Davanum Srinivas wrote: If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8695199 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://wso2.org/ :: Oxygen for Web Services Developers -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL
Re: [AXIS2] Which binding framework should i use for complex xml handling
Hi Anne, Thanks for your expert advice. Will follow the same, first design a schema then wsdl. Then generate the ADB binding classes using wsdl2java tool. I am working on it and now i got one question: Instead of importing the XSD into the wsdl, i can even write the schema definition into the xs:schema of wsdl right? Thanks, Kiran Kumar. Anne Thomas Manes wrote: I heartily concur with Dims. If you plan to use the same framework on both client and server, then you will probably get by very well by following the code-first approach. But if you will ever have the need to interoperate with other frameworks, you'll do much better adopting a Schema-first approach. Also keep in mind that the code-first approach should be used only for application integration. It is not an appropriate means to achieve SOA. SOA is all about reuse. And it involve reuse not just of application functionality, but also of data structures. The fundamental unit of reuse is the XML types that your applications and services share. If you use the code-first approach, then you will generate a different set of XML types for every service. If you have two services that work with customer data, you will generate two incompatible customer types. That is absolutely what you don't want to do. Your organization should define a set of common shared types that represent your core information structures, and your service interfaces should share these structures. You should not generate these structures from code. Anne On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: That's the best practice i recommend from experience. Advice not related to whether you use Axis2 or not. thanks, dims On 1/29/07, Sathija Pavuluri [EMAIL PROTECTED] wrote: As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). Sorry for chipping into this thread with an unrelated question, but wanted to know why you say that Is that because axis2 has less good features for pojo services? I had read some articles early on when I was jumping into this, that didnt advocate for either approach. Thanks, Sathija. oops forgot the link: http://mail-archives.apache.org/mod_mbox/ws-axis-user/200609.mbox/[EMAIL PROTECTED] -- dims On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: #1) Yes. Start with Schema first (i use XMLSPY to write xsd's). Then follow instructions from Anne here to fill up the template WSDL. #2) Axis2 w/o a doubt. thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Davanum Srinivas for your response. OK, you advise to start from WSDL rather than java/pojo's. I got two questions: 1. But, does that mean we have to prepare a WSDL on our own first and then start off. Sorry, if this question is silly. I am new to this axis world. 2. I would have a big xml data with complicated schema. So using xmlbeans would work fine means, which one is stable to use xmlbeans AXIS1.4 or AXIS2. Thanks, Kiran kumar. Davanum Srinivas wrote: If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8695199 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Which binding framework should i use for complex xml handling
yes, you can. On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi Anne, Thanks for your expert advice. Will follow the same, first design a schema then wsdl. Then generate the ADB binding classes using wsdl2java tool. I am working on it and now i got one question: Instead of importing the XSD into the wsdl, i can even write the schema definition into the xs:schema of wsdl right? Thanks, Kiran Kumar. Anne Thomas Manes wrote: I heartily concur with Dims. If you plan to use the same framework on both client and server, then you will probably get by very well by following the code-first approach. But if you will ever have the need to interoperate with other frameworks, you'll do much better adopting a Schema-first approach. Also keep in mind that the code-first approach should be used only for application integration. It is not an appropriate means to achieve SOA. SOA is all about reuse. And it involve reuse not just of application functionality, but also of data structures. The fundamental unit of reuse is the XML types that your applications and services share. If you use the code-first approach, then you will generate a different set of XML types for every service. If you have two services that work with customer data, you will generate two incompatible customer types. That is absolutely what you don't want to do. Your organization should define a set of common shared types that represent your core information structures, and your service interfaces should share these structures. You should not generate these structures from code. Anne On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: That's the best practice i recommend from experience. Advice not related to whether you use Axis2 or not. thanks, dims On 1/29/07, Sathija Pavuluri [EMAIL PROTECTED] wrote: As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). Sorry for chipping into this thread with an unrelated question, but wanted to know why you say that Is that because axis2 has less good features for pojo services? I had read some articles early on when I was jumping into this, that didnt advocate for either approach. Thanks, Sathija. oops forgot the link: http://mail-archives.apache.org/mod_mbox/ws-axis-user/200609.mbox/[EMAIL PROTECTED] -- dims On 1/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: #1) Yes. Start with Schema first (i use XMLSPY to write xsd's). Then follow instructions from Anne here to fill up the template WSDL. #2) Axis2 w/o a doubt. thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Thanks Davanum Srinivas for your response. OK, you advise to start from WSDL rather than java/pojo's. I got two questions: 1. But, does that mean we have to prepare a WSDL on our own first and then start off. Sorry, if this question is silly. I am new to this axis world. 2. I would have a big xml data with complicated schema. So using xmlbeans would work fine means, which one is stable to use xmlbeans AXIS1.4 or AXIS2. Thanks, Kiran kumar. Davanum Srinivas wrote: If you have a complicated schema, you should use xmlbeans. If you are willing to sacrifice a bit of schema support for better performance, use ADB. As i mention usually, start from WSDL/Schema. (NOT from java/pojo's). thanks, dims On 1/29/07, mvkirankumar [EMAIL PROTECTED] wrote: Hi, Please suggest me with the following: Which xml java binding framework should i use or which one is stable to use. I have tried AXIOM sample, jibx both do not work. Only the samples given in axis2 works. if i try out something, they do not work. Please help me, to take up a robust framework to implement in my project. thanks kiran kumar. -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8694267 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://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-AXIS2--Which-binding-framework-should-i-use-for-complex-xml-handling-tf3137320.html#a8695199 Sent from the Axis - User mailing list archive at Nabble.com.
