We chose WebService because it most fit our development model of programming to an internal API, then using tools to expose the API to a specific transport. We use CXF-WS, CXF-RS, some AMF adapters, etc. If you are comfortable with API programming, this may be the route for you as well.
If you need the low-level access to transport message details, and don't mind being tied to CXF, then WebServiceProvider may be what you are looking for. Again, I would recommend accessing the transport details through the interceptors and stick to programming to a custom API for your domain-specific stuff as an initial approach. $.02; please take with a grain of salt :) On Aug 14, 2013, at 4:49 PM, blipsman <b_lips...@yahoo.com> wrote: > 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 archive at Nabble.com.
