Hi Boris, Comments inline below ...
On Aug 14, 2013, at 10:49 AM, blipsman <b_lips...@yahoo.com> wrote: > Hi all, > I would appreciate any suggestion regarding my question. I just started > learning CXF with some knowledge of Maven And Spring Framework... > Trying to make decision about the following 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.... > What are the factors that should affect my decision? We jumped on CXF-WS as a stop-gap, did not spend too much time on it and have not had to modify that part of our system for a long while. That said, we've been using @WebService in the wild for a few years now, with no problems from a maintenance standpoint. > > 2. As I deal with routing of my soap messages between several web services > and clients, I need to modify my original soap envelope, by adding new > nodes, and doing other things, such as displaying some data that defined and > determined dynamically. As I read Glen Mazza JAX-WS handlers and CXF > interceptors, I realize that maybe I could use them instead XSLT > transformation to modify my soap envelope. I've had some very bad experiences with XSLT in several situations. If you can avoid it, I'd recommend doing so. CXF interceptors are probably more in the direction you're looking for, allowing you to chain lots of small transformations together rather than writing a big all-in-one-go thing. > Any suggestions are really appreciated!! I can heartily recommend CXF's JAX-RS implementation, using Jackson for JSON ser/deser. Very clean stack, if you have the luxury of a green field :) -- Tim > Boris > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/WebServiceProvider-or-WebService-tp5732420.html > Sent from the cxf-user mailing list archive at Nabble.com.
