Oh, OK, if it's not really needed to be in compliance with anything we can remove/deprecate it.
Glen dkulp wrote: > > > The XML binding is separate from the HTTP binding. The HTTP binding is > the > first "REST" stuff that was in CXF based on the JRA annotations. > > The XML binding is the thing that does the XML/HTTP stuff required by the > JAX-WS spec. > > That said, I would say deprecate for 2.2 unless we can get a client side > API > for the JAX-RS stuff. > > Dan > > > On Tuesday 20 January 2009 2:27:20 pm Glen Mazza wrote: >> I don't think we can do this and still remain a JAX-WS implementation. >> According to the JAX 2.1 Specification of May 2007, Chapter 11.1 (HTTP >> Binding--Configuration), it says: >> >> "Conformance (XML/HTTP Binding Support): An implementation MUST support >> the >> XML/HTTP binding." >> >> Perhaps we can wait a bit until a future JAX-WS spec drops this >> requirement, due to the growth of REST web services. In the interim, you >> might wish to send an email to the JSR-224 group asking them to make this >> optional. >> >> Glen >> >> Sergey Beryozkin-3 wrote: >> > Hi, >> > >> > I'd like to propose to have CXF HTTP Binding deprecated for the >> following >> > reasons : >> > >> > 1. It's not mantained at all >> > 2. CXF implements JAXRS which offers superior options toward building >> > restful services >> > 3. It adds to the overall build time and distribution size >> > >> > More specifically, I'd like to suggest that we formally declare it >> being >> > deprecated when 2.2 is released >> > which will give us an option to eventually remove it from the trunk, >> once >> > we have the proper client api support. >> > >> > Thoughts ? >> > >> > Cheers, Sergey > > > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog > > -- View this message in context: http://www.nabble.com/Proposal-to-deprecate-CXF-HTTP-Binding-tp21566458p21571371.html Sent from the cxf-dev mailing list archive at Nabble.com.
