On 11/03/13 14:38, Glen Mazza wrote:
It depends on your customer needs, but ideally, no, multiple ways to do
the same thing just adds to administrative headaches and runs the risk
of security holes developing while not adding any additional functionality.
As I've already said before, I see combining JAX-WS + JAX-RS as a nice
way for WS users to either start experimenting with or start gradually
exposing some of their WS backends as RS views, without having to make
the decisions like "we need to completely replace WS with RS or do not
use RS at all".
Then, after that initial effort confirming it may work, and going
forward, it indeed makes sense to simply offer independent
interfaces/endpoints, while still possibly sharing some of the common
code...
Cheers, Sergey
Glen
On 03/09/2013 03:28 AM, srinivas thallapalli wrote:
Hello,
Is it good practice to make the same service as both JAX-WS and RESTful?
Thanks
--
View this message in context:
http://cxf.547215.n5.nabble.com/JAX-WS-and-RESTful-for-same-service-tp5724330.html
Sent from the cxf-user mailing list archive at Nabble.com.
