Re: CXF 3.2?

[Freeman Fang]

Hi Dan,

Just added  “New http-undertow transport" in the release notes.

Thanks
－
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat



> On Sep 6, 2017, at 2:48 AM, Daniel Kulp  wrote:
> 
> The spring-boot-sample-rs-scan-app example is failing. Can someone look 
> at that?   I don’t want to release if the samples aren’t at least passing 
> their own tests.
> 
> Also, can folks look at the release-notes.txt and make sure it covers 
> everything.   Any other “new features” since 3.1?
> 
> Thanks!
> Dan
> 
> 
> 
> 
>> On Sep 4, 2017, at 5:36 PM, Andriy Redko  wrote:
>> 
>> Hey Sergey,
>> 
>> Makes perfect sense to me, let's not block 3.2 release. 3.2.1 sounds 
>> like a preferrable option indeed, with better deliverables at the end. 
>> Thanks!
>> 
>> Best Regards,
>>   Andriy Redko
>> 
>> SB> Hey Andriy
>> 
>> SB> IMHO it might wait till 3.2.1 (may be we can do a camel cxf demo making 
>> SB> sure the context can flow from Camel to CXF and vice versa) as a POC and 
>> SB> tweak few things along the way ? If we doc it right now in a bit of a 
>> SB> hurry then we will have less space for the changes ?
>> 
>> SB> Thanks, Sergey
>> SB> On 04/09/17 21:22, Andriy Redko wrote:
 Hey Dan,
>> 
 Sorry for last minute thing (always pops up), do I have time to push this
 guy https://issues.apache.org/jira/browse/CXF-7439? I am mostly done with 
 the implementation,
 need couple of more days to add a sample project and update the 
 documentation. It is considerably
 large chunk of the code, no urgency to have it in 3.2 really (could go to 
 3.2.1). Just appreciate
 the opinions, it is worth to delay a build for a couple of more days 
 (Wed/Thu) or not.
>> 
 Thanks!
>> 
 Best Regards,
Andriy Redko
>> 
>> 
>> 
 DK> We just got the final releases of WSS4J and the JAX-RS api and I’ve 
 also just managed to figure out how to get
 DK> atmosphore and the latest Jetty releases to play nicely together.   
 Also considering it’s 4pm my time on a Friday
 DK> before a long weekend, I’m not going to start the 3.2 build.   I think 
 it’s best to delay until Tuesday to give the updates and such a chance to 
 be tested.
>> 
 DK> Dan
>> 
>> 
>> 
>> 
>> On Aug 10, 2017, at 12:22 PM, Daniel Kulp  wrote:
>> 
>> 
>> It’s been over two years since 3.1.0 was released which is a long time.  
>>   I’d like to get 3.2.0 out shortly.   Looking through things, the major 
>> outstanding things are snapshots of a couple deps 
>> (xjc-utils,build-utils, wss4j) and updates to the JAX-RS stuff to use 
>> the released 2.1.   What else do folks have outstanding that would be 
>> “needed” to get into 3.2?Would Sept 1st be a good target for getting 
>> 3.2 built?   That would give use a few weeks to finish things up and get 
>> the releases out.
>> 
>> Thoughts?
>> 
>> -- 
>> Daniel Kulp
>> dk...@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>> 
>> 
>> 
>> 
> 
> -- 
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
> 

Re: CXF 3.2?

[Dennis Kieselhorst]

> The spring-boot-sample-rs-scan-app example is failing. Can someone
look at that?

Just fixed it.

Cheers
Dennis

Re: CXF 3.2?

[Andriy Redko]

Hey Sergey,

Makes perfect sense to me, let's not block 3.2 release. 3.2.1 sounds 
like a preferrable option indeed, with better deliverables at the end. 
Thanks!

Best Regards,
Andriy Redko

SB> Hey Andriy

SB> IMHO it might wait till 3.2.1 (may be we can do a camel cxf demo making 
SB> sure the context can flow from Camel to CXF and vice versa) as a POC and 
SB> tweak few things along the way ? If we doc it right now in a bit of a 
SB> hurry then we will have less space for the changes ?

SB> Thanks, Sergey
SB> On 04/09/17 21:22, Andriy Redko wrote:
>> Hey Dan,

>> Sorry for last minute thing (always pops up), do I have time to push this
>> guy https://issues.apache.org/jira/browse/CXF-7439? I am mostly done with 
>> the implementation,
>> need couple of more days to add a sample project and update the 
>> documentation. It is considerably
>> large chunk of the code, no urgency to have it in 3.2 really (could go to 
>> 3.2.1). Just appreciate
>> the opinions, it is worth to delay a build for a couple of more days 
>> (Wed/Thu) or not.

>> Thanks!

>> Best Regards,
>>  Andriy Redko



>> DK> We just got the final releases of WSS4J and the JAX-RS api and I’ve also 
>> just managed to figure out how to get
>> DK> atmosphore and the latest Jetty releases to play nicely together.   Also 
>> considering it’s 4pm my time on a Friday
>> DK> before a long weekend, I’m not going to start the 3.2 build.   I think 
>> it’s best to delay until Tuesday to give the updates and such a chance to be 
>> tested.

>> DK> Dan




 On Aug 10, 2017, at 12:22 PM, Daniel Kulp  wrote:


 It’s been over two years since 3.1.0 was released which is a long time.
 I’d like to get 3.2.0 out shortly.   Looking through things, the major 
 outstanding things are snapshots of a couple deps (xjc-utils,build-utils, 
 wss4j) and updates to the JAX-RS stuff to use the released 2.1.   What 
 else do folks have outstanding that would be “needed” to get into 3.2?
 Would Sept 1st be a good target for getting 3.2 built?   That would give 
 use a few weeks to finish things up and get the releases out.

 Thoughts?

 -- 
 Daniel Kulp
 dk...@apache.org - http://dankulp.com/blog
 Talend Community Coder - http://coders.talend.com

Re: CXF 3.2?

[Sergey Beryozkin]

Hey Andriy

IMHO it might wait till 3.2.1 (may be we can do a camel cxf demo making 
sure the context can flow from Camel to CXF and vice versa) as a POC and 
tweak few things along the way ? If we doc it right now in a bit of a 
hurry then we will have less space for the changes ?


Thanks, Sergey
On 04/09/17 21:22, Andriy Redko wrote:

Hey Dan,

Sorry for last minute thing (always pops up), do I have time to push this
guy https://issues.apache.org/jira/browse/CXF-7439? I am mostly done with the 
implementation,
need couple of more days to add a sample project and update the documentation. 
It is considerably
large chunk of the code, no urgency to have it in 3.2 really (could go to 
3.2.1). Just appreciate
the opinions, it is worth to delay a build for a couple of more days (Wed/Thu) 
or not.

Thanks!

Best Regards,
 Andriy Redko



DK> We just got the final releases of WSS4J and the JAX-RS api and I’ve also 
just managed to figure out how to get
DK> atmosphore and the latest Jetty releases to play nicely together.   Also 
considering it’s 4pm my time on a Friday
DK> before a long weekend, I’m not going to start the 3.2 build.   I think it’s 
best to delay until Tuesday to give the updates and such a chance to be tested.

DK> Dan





On Aug 10, 2017, at 12:22 PM, Daniel Kulp  wrote:




It’s been over two years since 3.1.0 was released which is a long time.I’d 
like to get 3.2.0 out shortly.   Looking through things, the major outstanding 
things are snapshots of a couple deps (xjc-utils,build-utils, wss4j) and 
updates to the JAX-RS stuff to use the released 2.1.   What else do folks have 
outstanding that would be “needed” to get into 3.2?Would Sept 1st be a good 
target for getting 3.2 built?   That would give use a few weeks to finish 
things up and get the releases out.



Thoughts?



--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: CXF 3.2?

[Andriy Redko]

Hey Dan,

Sorry for last minute thing (always pops up), do I have time to push this 
guy https://issues.apache.org/jira/browse/CXF-7439? I am mostly done with the 
implementation,
need couple of more days to add a sample project and update the documentation. 
It is considerably
large chunk of the code, no urgency to have it in 3.2 really (could go to 
3.2.1). Just appreciate 
the opinions, it is worth to delay a build for a couple of more days (Wed/Thu) 
or not.

Thanks!

Best Regards,
Andriy Redko



DK> We just got the final releases of WSS4J and the JAX-RS api and I’ve also 
just managed to figure out how to get
DK> atmosphore and the latest Jetty releases to play nicely together.   Also 
considering it’s 4pm my time on a Friday
DK> before a long weekend, I’m not going to start the 3.2 build.   I think it’s 
best to delay until Tuesday to give the updates and such a chance to be tested.

DK> Dan




>> On Aug 10, 2017, at 12:22 PM, Daniel Kulp  wrote:


>> It’s been over two years since 3.1.0 was released which is a long time.
>> I’d like to get 3.2.0 out shortly.   Looking through things, the major 
>> outstanding things are snapshots of a couple deps (xjc-utils,build-utils, 
>> wss4j) and updates to the JAX-RS stuff to use the released 2.1.   What else 
>> do folks have outstanding that would be “needed” to get into 3.2?Would 
>> Sept 1st be a good target for getting 3.2 built?   That would give use a few 
>> weeks to finish things up and get the releases out.

>> Thoughts?

>> -- 
>> Daniel Kulp
>> dk...@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com

Re: CXF 3.2?

[Dennis Kieselhorst]

Ok, just pushed some dependency updates and will try to fix some bugs
until Tuesday.

Btw. as this will be a new major version, we should involve Sally to
prepare a press release.

Regards
Dennis

Re: CXF 3.2?

[Sergey Beryozkin]

We can get it for 3.2.1 for ex, swagger-core + swagger-jaxrs which 
interacts with the new swagger-core would need to be available, so it is 
a bit tight...


Sergey
On 10/08/17 20:37, Dennis Kieselhorst wrote:

Good plan. I'd like to see support for Swagger/ OpenAPI Spec 3.0.0 in
CXF 3.2 but we should postpone it if no updated swagger-core library is
available by Sept 1st.

Regards
Dennis




--
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Re: SSE module missing from CXF 3.2.X snapshot?

[Andriy Redko]

Hi Andy,

SSE should be set now, the relevant change made its way into master.
Thanks!

Best Regards,
Andriy Redko

AM> Thanks Andriy!


AM> On Wed, Jul 19, 2017 at 9:35 PM Andriy Redko <drr...@gmail.com> wrote:


AM> Hi Andy,
AM>  
AM>  That would be my fault, my apologies. I will take care of this issue
AM>  so SSE module would be included as part of the ZIP distribution. Thanks
AM>  for spotting it.
AM>  
AM>  Best Regards,
AM>  Andriy Redko
AM>  
 AM>> Hi All,
AM>  
 AM>> I'm starting to play with some of the SSE stuff as part of JAX-RS 2.1, and
 AM>> I've noticed that the rt-rs-sse module is not in the CXF 3.2.X snapshot
 AM>> ZIPs available here:
 AM>> 
http://repository.apache.org/snapshots/org/apache/cxf/apache-cxf/3.2.0-SNAPSHOT/
AM>  
 AM>> I have been able to build the module locally, but I'm hoping to be able to
 AM>> point customers to a single ZIP file that contains all of the modules in
 AM>> use.
AM>  
 AM>> If there is some build/packaging steps that need to be performed to 
include
 AM>> the SSE module, I'd be happy to do the work - but hopefully somebody can
 AM>> point me in the right direction to get started.
AM>  
 AM>> Thanks,
AM>  
 AM>> Andy
AM>  
AM>  

Re: SSE module missing from CXF 3.2.X snapshot?

[Andy McCright]

Thanks Andriy!

On Wed, Jul 19, 2017 at 9:35 PM Andriy Redko <drr...@gmail.com> wrote:

> Hi Andy,
>
> That would be my fault, my apologies. I will take care of this issue
> so SSE module would be included as part of the ZIP distribution. Thanks
> for spotting it.
>
> Best Regards,
> Andriy Redko
>
> AM> Hi All,
>
> AM> I'm starting to play with some of the SSE stuff as part of JAX-RS 2.1,
> and
> AM> I've noticed that the rt-rs-sse module is not in the CXF 3.2.X snapshot
> AM> ZIPs available here:
> AM>
> http://repository.apache.org/snapshots/org/apache/cxf/apache-cxf/3.2.0-SNAPSHOT/
>
> AM> I have been able to build the module locally, but I'm hoping to be
> able to
> AM> point customers to a single ZIP file that contains all of the modules
> in
> AM> use.
>
> AM> If there is some build/packaging steps that need to be performed to
> include
> AM> the SSE module, I'd be happy to do the work - but hopefully somebody
> can
> AM> point me in the right direction to get started.
>
> AM> Thanks,
>
> AM> Andy
>
>

Re: SSE module missing from CXF 3.2.X snapshot?

[Andriy Redko]

Hi Andy,

That would be my fault, my apologies. I will take care of this issue 
so SSE module would be included as part of the ZIP distribution. Thanks 
for spotting it.

Best Regards,
Andriy Redko

AM> Hi All,

AM> I'm starting to play with some of the SSE stuff as part of JAX-RS 2.1, and
AM> I've noticed that the rt-rs-sse module is not in the CXF 3.2.X snapshot
AM> ZIPs available here:
AM> 
http://repository.apache.org/snapshots/org/apache/cxf/apache-cxf/3.2.0-SNAPSHOT/

AM> I have been able to build the module locally, but I'm hoping to be able to
AM> point customers to a single ZIP file that contains all of the modules in
AM> use.

AM> If there is some build/packaging steps that need to be performed to include
AM> the SSE module, I'd be happy to do the work - but hopefully somebody can
AM> point me in the right direction to get started.

AM> Thanks,

AM> Andy

SSE module missing from CXF 3.2.X snapshot?

[Andy McCright]

Hi All,

I'm starting to play with some of the SSE stuff as part of JAX-RS 2.1, and
I've noticed that the rt-rs-sse module is not in the CXF 3.2.X snapshot
ZIPs available here:
http://repository.apache.org/snapshots/org/apache/cxf/apache-cxf/3.2.0-SNAPSHOT/

I have been able to build the module locally, but I'm hoping to be able to
point customers to a single ZIP file that contains all of the modules in
use.

If there is some build/packaging steps that need to be performed to include
the SSE module, I'd be happy to do the work - but hopefully somebody can
point me in the right direction to get started.

Thanks,

Andy

Re: CXF 3.2 support jetty9 only (drop jetty8 support)

[Sergey Beryozkin]

Hope it can be released at around the end of January, may be a couple of 
weeks later.


Sergey
On 22/12/16 14:54, Guillaume Nodet wrote:

Btw, what's the ETA for CXF 3.2 ?

2016-12-22 14:30 GMT+01:00 Daniel Kulp <dk...@apache.org>:



I’d be fine with that.   Everyone has pretty much moved on from the Karaf
2.x versions that only have Jetty8.   As long as we can support the Jetty
version in Karaf 4.0.x, I’m fine.

Dan



On Dec 21, 2016, at 10:45 PM, Freeman Fang <freeman.f...@gmail.com>

wrote:


Hi Team,

We have several issues(like CXF-7160 and CXF-7179) recently which is

caused by Jetty9 & Jetty8 API imcompatible, though we should be able to
handle this by reflection on CXF 3.1.x,  for the coming CXF 3.2 how about
we support Jetty9(drop Jetty8 support)  only? This can relieve some burden
supporting both Jetty8 & Jetty9 in CXF http-jetty transport.


A couple of more reasons CXF 3.2 should support Jetty 9 only
1. Jetty8 was EOL at end of 2014 and no further work on jetty 8
2. benchmark showed Jetty9 is 30% faster than Jetty8 on server side due

to the big changes in IO layers

3. Jetty community strongly suggest to use Jetty9
4. pax-web support Jetty9 for a long time, so align the jetty version

seems more reasonable.


Any thoughts?

Thanks!
－
Freeman(Yue) Fang

Red Hat, Inc.
FuseSource is now part of Red Hat





--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: CXF 3.2 support jetty9 only (drop jetty8 support)

[Andrey Redko]

+1 to this idea, haven't seen Jetty 8 in while in many projects, Jetty 9
would be a way to go I think 
Thanks!

Best Regards,
Andriy Redko

On Wed, Dec 21, 2016 at 10:45 PM, Freeman Fang <freeman.f...@gmail.com>
wrote:

> Hi Team,
>
> We have several issues(like CXF-7160 and CXF-7179) recently which is
> caused by Jetty9 & Jetty8 API imcompatible, though we should be able to
> handle this by reflection on CXF 3.1.x,  for the coming CXF 3.2 how about
> we support Jetty9(drop Jetty8 support)  only? This can relieve some burden
> supporting both Jetty8 & Jetty9 in CXF http-jetty transport.
>
> A couple of more reasons CXF 3.2 should support Jetty 9 only
> 1. Jetty8 was EOL at end of 2014 and no further work on jetty 8
> 2. benchmark showed Jetty9 is 30% faster than Jetty8 on server side due to
> the big changes in IO layers
> 3. Jetty community strongly suggest to use Jetty9
> 4. pax-web support Jetty9 for a long time, so align the jetty version
> seems more reasonable.
>
> Any thoughts?
>
> Thanks!
> －
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
>
>
>
>

Re: CXF 3.2 support jetty9 only (drop jetty8 support)

[Guillaume Nodet]

Btw, what's the ETA for CXF 3.2 ?

2016-12-22 14:30 GMT+01:00 Daniel Kulp <dk...@apache.org>:

>
> I’d be fine with that.   Everyone has pretty much moved on from the Karaf
> 2.x versions that only have Jetty8.   As long as we can support the Jetty
> version in Karaf 4.0.x, I’m fine.
>
> Dan
>
>
> > On Dec 21, 2016, at 10:45 PM, Freeman Fang <freeman.f...@gmail.com>
> wrote:
> >
> > Hi Team,
> >
> > We have several issues(like CXF-7160 and CXF-7179) recently which is
> caused by Jetty9 & Jetty8 API imcompatible, though we should be able to
> handle this by reflection on CXF 3.1.x,  for the coming CXF 3.2 how about
> we support Jetty9(drop Jetty8 support)  only? This can relieve some burden
> supporting both Jetty8 & Jetty9 in CXF http-jetty transport.
> >
> > A couple of more reasons CXF 3.2 should support Jetty 9 only
> > 1. Jetty8 was EOL at end of 2014 and no further work on jetty 8
> > 2. benchmark showed Jetty9 is 30% faster than Jetty8 on server side due
> to the big changes in IO layers
> > 3. Jetty community strongly suggest to use Jetty9
> > 4. pax-web support Jetty9 for a long time, so align the jetty version
> seems more reasonable.
> >
> > Any thoughts?
> >
> > Thanks!
> > －
> > Freeman(Yue) Fang
> >
> > Red Hat, Inc.
> > FuseSource is now part of Red Hat
> >
> >
> >
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>


-- 

Guillaume Nodet

Red Hat, Open Source Integration

Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Re: CXF 3.2 support jetty9 only (drop jetty8 support)

[James Carman]

+1.  As long as karaf 4.0.x isn't impacted, I'm cool with this.

On Thu, Dec 22, 2016 at 8:30 AM Daniel Kulp <dk...@apache.org> wrote:



I’d be fine with that.   Everyone has pretty much moved on from the Karaf
2.x versions that only have Jetty8.   As long as we can support the Jetty
version in Karaf 4.0.x, I’m fine.



Dan





> On Dec 21, 2016, at 10:45 PM, Freeman Fang <freeman.f...@gmail.com> wrote:

>

> Hi Team,

>

> We have several issues(like CXF-7160 and CXF-7179) recently which is
caused by Jetty9 & Jetty8 API imcompatible, though we should be able to
handle this by reflection on CXF 3.1.x,  for the coming CXF 3.2 how about
we support Jetty9(drop Jetty8 support)  only? This can relieve some burden
supporting both Jetty8 & Jetty9 in CXF http-jetty transport.

>

> A couple of more reasons CXF 3.2 should support Jetty 9 only

> 1. Jetty8 was EOL at end of 2014 and no further work on jetty 8

> 2. benchmark showed Jetty9 is 30% faster than Jetty8 on server side due
to the big changes in IO layers

> 3. Jetty community strongly suggest to use Jetty9

> 4. pax-web support Jetty9 for a long time, so align the jetty version
seems more reasonable.

>

> Any thoughts?

>

> Thanks!

> －

> Freeman(Yue) Fang

>

> Red Hat, Inc.

> FuseSource is now part of Red Hat

>

>

>



--

Daniel Kulp

dk...@apache.org - http://dankulp.com/blog

Talend Community Coder - http://coders.talend.com

CXF 3.2 support jetty9 only (drop jetty8 support)

[Freeman Fang]

Hi Team,

We have several issues(like CXF-7160 and CXF-7179) recently which is caused by 
Jetty9 & Jetty8 API imcompatible, though we should be able to handle this by 
reflection on CXF 3.1.x,  for the coming CXF 3.2 how about we support 
Jetty9(drop Jetty8 support)  only? This can relieve some burden supporting both 
Jetty8 & Jetty9 in CXF http-jetty transport. 

A couple of more reasons CXF 3.2 should support Jetty 9 only
1. Jetty8 was EOL at end of 2014 and no further work on jetty 8
2. benchmark showed Jetty9 is 30% faster than Jetty8 on server side due to the 
big changes in IO layers
3. Jetty community strongly suggest to use Jetty9
4. pax-web support Jetty9 for a long time, so align the jetty version seems 
more reasonable.

Any thoughts?

Thanks!
－
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat