Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There is a misunderstanding here, Jetty and CXF are like apples and oranges, it doesn't make sense to compare them. One is a light servlet engine, the other one is a web services stack. </p> <p>If you're looking for a web services stack (which is my understanding), consider JAX-WS RI or CXF if you are looking for a JAX-WS compliant stack (both support contract-first or java-first), or SpringWS ("only" contract-first), or maybe Axis2 (I don't like it personally it because of its development and deployment model and its performances).</p> <p>If you don't need fancy WS-* stuff, I'd suggest to use JAX-WS RI which is included in Java 6 and is compliant with the WS-I Basic Profile 1.1 (so it covers a decent bunch of WS-* standards). If you need more advanced things (like WS-SecureConversation, WS-SecurityPolicy, WS-ReliableMessaging, WS-Trust, WS-AtomicTransactions/Coordination, WS-MetadataExchange, SOAP over TCP which are provided by WSIT/Tango), consider using Metro (Metro = JAX-WS RI + WSIT/Tango).</p> <p>(EDIT: Answering a comment from the OP about WS-SecureConversation support.</p> <p>Actually, I think that the stack that supports the most WS-* standards is Metro. You might want to check <a href="http://www.predic8.com/axis2-cxf-jax-ws-comparison.htm" rel="nofollow noreferrer">Apache Axis2, CXF and Sun JAX-WS RI in comparison</a> for more details. But, it is very unlikely that you'll need all of them and things might have slightly changed since the article has been published. So CXF might indeed be an alternative. For example, regarding WS-SecureConversation, CXF does support it too according to its <a href="http://cwiki.apache.org/CXF20DOC/ws-secureconversation.html" rel="nofollow noreferrer">documentation</a> but only with "wsdl-first" projects. Without more details about what you're going to do, it's hard to give you a more accurate answer about which one is the best for you.)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload