/WebServiceProvider-or-WebService-tp5732420p5732558.html
Sent from the cxf-user mailing list archive at Nabble.com.
.547215.n5.nabble.com/WebServiceProvider-or-WebService-tp5732418p5732530.html
Sent from the cxf-user mailing list archive at Nabble.com.
ize for my service endpoint:
> -@WebServiceProvider or @WebService
> I do know that @WebServiceProvider limits my web service only to one
> method, etc, invoke()...
> but @WebService I could have many methods
> What are the factors that should affect my decision?
@WebServiceProvi
--
> View this message in context:
> http://cxf.547215.n5.nabble.com/WebServiceProvider-or-WebService-tp5732420p5732458.html
> Sent from the cxf-user mailing list archive at Nabble.com.
Tim, Thanks a bunch for prompt reply...
Still my original question ...Why did you choose WebService instead of
WebServiceProvider?
--
View this message in context:
http://cxf.547215.n5.nabble.com/WebServiceProvider-or-WebService-tp5732420p5732458.html
Sent from the cxf-user mailing list
ng questions:
>
> 1. Which annotation would be preferable to utilize for my service endpoint:
> -@WebServiceProvider or @WebService
> I do know that @WebServiceProvider limits my web service only to one
> method, etc, invoke()...
> but @WebService I could have many methods
>
:
-@WebServiceProvider or @WebService
I do know that @WebServiceProvider limits my web service only to one
method, etc, invoke()...
but @WebService I could have many methods
What are the factors that should affect my decision?
2. As I deal with routing of my soap messages between several web services
and
:
-@WebServiceProvider or @WebService
I do know that @WebServiceProvider limits my web service only to one
method, etc, invoke()...
but @WebService I could have many methods
What are the factors that should affect my decision?
2. As I deal with routing of my soap messages between several web services
and
