If your goal is point-to-point integration between a single client and server, then the code-first development model is fine. But if your goal is to implement a service-oriented system, enable reuse of capabilities, reduce redundancy, and increase flexibility and agility, then the code-first development model is a bad practice.
Service-oriented systems require governance of data types and semantics. I'm sure you've noticed that if you use the code-first approach, then Axis will generate a unique set of types and namespaces for your application. Proliferation of schema types will make reuse extremely challenging, resulting in reduced flexibility and agility, and a complete failure of a SOA initiative. Saving a little bit of time during development sometimes results in massive longterm headaches. Anne On 6/12/07, Jarek Kucypera <[EMAIL PROTECTED]> wrote:
Anne Thomas Manes wrote: > I trust you recognize > the value of clean separation between your application object model > and a database data model and the DAO design pattern. Of course I do. My point is that I wanna write the interface layer of my system in Java, not int WSDL, of course for the price of not using all of the wsdl/schema/xml features. Actually we are doing it in our current project: we created core engine for the business logic and a separate,thin interface layer. The interface is simple enaugh to write it as a set of of beans and service classes whose only task is to translate params/ results and call the core. Due to simplicity of the interface and the fact we don't need any of additional ws features like addressing, reasonable POJO support just fits this scenario. > There is an impedance mismatch between XML data structures and Java > object models, just as there is an impedance mismatch between SQL data > models and Java object models. In many cases the mismatch is > insignificant, but it's a bad idea to assume that it doesn't exist. > Noone does assume that. And in those "many cases" it's worth to pay the price of simplicity to avoid diving into wsdl. > I agree that Axis2 could handle POJO deployment better, but even if it > were the best that it could be, I seriously doubt that it could handle > everything automatically. I don't expect POJO to handle everything,. But reasonable propagation of exceptions is a minimum for it to be usable. J.K. --------------------------------------------------------------------- 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]
