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 <sb...@gmail.com> on 2016/09/02 16:07:12 UTC
Removing some old modules in 3.2.0-SNAPSHOT
Hi
CXF module base continues to grow - a lot of modules is available, with
some of these modules being obsolete and never used.
I'd like to propose to drop some of these modules in 3.2.0-SNAPSHOT to
make the builds faster, the workspaces smaller and new users less
overwhelmed :-). Once we agree on the final list I can remove them but
as soon as we have at least a single user requesting the module back
we'll put it back in 3.2.1. But in meantime we should give this clean-up
a try :-).
The proposed list is below. Dan, others, please add -1 under any item
you feel like worth keeping (but note we will put any removed module
back in 3.2.1 or later whenever it is needed again):
1. rt/management-web
I was the one who added it, it was based on a GSOC project and I do
think it is a unique project (users can see logging events in Atom
readers), Aki did some good work around it a couple of years back, but I
haven't seen any user actually asking questions or trying to use it.
Thus it should go. I'll be the 1st one who will put it back if someone
will want to push it further.
2. rt/rs/security/oauth-parent/oauth
This module supports Oauth1 and is also based on the GSOC project.
Removing it might be a bit sensitive as some users did use it few years
back. But OAuth1 is technically deprecated and Oauth2 is now widely
deployed which is where we put a lot of effort into in CXF. I haven;t
heard any queries about it for the last few years.
3. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
be really useful to anyone ? May be we can drop them and put back if needed.
4. integration/jca - I don't even remember what JCA means :-). I vaguely
recall it was some old container spec ?
5. rt/bindings/object
I think I recall Dan explaining awhile back it is a more advanced
version of coloc but I don't think it has ever been used by CXF users ?
6. rt/databindings/jibx
I believe JIBX has not been maintained for many years now, if yes
then lets let it go
7. systests/jibx
8. rt/databindings/sdo
I know it was added on request from one of our previous employers,
which was awhile back. Not sure if we need to keep it though
9. rt/databindings/xmlbeans
Not sure if it is still needed. Looks like SOAP users do JAXB,
occasionally - Aegis
10. services/wsn ?
11. rt/ws/eventing ?
12. rt/ws/mex ?
This is it for now. Please provide the feedback, we can keep this thread
open for few weeks for sure
Thanks, Sergey
10.
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Andriy Redko <dr...@gmail.com>.
Hey Sergey,
Sounds awesome, the time to deprecate OAuth1 will certainly come :-)
Thanks a lot!
Best Regards,
Andriy Redko
SB> Hi Andriy
SB> Thanks, interesting to hear you are seeing quite a bit of life is left
SB> in OAuth1 (it was indeed a real innovation at a time).
SB> I did have some doubts about whether to include this module or not.
SB> Some modules (ex, Corba related), are indeed much older, but they are
SB> actually used these days so obviously I could not even offer for them be
SB> dropped.
SB> I haven't heard anything about OAuth1 recently from CXF users but
SB> may be it is a sign that what already works is just working.
SB> In the end of the day, it is a first try for us to clean up CXF a bit.
SB> I'm happy enough to keep this module given your concern. I'll add it to
SB> the list when we start a similar discussion in CXF 4.0 (whenever it
SB> comes :-))
SB> Sergey
SB> On 03/09/16 00:23, Andriy Redko wrote:
>> Hey Sergey,
>> You are very right, OAuth2 is certainly step forward, unfortunately
>> this days OAuth1 is still used (have day by day examples of that). Great
>> talk, as always, thanks a lot for the slides, looking into them!
>> Thanks!
>> Best Regards,
>> Andriy Redko
>> *SB> Hi Andriy
>> SB> Just something I'd like to clarify re CXF OAuth1 module. I was a mentor
>> SB> for the original GSOC project and spent quite a bit of time with it
>> SB> afterwards too.
>> SB> After spending even more time with OAuth2 I see OAuth2
>> SB> being actually simpler for a classical case originally covered by
>> OAuth1
>> SB> - one less roundtrip. It is more secure and this work is ongoing.
>> OAuth2
>> SB> got a lot of bad press after an exit of the OAuth1 author but a lot of
>> SB> that was originating from the users who either did not quite understand
>> SB> OAuth2 or were looking at the buggy implementations of Implicit
>> Flow, etc.
>> SB> These days Oauth2 is huge. But of you drill down into it and try to
>> SB> address a classical case it is simpler. And OAuth2 (with OIDC) will let
>> SB> one to scale to covering much more sophisticated cases. I'm definitely
>> SB> not planning to put more effort into CXF OAuth1 - and new users should
>> SB> be discouraged from trying it because they will go not far with it.
>> SB> I did this talk few years back:
>> *SB>
>> http://events.linuxfoundation.org/sites/events/files/slides/ApacheEuCxfOauthHawk.pdf
>> <http://events.linuxfoundation.org/sites/events/files/slides/ApacheEuCxfOauthHawk.pdf>
>> *SB> But as far as this module is concerned it has got a fair bit of
>> SB> attention a couple of years back. The last change I did there was 2
>> SB> years back. But I can accept someone is still using CXF OAuth1 client
>> SB> code against some OAuth1 server and more likely - protects CXF Server
>> SB> with CXF OAuth1 filter against some 3rd party OAuth1 client.
>> SB> Cheers, Sergey
>> SB> On 02/09/16 17:31, Sergey Beryozkin wrote:
>>>> Hi Andriy
>>>> Yeah, I just wanted to show I'm ready to depart with some of RS modules
>>>> too :-). You are right though, likely some existing integrations are
>>>> still around.
>>>> Sergey
>>>> On 02/09/16 17:27, Andrey Redko wrote:
>>>>> Hey Sergey,
>>>>> Great undertaking I think! From my side, I would put -1 to oauth module.
>>>>> You are right, technically it is old spec but it is still
>>>>> used widely (mostly because it is much simple to integrate comparing to
>>>>> oauth2 f.e.).
>>>>> Thanks.
>>>>> Best Regards,
>>>>> Andriy Redko
>>>>> On Fri, Sep 2, 2016 at 12:07 PM, Sergey Beryozkin <*sberyozkin@gmail.com <ma...@gmail.com>*>
>>>>> wrote:
>>>>>> Hi
>>>>>> CXF module base continues to grow - a lot of modules is available, with
>>>>>> some of these modules being obsolete and never used.
>>>>>> I'd like to propose to drop some of these modules in 3.2.0-SNAPSHOT to
>>>>>> make the builds faster, the workspaces smaller and new users less
>>>>>> overwhelmed :-). Once we agree on the final list I can remove them
>>>>>> but as
>>>>>> soon as we have at least a single user requesting the module back
>>>>>> we'll put
>>>>>> it back in 3.2.1. But in meantime we should give this clean-up a try
>>>>>> :-).
>>>>>> The proposed list is below. Dan, others, please add -1 under any item
>>>>>> you
>>>>>> feel like worth keeping (but note we will put any removed module back in
>>>>>> 3.2.1 or later whenever it is needed again):
>>>>>> 1. rt/management-web
>>>>>> I was the one who added it, it was based on a GSOC project and I do
>>>>>> think
>>>>>> it is a unique project (users can see logging events in Atom
>>>>>> readers), Aki
>>>>>> did some good work around it a couple of years back, but I haven't
>>>>>> seen any
>>>>>> user actually asking questions or trying to use it.
>>>>>> Thus it should go. I'll be the 1st one who will put it back if someone
>>>>>> will want to push it further.
>>>>>> 2. rt/rs/security/oauth-parent/oauth
>>>>>> This module supports Oauth1 and is also based on the GSOC project.
>>>>>> Removing it might be a bit sensitive as some users did use it few years
>>>>>> back. But OAuth1 is technically deprecated and Oauth2 is now widely
>>>>>> deployed which is where we put a lot of effort into in CXF. I haven;t
>>>>>> heard
>>>>>> any queries about it for the last few years.
>>>>>> 3. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can
>>>>>> they be
>>>>>> really useful to anyone ? May be we can drop them and put back if
>>>>>> needed.
>>>>>> 4. integration/jca - I don't even remember what JCA means :-). I vaguely
>>>>>> recall it was some old container spec ?
>>>>>> 5. rt/bindings/object
>>>>>> I think I recall Dan explaining awhile back it is a more advanced
>>>>>> version
>>>>>> of coloc but I don't think it has ever been used by CXF users ?
>>>>>> 6. rt/databindings/jibx
>>>>>> I believe JIBX has not been maintained for many years now, if yes
>>>>>> then
>>>>>> lets let it go
>>>>>> 7. systests/jibx
>>>>>> 8. rt/databindings/sdo
>>>>>> I know it was added on request from one of our previous employers,
>>>>>> which was awhile back. Not sure if we need to keep it though
>>>>>> 9. rt/databindings/xmlbeans
>>>>>> Not sure if it is still needed. Looks like SOAP users do JAXB,
>>>>>> occasionally - Aegis
>>>>>> 10. services/wsn ?
>>>>>> 11. rt/ws/eventing ?
>>>>>> 12. rt/ws/mex ?
>>>>>> This is it for now. Please provide the feedback, we can keep this thread
>>>>>> open for few weeks for sure
>>>>>> Thanks, Sergey
>>>>>> 10.
>> *
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi Andriy
Thanks, interesting to hear you are seeing quite a bit of life is left
in OAuth1 (it was indeed a real innovation at a time).
I did have some doubts about whether to include this module or not.
Some modules (ex, Corba related), are indeed much older, but they are
actually used these days so obviously I could not even offer for them be
dropped.
I haven't heard anything about OAuth1 recently from CXF users but
may be it is a sign that what already works is just working.
In the end of the day, it is a first try for us to clean up CXF a bit.
I'm happy enough to keep this module given your concern. I'll add it to
the list when we start a similar discussion in CXF 4.0 (whenever it
comes :-))
Sergey
On 03/09/16 00:23, Andriy Redko wrote:
> Hey Sergey,
>
> You are very right, OAuth2 is certainly step forward, unfortunately
> this days OAuth1 is still used (have day by day examples of that). Great
> talk, as always, thanks a lot for the slides, looking into them!
>
> Thanks!
>
> Best Regards,
> Andriy Redko
>
> *SB> Hi Andriy
>
> SB> Just something I'd like to clarify re CXF OAuth1 module. I was a mentor
> SB> for the original GSOC project and spent quite a bit of time with it
> SB> afterwards too.
> SB> After spending even more time with OAuth2 I see OAuth2
> SB> being actually simpler for a classical case originally covered by
> OAuth1
> SB> - one less roundtrip. It is more secure and this work is ongoing.
> OAuth2
> SB> got a lot of bad press after an exit of the OAuth1 author but a lot of
> SB> that was originating from the users who either did not quite understand
> SB> OAuth2 or were looking at the buggy implementations of Implicit
> Flow, etc.
>
> SB> These days Oauth2 is huge. But of you drill down into it and try to
> SB> address a classical case it is simpler. And OAuth2 (with OIDC) will let
> SB> one to scale to covering much more sophisticated cases. I'm definitely
> SB> not planning to put more effort into CXF OAuth1 - and new users should
> SB> be discouraged from trying it because they will go not far with it.
>
> SB> I did this talk few years back:
> *SB>
> http://events.linuxfoundation.org/sites/events/files/slides/ApacheEuCxfOauthHawk.pdf
> <http://events.linuxfoundation.org/sites/events/files/slides/ApacheEuCxfOauthHawk.pdf>
>
> *SB> But as far as this module is concerned it has got a fair bit of
> SB> attention a couple of years back. The last change I did there was 2
> SB> years back. But I can accept someone is still using CXF OAuth1 client
> SB> code against some OAuth1 server and more likely - protects CXF Server
> SB> with CXF OAuth1 filter against some 3rd party OAuth1 client.
>
> SB> Cheers, Sergey
>
>
>
> SB> On 02/09/16 17:31, Sergey Beryozkin wrote:
>>> Hi Andriy
>
>>> Yeah, I just wanted to show I'm ready to depart with some of RS modules
>>> too :-). You are right though, likely some existing integrations are
>>> still around.
>
>>> Sergey
>>> On 02/09/16 17:27, Andrey Redko wrote:
>>>> Hey Sergey,
>
>>>> Great undertaking I think! From my side, I would put -1 to oauth module.
>>>> You are right, technically it is old spec but it is still
>>>> used widely (mostly because it is much simple to integrate comparing to
>>>> oauth2 f.e.).
>
>>>> Thanks.
>
>>>> Best Regards,
>>>> Andriy Redko
>
>>>> On Fri, Sep 2, 2016 at 12:07 PM, Sergey Beryozkin <*sberyozkin@gmail.com <ma...@gmail.com>*>
>>>> wrote:
>
>>>>> Hi
>
>>>>> CXF module base continues to grow - a lot of modules is available, with
>>>>> some of these modules being obsolete and never used.
>
>>>>> I'd like to propose to drop some of these modules in 3.2.0-SNAPSHOT to
>>>>> make the builds faster, the workspaces smaller and new users less
>>>>> overwhelmed :-). Once we agree on the final list I can remove them
>>>>> but as
>>>>> soon as we have at least a single user requesting the module back
>>>>> we'll put
>>>>> it back in 3.2.1. But in meantime we should give this clean-up a try
>>>>> :-).
>
>>>>> The proposed list is below. Dan, others, please add -1 under any item
>>>>> you
>>>>> feel like worth keeping (but note we will put any removed module back in
>>>>> 3.2.1 or later whenever it is needed again):
>
>>>>> 1. rt/management-web
>
>>>>> I was the one who added it, it was based on a GSOC project and I do
>>>>> think
>>>>> it is a unique project (users can see logging events in Atom
>>>>> readers), Aki
>>>>> did some good work around it a couple of years back, but I haven't
>>>>> seen any
>>>>> user actually asking questions or trying to use it.
>>>>> Thus it should go. I'll be the 1st one who will put it back if someone
>>>>> will want to push it further.
>
>>>>> 2. rt/rs/security/oauth-parent/oauth
>
>>>>> This module supports Oauth1 and is also based on the GSOC project.
>>>>> Removing it might be a bit sensitive as some users did use it few years
>>>>> back. But OAuth1 is technically deprecated and Oauth2 is now widely
>>>>> deployed which is where we put a lot of effort into in CXF. I haven;t
>>>>> heard
>>>>> any queries about it for the last few years.
>
>>>>> 3. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can
>>>>> they be
>>>>> really useful to anyone ? May be we can drop them and put back if
>>>>> needed.
>
>>>>> 4. integration/jca - I don't even remember what JCA means :-). I vaguely
>>>>> recall it was some old container spec ?
>
>
>>>>> 5. rt/bindings/object
>
>>>>> I think I recall Dan explaining awhile back it is a more advanced
>>>>> version
>>>>> of coloc but I don't think it has ever been used by CXF users ?
>
>>>>> 6. rt/databindings/jibx
>>>>> I believe JIBX has not been maintained for many years now, if yes
>>>>> then
>>>>> lets let it go
>
>>>>> 7. systests/jibx
>
>>>>> 8. rt/databindings/sdo
>
>>>>> I know it was added on request from one of our previous employers,
>>>>> which was awhile back. Not sure if we need to keep it though
>
>>>>> 9. rt/databindings/xmlbeans
>
>>>>> Not sure if it is still needed. Looks like SOAP users do JAXB,
>>>>> occasionally - Aegis
>
>>>>> 10. services/wsn ?
>
>>>>> 11. rt/ws/eventing ?
>
>>>>> 12. rt/ws/mex ?
>
>
>>>>> This is it for now. Please provide the feedback, we can keep this thread
>>>>> open for few weeks for sure
>
>>>>> Thanks, Sergey
>
>>>>> 10.
>
>
>
>
>
>
>
>
>
> *
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi Andriy
Just something I'd like to clarify re CXF OAuth1 module. I was a mentor
for the original GSOC project and spent quite a bit of time with it
afterwards too.
After spending even more time with OAuth2 I see OAuth2
being actually simpler for a classical case originally covered by OAuth1
- one less roundtrip. It is more secure and this work is ongoing. OAuth2
got a lot of bad press after an exit of the OAuth1 author but a lot of
that was originating from the users who either did not quite understand
OAuth2 or were looking at the buggy implementations of Implicit Flow, etc.
These days Oauth2 is huge. But of you drill down into it and try to
address a classical case it is simpler. And OAuth2 (with OIDC) will let
one to scale to covering much more sophisticated cases. I'm definitely
not planning to put more effort into CXF OAuth1 - and new users should
be discouraged from trying it because they will go not far with it.
I did this talk few years back:
http://events.linuxfoundation.org/sites/events/files/slides/ApacheEuCxfOauthHawk.pdf
But as far as this module is concerned it has got a fair bit of
attention a couple of years back. The last change I did there was 2
years back. But I can accept someone is still using CXF OAuth1 client
code against some OAuth1 server and more likely - protects CXF Server
with CXF OAuth1 filter against some 3rd party OAuth1 client.
Cheers, Sergey
On 02/09/16 17:31, Sergey Beryozkin wrote:
> Hi Andriy
>
> Yeah, I just wanted to show I'm ready to depart with some of RS modules
> too :-). You are right though, likely some existing integrations are
> still around.
>
> Sergey
> On 02/09/16 17:27, Andrey Redko wrote:
>> Hey Sergey,
>>
>> Great undertaking I think! From my side, I would put -1 to oauth module.
>> You are right, technically it is old spec but it is still
>> used widely (mostly because it is much simple to integrate comparing to
>> oauth2 f.e.).
>>
>> Thanks.
>>
>> Best Regards,
>> Andriy Redko
>>
>> On Fri, Sep 2, 2016 at 12:07 PM, Sergey Beryozkin <sb...@gmail.com>
>> wrote:
>>
>>> Hi
>>>
>>> CXF module base continues to grow - a lot of modules is available, with
>>> some of these modules being obsolete and never used.
>>>
>>> I'd like to propose to drop some of these modules in 3.2.0-SNAPSHOT to
>>> make the builds faster, the workspaces smaller and new users less
>>> overwhelmed :-). Once we agree on the final list I can remove them
>>> but as
>>> soon as we have at least a single user requesting the module back
>>> we'll put
>>> it back in 3.2.1. But in meantime we should give this clean-up a try
>>> :-).
>>>
>>> The proposed list is below. Dan, others, please add -1 under any item
>>> you
>>> feel like worth keeping (but note we will put any removed module back in
>>> 3.2.1 or later whenever it is needed again):
>>>
>>> 1. rt/management-web
>>>
>>> I was the one who added it, it was based on a GSOC project and I do
>>> think
>>> it is a unique project (users can see logging events in Atom
>>> readers), Aki
>>> did some good work around it a couple of years back, but I haven't
>>> seen any
>>> user actually asking questions or trying to use it.
>>> Thus it should go. I'll be the 1st one who will put it back if someone
>>> will want to push it further.
>>>
>>> 2. rt/rs/security/oauth-parent/oauth
>>>
>>> This module supports Oauth1 and is also based on the GSOC project.
>>> Removing it might be a bit sensitive as some users did use it few years
>>> back. But OAuth1 is technically deprecated and Oauth2 is now widely
>>> deployed which is where we put a lot of effort into in CXF. I haven;t
>>> heard
>>> any queries about it for the last few years.
>>>
>>> 3. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can
>>> they be
>>> really useful to anyone ? May be we can drop them and put back if
>>> needed.
>>>
>>> 4. integration/jca - I don't even remember what JCA means :-). I vaguely
>>> recall it was some old container spec ?
>>>
>>>
>>> 5. rt/bindings/object
>>>
>>> I think I recall Dan explaining awhile back it is a more advanced
>>> version
>>> of coloc but I don't think it has ever been used by CXF users ?
>>>
>>> 6. rt/databindings/jibx
>>> I believe JIBX has not been maintained for many years now, if yes
>>> then
>>> lets let it go
>>>
>>> 7. systests/jibx
>>>
>>> 8. rt/databindings/sdo
>>>
>>> I know it was added on request from one of our previous employers,
>>> which was awhile back. Not sure if we need to keep it though
>>>
>>> 9. rt/databindings/xmlbeans
>>>
>>> Not sure if it is still needed. Looks like SOAP users do JAXB,
>>> occasionally - Aegis
>>>
>>> 10. services/wsn ?
>>>
>>> 11. rt/ws/eventing ?
>>>
>>> 12. rt/ws/mex ?
>>>
>>>
>>> This is it for now. Please provide the feedback, we can keep this thread
>>> open for few weeks for sure
>>>
>>> Thanks, Sergey
>>>
>>> 10.
>>>
>>>
>>>
>>
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Meant "this module" (integration/jca)
On 04/09/16 17:53, Sergey Beryozkin wrote:
> Hi, Thanks, I guess this method was used in early ServiceMix (or even
> pre ServiceMix) ... May be it should be kept. But as I noted we'd
> readily put anything that may be required later on so, I'll keep in the
> list for now, as no -1 has been received on dropping it yet.
>
> Thanks, Sergey
>
> On 02/09/16 22:16, David Jencks wrote:
>> no idea what the integration/jca module might do but\u2026 jca (java
>> connector architecture) is the spec way of installing things like JMS
>> providers, SAP connector, CICS connector and other \u201centerprise
>> integration\u201d products. If there\u2019s a way to use JMS as a transport
>> this might be involved.
>>
>> david jencks
>>
>>> On Sep 2, 2016, at 1:41 PM, Sergey Beryozkin <sb...@gmail.com>
>>> wrote:
>>>
>>> Updated list (it may be a bit noisy but it will settle down...)
>>>
>>> 1. rt/management-web
>>>
>>> I was the one who added it, it was based on a GSOC project and I do
>>> think it is a unique project (users can see logging events in Atom
>>> readers), Aki did some good work around it a couple of years back,
>>> but I haven't seen any user actually asking questions or trying to
>>> use it.
>>> Thus it should go. I'll be the 1st one who will put it back if
>>> someone will want to push it further.
>>>
>>> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can
>>> they be really useful to anyone ? May be we can drop them and put
>>> back if needed.
>>>
>>> 3. integration/jca - I don't even remember what JCA means . I vaguely
>>> recall it was some old container spec ?
>>>
>>>
>>> 4. rt/bindings/object
>>>
>>> I think I recall Dan explaining awhile back it is a more advanced
>>> version of coloc but I don't think it has ever been used by CXF users ?
>>>
>>> 5. rt/databindings/jibx
>>> I believe JIBX has not been maintained for many years now, if yes
>>> then lets let it go
>>>
>>> 6. systests/jibx
>>>
>>> 7. rt/databindings/sdo
>>>
>>> I know it was added on request from one of our previous employers,
>>> which was awhile back. Not sure if we need to keep it though
>>>
>>> 8. rt/databindings/xmlbeans
>>>
>>> Not sure if it is still needed. Looks like SOAP users do JAXB,
>>> occasionally - Aegis
>>>
>>> 9. services/wsn ?
>>
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi, Thanks, I guess this method was used in early ServiceMix (or even
pre ServiceMix) ... May be it should be kept. But as I noted we'd
readily put anything that may be required later on so, I'll keep in the
list for now, as no -1 has been received on dropping it yet.
Thanks, Sergey
On 02/09/16 22:16, David Jencks wrote:
> no idea what the integration/jca module might do but\u2026 jca (java connector architecture) is the spec way of installing things like JMS providers, SAP connector, CICS connector and other \u201centerprise integration\u201d products. If there\u2019s a way to use JMS as a transport this might be involved.
>
> david jencks
>
>> On Sep 2, 2016, at 1:41 PM, Sergey Beryozkin <sb...@gmail.com> wrote:
>>
>> Updated list (it may be a bit noisy but it will settle down...)
>>
>> 1. rt/management-web
>>
>> I was the one who added it, it was based on a GSOC project and I do think it is a unique project (users can see logging events in Atom readers), Aki did some good work around it a couple of years back, but I haven't seen any user actually asking questions or trying to use it.
>> Thus it should go. I'll be the 1st one who will put it back if someone will want to push it further.
>>
>> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they be really useful to anyone ? May be we can drop them and put back if needed.
>>
>> 3. integration/jca - I don't even remember what JCA means . I vaguely recall it was some old container spec ?
>>
>>
>> 4. rt/bindings/object
>>
>> I think I recall Dan explaining awhile back it is a more advanced version of coloc but I don't think it has ever been used by CXF users ?
>>
>> 5. rt/databindings/jibx
>> I believe JIBX has not been maintained for many years now, if yes then lets let it go
>>
>> 6. systests/jibx
>>
>> 7. rt/databindings/sdo
>>
>> I know it was added on request from one of our previous employers, which was awhile back. Not sure if we need to keep it though
>>
>> 8. rt/databindings/xmlbeans
>>
>> Not sure if it is still needed. Looks like SOAP users do JAXB, occasionally - Aegis
>>
>> 9. services/wsn ?
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by David Jencks <da...@yahoo.com.INVALID>.
no idea what the integration/jca module might do but… jca (java connector architecture) is the spec way of installing things like JMS providers, SAP connector, CICS connector and other “enterprise integration” products. If there’s a way to use JMS as a transport this might be involved.
david jencks
> On Sep 2, 2016, at 1:41 PM, Sergey Beryozkin <sb...@gmail.com> wrote:
>
> Updated list (it may be a bit noisy but it will settle down...)
>
> 1. rt/management-web
>
> I was the one who added it, it was based on a GSOC project and I do think it is a unique project (users can see logging events in Atom readers), Aki did some good work around it a couple of years back, but I haven't seen any user actually asking questions or trying to use it.
> Thus it should go. I'll be the 1st one who will put it back if someone will want to push it further.
>
> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they be really useful to anyone ? May be we can drop them and put back if needed.
>
> 3. integration/jca - I don't even remember what JCA means . I vaguely recall it was some old container spec ?
>
>
> 4. rt/bindings/object
>
> I think I recall Dan explaining awhile back it is a more advanced version of coloc but I don't think it has ever been used by CXF users ?
>
> 5. rt/databindings/jibx
> I believe JIBX has not been maintained for many years now, if yes then lets let it go
>
> 6. systests/jibx
>
> 7. rt/databindings/sdo
>
> I know it was added on request from one of our previous employers, which was awhile back. Not sure if we need to keep it though
>
> 8. rt/databindings/xmlbeans
>
> Not sure if it is still needed. Looks like SOAP users do JAXB, occasionally - Aegis
>
> 9. services/wsn ?
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi Freeman
Sure.
Sergey
On 05/09/16 02:55, Freeman Fang wrote:
> Hi Sergey,
>
> I think we still need keep the services/wsn, WS-N is one of WS-* specification and AFAIK users still use it.
>
> Thanks!
> \uff0d\uff0d\uff0d\uff0d\uff0d\uff0d\uff0d\uff0d\uff0d\uff0d\uff0d\uff0d\uff0d
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
>
>
>
>> On Sep 3, 2016, at 4:41 AM, Sergey Beryozkin <sb...@gmail.com> wrote:
>>
>> Updated list (it may be a bit noisy but it will settle down...)
>>
>> 1. rt/management-web
>>
>> I was the one who added it, it was based on a GSOC project and I do think it is a unique project (users can see logging events in Atom readers), Aki did some good work around it a couple of years back, but I haven't seen any user actually asking questions or trying to use it.
>> Thus it should go. I'll be the 1st one who will put it back if someone will want to push it further.
>>
>> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they be really useful to anyone ? May be we can drop them and put back if needed.
>>
>> 3. integration/jca - I don't even remember what JCA means . I vaguely recall it was some old container spec ?
>>
>>
>> 4. rt/bindings/object
>>
>> I think I recall Dan explaining awhile back it is a more advanced version of coloc but I don't think it has ever been used by CXF users ?
>>
>> 5. rt/databindings/jibx
>> I believe JIBX has not been maintained for many years now, if yes then lets let it go
>>
>> 6. systests/jibx
>>
>> 7. rt/databindings/sdo
>>
>> I know it was added on request from one of our previous employers, which was awhile back. Not sure if we need to keep it though
>>
>> 8. rt/databindings/xmlbeans
>>
>> Not sure if it is still needed. Looks like SOAP users do JAXB, occasionally - Aegis
>>
>> 9. services/wsn ?
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Freeman Fang <fr...@gmail.com>.
Hi Mr. Kelly
Thank you very much!
You mentioned that Mason is a little bit weak at English foundation compared to other kids last week. So we want to know how we can do at home to cooperate with you to improve his English capability.
From about 1 year ago, I began to read English books for him for about 20 to 40 minutes almost every night, mainly picture books. But we don't speak English at home because our English is not that good. Besides this, Mason hasn't gone to any English classes to learn English and neither learned how to write words or letters.
So now we want to know:
1. Based on your observation, witch part is the most weak of his English, listen, speak, read or write?
2. Because I think listening may be the most important capability, do you suggest we should let him listen more English materials from now on?
3. what's your specific suggestion on improving his English capability at home?
We hope get your feedback and thank you again!
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
> On Sep 5, 2016, at 9:55 AM, Freeman Fang <fr...@gmail.com> wrote:
>
> Hi Sergey,
>
> I think we still need keep the services/wsn, WS-N is one of WS-* specification and AFAIK users still use it.
>
> Thanks!
> －－－－－－－－－－－－－
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
>
>
>
>> On Sep 3, 2016, at 4:41 AM, Sergey Beryozkin <sberyozkin@gmail.com <ma...@gmail.com>> wrote:
>>
>> Updated list (it may be a bit noisy but it will settle down...)
>>
>> 1. rt/management-web
>>
>> I was the one who added it, it was based on a GSOC project and I do think it is a unique project (users can see logging events in Atom readers), Aki did some good work around it a couple of years back, but I haven't seen any user actually asking questions or trying to use it.
>> Thus it should go. I'll be the 1st one who will put it back if someone will want to push it further.
>>
>> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they be really useful to anyone ? May be we can drop them and put back if needed.
>>
>> 3. integration/jca - I don't even remember what JCA means . I vaguely recall it was some old container spec ?
>>
>>
>> 4. rt/bindings/object
>>
>> I think I recall Dan explaining awhile back it is a more advanced version of coloc but I don't think it has ever been used by CXF users ?
>>
>> 5. rt/databindings/jibx
>> I believe JIBX has not been maintained for many years now, if yes then lets let it go
>>
>> 6. systests/jibx
>>
>> 7. rt/databindings/sdo
>>
>> I know it was added on request from one of our previous employers, which was awhile back. Not sure if we need to keep it though
>>
>> 8. rt/databindings/xmlbeans
>>
>> Not sure if it is still needed. Looks like SOAP users do JAXB, occasionally - Aegis
>>
>> 9. services/wsn ?
>
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Alessio Soldano <as...@redhat.com>.
Il 23/12/2016 17:03, Sergey Beryozkin ha scritto:
> OK, these 5 modules (jibx, xmlbeans, sdo, binding/object,
> rt-management-web - the best but never used logging system for the
> endpoints :-), +2 systest jibx modules) have gone, -7 in total.
>
> Not too many but it is a start.
>
> I was hesitating for few mins about removing a databindins-xmlbeans,
> but then I reminded myself we can put it back if needed. I removed a
> JAX-RS Xmlbeans provider extension awhile back, and with JAXB and
> Aegis providing probably a 100% coverage for SOAP XML with no Xmlbeans
> queries at all we are likely safe here.
>
> Dan, others, ping me please if you'd like some of these removed
> modules return to the 3.2.0 starting line, happy enough for the moment
> we have decreased a total number of modules by -7 :-)
Thanks :-)
Cheers
Alessio
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
OK, these 5 modules (jibx, xmlbeans, sdo, binding/object,
rt-management-web - the best but never used logging system for the
endpoints :-), +2 systest jibx modules) have gone, -7 in total.
Not too many but it is a start.
I was hesitating for few mins about removing a databindins-xmlbeans, but
then I reminded myself we can put it back if needed. I removed a JAX-RS
Xmlbeans provider extension awhile back, and with JAXB and Aegis
providing probably a 100% coverage for SOAP XML with no Xmlbeans queries
at all we are likely safe here.
Dan, others, ping me please if you'd like some of these removed modules
return to the 3.2.0 starting line, happy enough for the moment we have
decreased a total number of modules by -7 :-)
Sergey
On 23/12/16 11:43, Sergey Beryozkin wrote:
> So far the modules rt-management-web and rt-databindings-jibx have gone,
> with
> rt-databindings-sdo, rt-databindings-xmlbeans and rt-bindings-object
> being on the way, I suppose I will remove them now and then we can
> double check once more in January.
>
> I've also proposed removing the archetypes but may be it is not a good
> idea because the archetypes can be enhanced to accommodate for whatever
> are the most often used features are, etc. May be we can also keep a jca
> integration module. Another batch of the obsolete modules can be removed
> in some future major CXF release
>
> Thanks, Sergey
>
> On 22/12/16 14:30, Sergey Beryozkin wrote:
>> Hi All,
>> I've created a master issue,
>> https://issues.apache.org/jira/browse/CXF-7191, please double check,
>>
>> and started from removing the cxf-rt-management-web module.
>> As I've already mentioned few times, the modules will be restored on
>> demand,
>>
>> I'm planning to remove JIBX related modules next...and will take a pause
>> till early January before competing the rest of the subtasks.
>>
>> It will be only -6 or so modules but as they say every little helps as
>> far as attempting to minimize the CXF module space is concerned
>>
>> Thanks, Sergey
>>
>> On 25/11/16 22:44, Sergey Beryozkin wrote:
>>> Hi All
>>>
>>> Just a reminder that the below is a list of the modules which will,
>>> unless someone objects, be gone from 3.2.0 - but will be put back
>>> immediately if either of these modules is still used.
>>> We'd just to make the best effort at starting cleaning up CXF large
>>> module space.
>>>
>>> Thanks, Sergey
>>> On 05/09/16 09:54, Sergey Beryozkin wrote:
>>>> Updated list
>>>>
>>>> 1. rt/management-web
>>>>
>>>> I was the one who added it, it was based on a GSOC project and I do
>>>> think it is a unique project (users can see logging events in Atom
>>>> readers), Aki did some good work around it a couple of years back,
>>>> but I
>>>> haven't seen any user actually asking questions or trying to use it.
>>>> Thus it should go. I'll be the 1st one who will put it back if someone
>>>> will want to push it further.
>>>>
>>>> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
>>>> be really useful to anyone ? May be we can drop them and put back if
>>>> needed.
>>>>
>>>> 3. integration/jca
>>>>
>>>> 4. rt/bindings/object
>>>>
>>>> I think I recall Dan explaining awhile back it is a more advanced
>>>> version of coloc but I don't think it has ever been used by CXF users ?
>>>>
>>>> 5. rt/databindings/jibx
>>>> I believe JIBX has not been maintained for many years now, if yes
>>>> then lets let it go
>>>>
>>>> 6. systests/jibx
>>>>
>>>> 7. rt/databindings/sdo
>>>>
>>>> I know it was added on request from one of our previous employers,
>>>> which was awhile back. Not sure if we need to keep it though
>>>>
>>>> 8. rt/databindings/xmlbeans
>>>>
>>>> Not sure if it is still needed. Looks like SOAP users do JAXB,
>>>> occasionally - Aegis
>>>>
>>>
>>>
>>
>>
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
So far the modules rt-management-web and rt-databindings-jibx have gone,
with
rt-databindings-sdo, rt-databindings-xmlbeans and rt-bindings-object
being on the way, I suppose I will remove them now and then we can
double check once more in January.
I've also proposed removing the archetypes but may be it is not a good
idea because the archetypes can be enhanced to accommodate for whatever
are the most often used features are, etc. May be we can also keep a jca
integration module. Another batch of the obsolete modules can be removed
in some future major CXF release
Thanks, Sergey
On 22/12/16 14:30, Sergey Beryozkin wrote:
> Hi All,
> I've created a master issue,
> https://issues.apache.org/jira/browse/CXF-7191, please double check,
>
> and started from removing the cxf-rt-management-web module.
> As I've already mentioned few times, the modules will be restored on
> demand,
>
> I'm planning to remove JIBX related modules next...and will take a pause
> till early January before competing the rest of the subtasks.
>
> It will be only -6 or so modules but as they say every little helps as
> far as attempting to minimize the CXF module space is concerned
>
> Thanks, Sergey
>
> On 25/11/16 22:44, Sergey Beryozkin wrote:
>> Hi All
>>
>> Just a reminder that the below is a list of the modules which will,
>> unless someone objects, be gone from 3.2.0 - but will be put back
>> immediately if either of these modules is still used.
>> We'd just to make the best effort at starting cleaning up CXF large
>> module space.
>>
>> Thanks, Sergey
>> On 05/09/16 09:54, Sergey Beryozkin wrote:
>>> Updated list
>>>
>>> 1. rt/management-web
>>>
>>> I was the one who added it, it was based on a GSOC project and I do
>>> think it is a unique project (users can see logging events in Atom
>>> readers), Aki did some good work around it a couple of years back, but I
>>> haven't seen any user actually asking questions or trying to use it.
>>> Thus it should go. I'll be the 1st one who will put it back if someone
>>> will want to push it further.
>>>
>>> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
>>> be really useful to anyone ? May be we can drop them and put back if
>>> needed.
>>>
>>> 3. integration/jca
>>>
>>> 4. rt/bindings/object
>>>
>>> I think I recall Dan explaining awhile back it is a more advanced
>>> version of coloc but I don't think it has ever been used by CXF users ?
>>>
>>> 5. rt/databindings/jibx
>>> I believe JIBX has not been maintained for many years now, if yes
>>> then lets let it go
>>>
>>> 6. systests/jibx
>>>
>>> 7. rt/databindings/sdo
>>>
>>> I know it was added on request from one of our previous employers,
>>> which was awhile back. Not sure if we need to keep it though
>>>
>>> 8. rt/databindings/xmlbeans
>>>
>>> Not sure if it is still needed. Looks like SOAP users do JAXB,
>>> occasionally - Aegis
>>>
>>
>>
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi All,
I've created a master issue,
https://issues.apache.org/jira/browse/CXF-7191, please double check,
and started from removing the cxf-rt-management-web module.
As I've already mentioned few times, the modules will be restored on
demand,
I'm planning to remove JIBX related modules next...and will take a pause
till early January before competing the rest of the subtasks.
It will be only -6 or so modules but as they say every little helps as
far as attempting to minimize the CXF module space is concerned
Thanks, Sergey
On 25/11/16 22:44, Sergey Beryozkin wrote:
> Hi All
>
> Just a reminder that the below is a list of the modules which will,
> unless someone objects, be gone from 3.2.0 - but will be put back
> immediately if either of these modules is still used.
> We'd just to make the best effort at starting cleaning up CXF large
> module space.
>
> Thanks, Sergey
> On 05/09/16 09:54, Sergey Beryozkin wrote:
>> Updated list
>>
>> 1. rt/management-web
>>
>> I was the one who added it, it was based on a GSOC project and I do
>> think it is a unique project (users can see logging events in Atom
>> readers), Aki did some good work around it a couple of years back, but I
>> haven't seen any user actually asking questions or trying to use it.
>> Thus it should go. I'll be the 1st one who will put it back if someone
>> will want to push it further.
>>
>> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
>> be really useful to anyone ? May be we can drop them and put back if
>> needed.
>>
>> 3. integration/jca
>>
>> 4. rt/bindings/object
>>
>> I think I recall Dan explaining awhile back it is a more advanced
>> version of coloc but I don't think it has ever been used by CXF users ?
>>
>> 5. rt/databindings/jibx
>> I believe JIBX has not been maintained for many years now, if yes
>> then lets let it go
>>
>> 6. systests/jibx
>>
>> 7. rt/databindings/sdo
>>
>> I know it was added on request from one of our previous employers,
>> which was awhile back. Not sure if we need to keep it though
>>
>> 8. rt/databindings/xmlbeans
>>
>> Not sure if it is still needed. Looks like SOAP users do JAXB,
>> occasionally - Aegis
>>
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi All
Just a reminder that the below is a list of the modules which will,
unless someone objects, be gone from 3.2.0 - but will be put back
immediately if either of these modules is still used.
We'd just to make the best effort at starting cleaning up CXF large
module space.
Thanks, Sergey
On 05/09/16 09:54, Sergey Beryozkin wrote:
> Updated list
>
> 1. rt/management-web
>
> I was the one who added it, it was based on a GSOC project and I do
> think it is a unique project (users can see logging events in Atom
> readers), Aki did some good work around it a couple of years back, but I
> haven't seen any user actually asking questions or trying to use it.
> Thus it should go. I'll be the 1st one who will put it back if someone
> will want to push it further.
>
> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
> be really useful to anyone ? May be we can drop them and put back if
> needed.
>
> 3. integration/jca
>
> 4. rt/bindings/object
>
> I think I recall Dan explaining awhile back it is a more advanced
> version of coloc but I don't think it has ever been used by CXF users ?
>
> 5. rt/databindings/jibx
> I believe JIBX has not been maintained for many years now, if yes
> then lets let it go
>
> 6. systests/jibx
>
> 7. rt/databindings/sdo
>
> I know it was added on request from one of our previous employers,
> which was awhile back. Not sure if we need to keep it though
>
> 8. rt/databindings/xmlbeans
>
> Not sure if it is still needed. Looks like SOAP users do JAXB,
> occasionally - Aegis
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Updated list
1. rt/management-web
I was the one who added it, it was based on a GSOC project and I do
think it is a unique project (users can see logging events in Atom
readers), Aki did some good work around it a couple of years back, but I
haven't seen any user actually asking questions or trying to use it.
Thus it should go. I'll be the 1st one who will put it back if someone
will want to push it further.
2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
be really useful to anyone ? May be we can drop them and put back if needed.
3. integration/jca
4. rt/bindings/object
I think I recall Dan explaining awhile back it is a more advanced
version of coloc but I don't think it has ever been used by CXF users ?
5. rt/databindings/jibx
I believe JIBX has not been maintained for many years now, if yes
then lets let it go
6. systests/jibx
7. rt/databindings/sdo
I know it was added on request from one of our previous employers,
which was awhile back. Not sure if we need to keep it though
8. rt/databindings/xmlbeans
Not sure if it is still needed. Looks like SOAP users do JAXB,
occasionally - Aegis
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Freeman Fang <fr...@gmail.com>.
Hi Sergey,
I think we still need keep the services/wsn, WS-N is one of WS-* specification and AFAIK users still use it.
Thanks!
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
> On Sep 3, 2016, at 4:41 AM, Sergey Beryozkin <sb...@gmail.com> wrote:
>
> Updated list (it may be a bit noisy but it will settle down...)
>
> 1. rt/management-web
>
> I was the one who added it, it was based on a GSOC project and I do think it is a unique project (users can see logging events in Atom readers), Aki did some good work around it a couple of years back, but I haven't seen any user actually asking questions or trying to use it.
> Thus it should go. I'll be the 1st one who will put it back if someone will want to push it further.
>
> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they be really useful to anyone ? May be we can drop them and put back if needed.
>
> 3. integration/jca - I don't even remember what JCA means . I vaguely recall it was some old container spec ?
>
>
> 4. rt/bindings/object
>
> I think I recall Dan explaining awhile back it is a more advanced version of coloc but I don't think it has ever been used by CXF users ?
>
> 5. rt/databindings/jibx
> I believe JIBX has not been maintained for many years now, if yes then lets let it go
>
> 6. systests/jibx
>
> 7. rt/databindings/sdo
>
> I know it was added on request from one of our previous employers, which was awhile back. Not sure if we need to keep it though
>
> 8. rt/databindings/xmlbeans
>
> Not sure if it is still needed. Looks like SOAP users do JAXB, occasionally - Aegis
>
> 9. services/wsn ?
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Updated list (it may be a bit noisy but it will settle down...)
1. rt/management-web
I was the one who added it, it was based on a GSOC project and I do
think it is a unique project (users can see logging events in Atom
readers), Aki did some good work around it a couple of years back, but I
haven't seen any user actually asking questions or trying to use it.
Thus it should go. I'll be the 1st one who will put it back if someone
will want to push it further.
2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
be really useful to anyone ? May be we can drop them and put back if needed.
3. integration/jca - I don't even remember what JCA means . I vaguely
recall it was some old container spec ?
4. rt/bindings/object
I think I recall Dan explaining awhile back it is a more advanced
version of coloc but I don't think it has ever been used by CXF users ?
5. rt/databindings/jibx
I believe JIBX has not been maintained for many years now, if yes
then lets let it go
6. systests/jibx
7. rt/databindings/sdo
I know it was added on request from one of our previous employers,
which was awhile back. Not sure if we need to keep it though
8. rt/databindings/xmlbeans
Not sure if it is still needed. Looks like SOAP users do JAXB,
occasionally - Aegis
9. services/wsn ?
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Let me drop a netty transport from this list - it is relatively new,
we've had few queries about it, and I see Brad asking about Netty and
CXF on Camel users, I guess it can be reviewed in CXF 4.
Sergey
On 02/09/16 17:39, Sergey Beryozkin wrote:
> An updated list:
> (Alessio, see item 10 (just a try), I know http-netty was added first
> followed by http-undertow, so may be you know best if adding http-netty
> was a temp requirement though I guess it may be used by some users, we
> do not know...)
>
> 1. rt/management-web
>
> I was the one who added it, it was based on a GSOC project and I do
> think it is a unique project (users can see logging events in Atom
> readers), Aki did some good work around it a couple of years back, but I
> haven't seen any user actually asking questions or trying to use it.
> Thus it should go. I'll be the 1st one who will put it back if someone
> will want to push it further.
>
> 2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
> be really useful to anyone ? May be we can drop them and put back if
> needed.
>
> 3. integration/jca - I don't even remember what JCA means . I vaguely
> recall it was some old container spec ?
>
>
> 4. rt/bindings/object
>
> I think I recall Dan explaining awhile back it is a more advanced
> version of coloc but I don't think it has ever been used by CXF users ?
>
> 5. rt/databindings/jibx
> I believe JIBX has not been maintained for many years now, if yes
> then lets let it go
>
> 6. systests/jibx
>
> 7. rt/databindings/sdo
>
> I know it was added on request from one of our previous employers,
> which was awhile back. Not sure if we need to keep it though
>
> 8. rt/databindings/xmlbeans
>
> Not sure if it is still needed. Looks like SOAP users do JAXB,
> occasionally - Aegis
>
> 9. services/wsn ?
>
> 10. rt/transports/http-netty ?
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
An updated list:
(Alessio, see item 10 (just a try), I know http-netty was added first
followed by http-undertow, so may be you know best if adding http-netty
was a temp requirement though I guess it may be used by some users, we
do not know...)
1. rt/management-web
I was the one who added it, it was based on a GSOC project and I do
think it is a unique project (users can see logging events in Atom
readers), Aki did some good work around it a couple of years back, but I
haven't seen any user actually asking questions or trying to use it.
Thus it should go. I'll be the 1st one who will put it back if someone
will want to push it further.
2. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
be really useful to anyone ? May be we can drop them and put back if needed.
3. integration/jca - I don't even remember what JCA means . I vaguely
recall it was some old container spec ?
4. rt/bindings/object
I think I recall Dan explaining awhile back it is a more advanced
version of coloc but I don't think it has ever been used by CXF users ?
5. rt/databindings/jibx
I believe JIBX has not been maintained for many years now, if yes
then lets let it go
6. systests/jibx
7. rt/databindings/sdo
I know it was added on request from one of our previous employers,
which was awhile back. Not sure if we need to keep it though
8. rt/databindings/xmlbeans
Not sure if it is still needed. Looks like SOAP users do JAXB,
occasionally - Aegis
9. services/wsn ?
10. rt/transports/http-netty ?
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi Andriy
Yeah, I just wanted to show I'm ready to depart with some of RS modules
too :-). You are right though, likely some existing integrations are
still around.
Sergey
On 02/09/16 17:27, Andrey Redko wrote:
> Hey Sergey,
>
> Great undertaking I think! From my side, I would put -1 to oauth module.
> You are right, technically it is old spec but it is still
> used widely (mostly because it is much simple to integrate comparing to
> oauth2 f.e.).
>
> Thanks.
>
> Best Regards,
> Andriy Redko
>
> On Fri, Sep 2, 2016 at 12:07 PM, Sergey Beryozkin <sb...@gmail.com>
> wrote:
>
>> Hi
>>
>> CXF module base continues to grow - a lot of modules is available, with
>> some of these modules being obsolete and never used.
>>
>> I'd like to propose to drop some of these modules in 3.2.0-SNAPSHOT to
>> make the builds faster, the workspaces smaller and new users less
>> overwhelmed :-). Once we agree on the final list I can remove them but as
>> soon as we have at least a single user requesting the module back we'll put
>> it back in 3.2.1. But in meantime we should give this clean-up a try :-).
>>
>> The proposed list is below. Dan, others, please add -1 under any item you
>> feel like worth keeping (but note we will put any removed module back in
>> 3.2.1 or later whenever it is needed again):
>>
>> 1. rt/management-web
>>
>> I was the one who added it, it was based on a GSOC project and I do think
>> it is a unique project (users can see logging events in Atom readers), Aki
>> did some good work around it a couple of years back, but I haven't seen any
>> user actually asking questions or trying to use it.
>> Thus it should go. I'll be the 1st one who will put it back if someone
>> will want to push it further.
>>
>> 2. rt/rs/security/oauth-parent/oauth
>>
>> This module supports Oauth1 and is also based on the GSOC project.
>> Removing it might be a bit sensitive as some users did use it few years
>> back. But OAuth1 is technically deprecated and Oauth2 is now widely
>> deployed which is where we put a lot of effort into in CXF. I haven;t heard
>> any queries about it for the last few years.
>>
>> 3. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they be
>> really useful to anyone ? May be we can drop them and put back if needed.
>>
>> 4. integration/jca - I don't even remember what JCA means :-). I vaguely
>> recall it was some old container spec ?
>>
>>
>> 5. rt/bindings/object
>>
>> I think I recall Dan explaining awhile back it is a more advanced version
>> of coloc but I don't think it has ever been used by CXF users ?
>>
>> 6. rt/databindings/jibx
>> I believe JIBX has not been maintained for many years now, if yes then
>> lets let it go
>>
>> 7. systests/jibx
>>
>> 8. rt/databindings/sdo
>>
>> I know it was added on request from one of our previous employers,
>> which was awhile back. Not sure if we need to keep it though
>>
>> 9. rt/databindings/xmlbeans
>>
>> Not sure if it is still needed. Looks like SOAP users do JAXB,
>> occasionally - Aegis
>>
>> 10. services/wsn ?
>>
>> 11. rt/ws/eventing ?
>>
>> 12. rt/ws/mex ?
>>
>>
>> This is it for now. Please provide the feedback, we can keep this thread
>> open for few weeks for sure
>>
>> Thanks, Sergey
>>
>> 10.
>>
>>
>>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Andrey Redko <dr...@gmail.com>.
Hey Sergey,
Great undertaking I think! From my side, I would put -1 to oauth module.
You are right, technically it is old spec but it is still
used widely (mostly because it is much simple to integrate comparing to
oauth2 f.e.).
Thanks.
Best Regards,
Andriy Redko
On Fri, Sep 2, 2016 at 12:07 PM, Sergey Beryozkin <sb...@gmail.com>
wrote:
> Hi
>
> CXF module base continues to grow - a lot of modules is available, with
> some of these modules being obsolete and never used.
>
> I'd like to propose to drop some of these modules in 3.2.0-SNAPSHOT to
> make the builds faster, the workspaces smaller and new users less
> overwhelmed :-). Once we agree on the final list I can remove them but as
> soon as we have at least a single user requesting the module back we'll put
> it back in 3.2.1. But in meantime we should give this clean-up a try :-).
>
> The proposed list is below. Dan, others, please add -1 under any item you
> feel like worth keeping (but note we will put any removed module back in
> 3.2.1 or later whenever it is needed again):
>
> 1. rt/management-web
>
> I was the one who added it, it was based on a GSOC project and I do think
> it is a unique project (users can see logging events in Atom readers), Aki
> did some good work around it a couple of years back, but I haven't seen any
> user actually asking questions or trying to use it.
> Thus it should go. I'll be the 1st one who will put it back if someone
> will want to push it further.
>
> 2. rt/rs/security/oauth-parent/oauth
>
> This module supports Oauth1 and is also based on the GSOC project.
> Removing it might be a bit sensitive as some users did use it few years
> back. But OAuth1 is technically deprecated and Oauth2 is now widely
> deployed which is where we put a lot of effort into in CXF. I haven;t heard
> any queries about it for the last few years.
>
> 3. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they be
> really useful to anyone ? May be we can drop them and put back if needed.
>
> 4. integration/jca - I don't even remember what JCA means :-). I vaguely
> recall it was some old container spec ?
>
>
> 5. rt/bindings/object
>
> I think I recall Dan explaining awhile back it is a more advanced version
> of coloc but I don't think it has ever been used by CXF users ?
>
> 6. rt/databindings/jibx
> I believe JIBX has not been maintained for many years now, if yes then
> lets let it go
>
> 7. systests/jibx
>
> 8. rt/databindings/sdo
>
> I know it was added on request from one of our previous employers,
> which was awhile back. Not sure if we need to keep it though
>
> 9. rt/databindings/xmlbeans
>
> Not sure if it is still needed. Looks like SOAP users do JAXB,
> occasionally - Aegis
>
> 10. services/wsn ?
>
> 11. rt/ws/eventing ?
>
> 12. rt/ws/mex ?
>
>
> This is it for now. Please provide the feedback, we can keep this thread
> open for few weeks for sure
>
> Thanks, Sergey
>
> 10.
>
>
>
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi Alessio
Sure, I knew ws-transfer was a recent addition but was not sure about
-mex and -eventing. If any of us thinks a given module needs to stays
then it stays.
Thanks, Sergey
On 02/09/16 17:19, Alessio Soldano wrote:
> Hi Sergey,
> I like the idea of cleaning up the code base a bit. I would however cast
> my -1 on the removal of rt/ws/eventing and rt/ws/mex, which are ws-*
> spec we kind of declare support for / implementation.
>
> Cheers
> Alessio
>
> Il 02/09/2016 18:07, Sergey Beryozkin ha scritto:
>> Hi
>>
>> CXF module base continues to grow - a lot of modules is available,
>> with some of these modules being obsolete and never used.
>>
>> I'd like to propose to drop some of these modules in 3.2.0-SNAPSHOT to
>> make the builds faster, the workspaces smaller and new users less
>> overwhelmed :-). Once we agree on the final list I can remove them but
>> as soon as we have at least a single user requesting the module back
>> we'll put it back in 3.2.1. But in meantime we should give this
>> clean-up a try :-).
>>
>> The proposed list is below. Dan, others, please add -1 under any item
>> you feel like worth keeping (but note we will put any removed module
>> back in 3.2.1 or later whenever it is needed again):
>>
>> 1. rt/management-web
>>
>> I was the one who added it, it was based on a GSOC project and I do
>> think it is a unique project (users can see logging events in Atom
>> readers), Aki did some good work around it a couple of years back, but
>> I haven't seen any user actually asking questions or trying to use it.
>> Thus it should go. I'll be the 1st one who will put it back if someone
>> will want to push it further.
>>
>> 2. rt/rs/security/oauth-parent/oauth
>>
>> This module supports Oauth1 and is also based on the GSOC project.
>> Removing it might be a bit sensitive as some users did use it few
>> years back. But OAuth1 is technically deprecated and Oauth2 is now
>> widely deployed which is where we put a lot of effort into in CXF. I
>> haven;t heard any queries about it for the last few years.
>>
>> 3. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
>> be really useful to anyone ? May be we can drop them and put back if
>> needed.
>>
>> 4. integration/jca - I don't even remember what JCA means :-). I
>> vaguely recall it was some old container spec ?
>>
>>
>> 5. rt/bindings/object
>>
>> I think I recall Dan explaining awhile back it is a more advanced
>> version of coloc but I don't think it has ever been used by CXF users ?
>>
>> 6. rt/databindings/jibx
>> I believe JIBX has not been maintained for many years now, if yes
>> then lets let it go
>>
>> 7. systests/jibx
>>
>> 8. rt/databindings/sdo
>>
>> I know it was added on request from one of our previous employers,
>> which was awhile back. Not sure if we need to keep it though
>>
>> 9. rt/databindings/xmlbeans
>>
>> Not sure if it is still needed. Looks like SOAP users do JAXB,
>> occasionally - Aegis
>>
>> 10. services/wsn ?
>>
>> 11. rt/ws/eventing ?
>>
>> 12. rt/ws/mex ?
>>
>>
>> This is it for now. Please provide the feedback, we can keep this
>> thread open for few weeks for sure
>>
>> Thanks, Sergey
>>
>> 10.
>>
>>
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: Removing some old modules in 3.2.0-SNAPSHOT
Posted by Alessio Soldano <as...@redhat.com>.
Hi Sergey,
I like the idea of cleaning up the code base a bit. I would however cast
my -1 on the removal of rt/ws/eventing and rt/ws/mex, which are ws-*
spec we kind of declare support for / implementation.
Cheers
Alessio
Il 02/09/2016 18:07, Sergey Beryozkin ha scritto:
> Hi
>
> CXF module base continues to grow - a lot of modules is available,
> with some of these modules being obsolete and never used.
>
> I'd like to propose to drop some of these modules in 3.2.0-SNAPSHOT to
> make the builds faster, the workspaces smaller and new users less
> overwhelmed :-). Once we agree on the final list I can remove them but
> as soon as we have at least a single user requesting the module back
> we'll put it back in 3.2.1. But in meantime we should give this
> clean-up a try :-).
>
> The proposed list is below. Dan, others, please add -1 under any item
> you feel like worth keeping (but note we will put any removed module
> back in 3.2.1 or later whenever it is needed again):
>
> 1. rt/management-web
>
> I was the one who added it, it was based on a GSOC project and I do
> think it is a unique project (users can see logging events in Atom
> readers), Aki did some good work around it a couple of years back, but
> I haven't seen any user actually asking questions or trying to use it.
> Thus it should go. I'll be the 1st one who will put it back if someone
> will want to push it further.
>
> 2. rt/rs/security/oauth-parent/oauth
>
> This module supports Oauth1 and is also based on the GSOC project.
> Removing it might be a bit sensitive as some users did use it few
> years back. But OAuth1 is technically deprecated and Oauth2 is now
> widely deployed which is where we put a lot of effort into in CXF. I
> haven;t heard any queries about it for the last few years.
>
> 3. maven-plugin/archetypes: Maven JAXWS and JAXRS prototypes. Can they
> be really useful to anyone ? May be we can drop them and put back if
> needed.
>
> 4. integration/jca - I don't even remember what JCA means :-). I
> vaguely recall it was some old container spec ?
>
>
> 5. rt/bindings/object
>
> I think I recall Dan explaining awhile back it is a more advanced
> version of coloc but I don't think it has ever been used by CXF users ?
>
> 6. rt/databindings/jibx
> I believe JIBX has not been maintained for many years now, if yes
> then lets let it go
>
> 7. systests/jibx
>
> 8. rt/databindings/sdo
>
> I know it was added on request from one of our previous employers,
> which was awhile back. Not sure if we need to keep it though
>
> 9. rt/databindings/xmlbeans
>
> Not sure if it is still needed. Looks like SOAP users do JAXB,
> occasionally - Aegis
>
> 10. services/wsn ?
>
> 11. rt/ws/eventing ?
>
> 12. rt/ws/mex ?
>
>
> This is it for now. Please provide the feedback, we can keep this
> thread open for few weeks for sure
>
> Thanks, Sergey
>
> 10.
>
>
--
Alessio Soldano
Web Service Lead, JBoss