You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Sergey Beryozkin <se...@progress.com> on 2009/01/20 17:21:30 UTC
Proposal to deprecate CXF HTTP Binding
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
Re: Proposal to deprecate CXF HTTP Binding
Posted by Sergey Beryozkin <se...@progress.com>.
> Actually, I'll argue a bit. 2.1 will be live and maintained for some time.
> Anyone who really wants to use it can use 2.1. Can you think of a
> 2.2-specific feature that someone would want to combine with the old HTTP
> binding?
Not really...If we knew that no HTTP binding users migrated to CXF 2.2-SNAPSHOT (how likely it is ?) then
I guess we could indeed remove it for 2.2...
Are there any HTTP binding users out there who already started working with CXF 2.2-SNAPSHOT ?
Cheers, Sergey
>
> On Tue, Jan 20, 2009 at 12:30 PM, Benson Margulies <bi...@gmail.com>wrote:
>
>> OK
>>
>>
>> On Tue, Jan 20, 2009 at 12:20 PM, Sergey Beryozkin <
>> sergey.beryozkin@progress.com> wrote:
>>
>>> Hi Benson
>>>
>>> I'd give HTTP Binding a bit more time to live, just declare it as
>>> deprecated and then remove it altogether in the next release.
>>> I think a number of users are actually using its client support and while
>>> I can say that we will attempt to
>>> provide a restful client api, I can't guarantee yet that it will be close
>>> to what HTTPBinding provides and even it will be of some reasonable quality
>>> in time for 2.2 release...
>>>
>>> Cheers, Sergey
>>>
>>>
>>> +1 to deletion from the trunk for 2.2.
>>>>
>>>> On Tue, Jan 20, 2009 at 11:21 AM, Sergey Beryozkin <
>>>> sergey.beryozkin@progress.com> 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
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Proposal to deprecate CXF HTTP Binding
Posted by Sergey Beryozkin <se...@progress.com>.
> Actually, I'll argue a bit. 2.1 will be live and maintained for some time.
> Anyone who really wants to use it can use 2.1. Can you think of a
> 2.2-specific feature that someone would want to combine with the old HTTP
> binding?
Not really...If we knew that no HTTP binding users migrated to CXF 2.2-SNAPSHOT (how likely it is ?) then
I guess we could indeed remove it for 2.2...
Are there any HTTP binding users out there who already started working with CXF 2.2-SNAPSHOT ?
Cheers, Sergey
>
> On Tue, Jan 20, 2009 at 12:30 PM, Benson Margulies <bi...@gmail.com>wrote:
>
>> OK
>>
>>
>> On Tue, Jan 20, 2009 at 12:20 PM, Sergey Beryozkin <
>> sergey.beryozkin@progress.com> wrote:
>>
>>> Hi Benson
>>>
>>> I'd give HTTP Binding a bit more time to live, just declare it as
>>> deprecated and then remove it altogether in the next release.
>>> I think a number of users are actually using its client support and while
>>> I can say that we will attempt to
>>> provide a restful client api, I can't guarantee yet that it will be close
>>> to what HTTPBinding provides and even it will be of some reasonable quality
>>> in time for 2.2 release...
>>>
>>> Cheers, Sergey
>>>
>>>
>>> +1 to deletion from the trunk for 2.2.
>>>>
>>>> On Tue, Jan 20, 2009 at 11:21 AM, Sergey Beryozkin <
>>>> sergey.beryozkin@progress.com> 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
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Proposal to deprecate CXF HTTP Binding
Posted by Benson Margulies <bi...@gmail.com>.
Actually, I'll argue a bit. 2.1 will be live and maintained for some time.
Anyone who really wants to use it can use 2.1. Can you think of a
2.2-specific feature that someone would want to combine with the old HTTP
binding?
On Tue, Jan 20, 2009 at 12:30 PM, Benson Margulies <bi...@gmail.com>wrote:
> OK
>
>
> On Tue, Jan 20, 2009 at 12:20 PM, Sergey Beryozkin <
> sergey.beryozkin@progress.com> wrote:
>
>> Hi Benson
>>
>> I'd give HTTP Binding a bit more time to live, just declare it as
>> deprecated and then remove it altogether in the next release.
>> I think a number of users are actually using its client support and while
>> I can say that we will attempt to
>> provide a restful client api, I can't guarantee yet that it will be close
>> to what HTTPBinding provides and even it will be of some reasonable quality
>> in time for 2.2 release...
>>
>> Cheers, Sergey
>>
>>
>> +1 to deletion from the trunk for 2.2.
>>>
>>> On Tue, Jan 20, 2009 at 11:21 AM, Sergey Beryozkin <
>>> sergey.beryozkin@progress.com> 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
>>>>
>>>>
>>>
>>
>
Re: Proposal to deprecate CXF HTTP Binding
Posted by Benson Margulies <bi...@gmail.com>.
OK
On Tue, Jan 20, 2009 at 12:20 PM, Sergey Beryozkin <
sergey.beryozkin@progress.com> wrote:
> Hi Benson
>
> I'd give HTTP Binding a bit more time to live, just declare it as
> deprecated and then remove it altogether in the next release.
> I think a number of users are actually using its client support and while I
> can say that we will attempt to
> provide a restful client api, I can't guarantee yet that it will be close
> to what HTTPBinding provides and even it will be of some reasonable quality
> in time for 2.2 release...
>
> Cheers, Sergey
>
>
> +1 to deletion from the trunk for 2.2.
>>
>> On Tue, Jan 20, 2009 at 11:21 AM, Sergey Beryozkin <
>> sergey.beryozkin@progress.com> 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
>>>
>>>
>>
>
Re: Proposal to deprecate CXF HTTP Binding
Posted by Sergey Beryozkin <se...@progress.com>.
Hi Benson
I'd give HTTP Binding a bit more time to live, just declare it as deprecated and then remove it altogether in the next release.
I think a number of users are actually using its client support and while I can say that we will attempt to
provide a restful client api, I can't guarantee yet that it will be close to what HTTPBinding provides and even it will be of some
reasonable quality in time for 2.2 release...
Cheers, Sergey
> +1 to deletion from the trunk for 2.2.
>
> On Tue, Jan 20, 2009 at 11:21 AM, Sergey Beryozkin <
> sergey.beryozkin@progress.com> 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
>>
>
Re: Proposal to deprecate CXF HTTP Binding
Posted by Benson Margulies <bi...@gmail.com>.
+1 to deletion from the trunk for 2.2.
On Tue, Jan 20, 2009 at 11:21 AM, Sergey Beryozkin <
sergey.beryozkin@progress.com> 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
>
Re: Proposal to deprecate CXF HTTP Binding
Posted by Glen Mazza <gl...@gmail.com>.
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
> dkulp@apache.org
> 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.
Re: Proposal to deprecate CXF HTTP Binding
Posted by Daniel Kulp <dk...@apache.org>.
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
dkulp@apache.org
http://dankulp.com/blog
Re: Proposal to deprecate CXF HTTP Binding
Posted by Glen Mazza <gl...@gmail.com>.
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
>
>
--
View this message in context: http://www.nabble.com/Proposal-to-deprecate-CXF-HTTP-Binding-tp21566458p21569868.html
Sent from the cxf-dev mailing list archive at Nabble.com.