Should work fine, but won't be a high-performance solution.
We decided to use Axis (1.1) with Castor since it was really easy using this approach (but also not a high-performance solution):
http://www-106.ibm.com/developerworks/webservices/library/ws-castor/
These articles were useful in understanding the options and their performance implications (this link is to Part 1, and it contains links to the other Parts):
http://www-106.ibm.com/developerworks/library/x-databdopt/index.html
The author of those articles also did a few interesting talks that are available online at JavaLobby (free registration required):
http://javalobby.org/av/javapolis/
Wierenga, R. - SPLXE wrote:
Hi,
I want to offer and consume a document/literal type webservice using jaxb as
the serialization mechanism. This is supposed to run in a websphere 4.0.x
environment.
Question 1. is this feasible? Question 2. should I use Axis 1.1 or 1.2? Question 3. Any pitfalls which i should be aware of?
Kind Regards, Robin Wierenga, Accenture
