I have to disagree with you -- at least if your goal is interoperability. XML is the external interface to your service, and it's a useful practice to maintain a clean separation of concern between your interface and your implementation. I trust you recognize the value of clean separation between your application object model and a database data model and the DAO design pattern. The same benefits exist when maintaining the separation between your externally facing XML model and your internal object model.
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. 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. Anne On 5/25/07, Jarek Kucypera <[EMAIL PROTECTED]> wrote:
Dennis Sosnoski wrote: > I haven't tried out the Axis2 POJO support, but in general anything > you do using POJOs directly is going to be both inflexible and very > limited in terms of the XML support. With all respect, xml here is the tool, not the purpose. I would like to expose my serwice without any knowlege of wsdl and xml and focus just on the bussiness logic, even for the price of not utilizng all the features of xml. Even with axis2 1.2 it's hardly possible. 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]
