Jarek Kucypera 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.

I understand your goal and I'm not unsympathetic. Certainly the POJO support in Axis2 could do a better job than it apparently does of handling some of these cases (such as the 0-length array example which was the topic of this thread). But generally the idea of deploying POJOs directly is a very limited approach, at best only suitable for small applications, and if you're doing anything substantial you're probably going to need to start controlling the XML conversions at some point. That's where either JiBX or JAXB 2.0 can help, since they both allow basically POJO objects to be converted to and from XML without the limitations of direct-from-POJO approaches.

If you're really determined to work directly with POJOs and don't care about the XML and WSDL, the original Axis may be a better alternative for you than Axis2. Axis supports the rpc/enc style which provides the best support for direct use of POJOs in web services. But note that you'll lose interoperability by going with rpc/enc, which pretty much defeats the whole idea of making something a web service. This style has been deprecated in newer frameworks largely due to the limitations, and Axis2 does not support rpc/enc at all.

 - Dennis

--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to