It looks like jaxws:endpoint does now support the jaxws:dataBinding according to the schema.
Does this mean that there is no difference, other than personal preference, between the two approaches? Are there plans to make the two approaches diverge in the future? - Eric Johnson Principle Technical Writer MII-KS, FUSE Progress Software Corporation -----Original Message----- From: Ian Roberts <[EMAIL PROTECTED]> Reply-To: [email protected] To: [email protected] Subject: Re: jaxws:endpoint vs. jaxws;server Date: Fri, 17 Oct 2008 17:13:15 +0100 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? I haven't noticed any difference in behaviour or expressivity between the two approaches, other than the cosmetic difference that jaxws:server uses serviceClass and serviceBean whereas jaxws:endpoint uses implementorClass and implementor. I wonder if they might diverge in future though - looking at the code EndpointImpl.publish already does a bit more than just JaxWsServerFactoryBean.create. I tend to use jaxws:server myself simply because I once ran into a case where I needed to specify a custom data binding object, and this was easier with jaxws:server which supported a nested jaxws:dataBinding tag whereas jaxws:endpoint didn't (for all I know it might now, but it didn't in the version I was using at the time). Ian
