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 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
