For the user who has the Xfire using experience, I think they will prefer to use jaxws:server tag. For the JAXWS API fans, jaxws:endpoint will be they first choice.
There are not much difference between the jaxws:endpoint and jaxws:server, since the EndpointImpl is a wrapper class for the JaxWsServerFactoryBean. If you take a look at the their schema[1], you will find jaxws:server is using serviceBean attribute to specify the implementor, and jaxws:endpoint is just using implementor to do that. [1]http://svn.apache.org/repos/asf/cxf/trunk/rt/frontend/jaxws/src/main/resources/schemas/jaxws.xsd Willem Fred Dushin wrote: > Thanks Willem. > > So, from an end-user's perspective, which is preferable? What > advantages are there to using one over the other? When would you use > one, as opposed to the other? > > Thanks, > -Fred > > On Oct 17, 2008, at 12:16 AM, Willem Jiang wrote: > >> First, they are all for the server side configuration. >> >> Second, jaxws:endpoint is coming from JAXWS API, and it is used to >> configure the org.apache.cxf.jaxws.EndpointImpl which extends >> javax.xml.ws.Endpoint. >> >> jaxws:server is for configuring the JaxWsServerFactoryBean, which is >> coming from the Xfire API. >> >> Willem >> >> Eric Johnson wrote: >>> What is the difference between using jaxws:endpoint to configure a >>> service and using jaxws:server? >>> >>> >>> >>> >> > >
