Open Source WS Stacks for Java - Design Goals and Philosophy

Archived Content
This article is provided for historical perspective only, and may not reflect current conditions. Please refer to relevant product page for more up-to-date product information and resources.
  • By Paul Fremantle
  • 8 Oct, 2007
  • Can you describe the main design goals of "your" framework? What do you perceive as its main strengths and unique features?
  • What's your position on and the framework's support for JCP standards such as JAX-WS, JAX-RPC, JAXM, JAXB? Why is support for it included/not included?
  • What Web services standards do you support, and why are those you don't support not supported (i.e. do you plan to include them later, not at all, ...)
  • What's your position with regards to data binding and the problems many people associate with it? Do you support native access to the XML message, an XML/object mapping, or both?
  • How well do you support interoperability with other WS implementations, particularly .NET/WCF?
  • What is your position with regards to REST? Do you offer any kind of REST support?
  • What is your framework's maturity? Are there any case studies you can point to, are there any commercial or open source products that rely on it?

Read what they had to say about each of the products...


About Author

  • Paul Fremantle
  • Co-Founder & CTO
  • WSO2