One advantage of JAX-WS is that it is portable to other web service stacks, primarily GlassFish Metro.
Glen kpalania wrote: > > I've started out using the Simple Frontend and it seems super-easy to > expose existing APIs as web services with absolutely no annotations and/or > WSDLs. Given this, it seems like a no-brainer to take this approach as > opposed to using the JAX-WS Frontend. But, it can't be true, and I am > clearly missing some pros of the JAX-WS approach. > > Would someone mind clarifying? When should we use one versus the other? > -- View this message in context: http://www.nabble.com/JAX-WS-Frontend-vs-Simple-Frontend-tp19771467p19781834.html Sent from the cxf-user mailing list archive at Nabble.com.
