Re: CXF 3.2?
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 >
[GitHub] cxf issue #311: Added switch to disable the generation of a Lifetime element...
Github user vpopescu commented on the issue: https://github.com/apache/cxf/pull/311 Not sure I understand the error. Did I do something wrong? ---
Re: cxf git commit: fixed NPE
> Thanks Dennis, you were right when you were talking about simplifying > > the code and having the default licenses removed :-)> Hehe never mind, I should have reviewed the code instead of just testing the functionality... :-) Regards Dennis
Re: CXF 3.2?
> The spring-boot-sample-rs-scan-app example is failing. Can someone look at that? Just fixed it. Cheers Dennis
Re: cxf git commit: fixed NPE
Thanks Dennis, you were right when you were talking about simplifying the code and having the default licenses removed :-) Cheers, Sergey On 05/09/17 20:32, d...@apache.org wrote: Repository: cxf Updated Branches: refs/heads/master 70ac8edcc -> 3453c6cca fixed NPE Project: http://git-wip-us.apache.org/repos/asf/cxf/repo Commit: http://git-wip-us.apache.org/repos/asf/cxf/commit/3453c6cc Tree: http://git-wip-us.apache.org/repos/asf/cxf/tree/3453c6cc Diff: http://git-wip-us.apache.org/repos/asf/cxf/diff/3453c6cc Branch: refs/heads/master Commit: 3453c6ccac9bb829af8ecc65823e66b68db3e831 Parents: 70ac8ed Author: Dennis Kieselhorst Authored: Tue Sep 5 21:32:27 2017 +0200 Committer: Dennis Kieselhorst Committed: Tue Sep 5 21:32:27 2017 +0200 -- .../main/java/org/apache/cxf/jaxrs/swagger/Swagger2Feature.java| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cxf/blob/3453c6cc/rt/rs/description-swagger/src/main/java/org/apache/cxf/jaxrs/swagger/Swagger2Feature.java -- diff --git a/rt/rs/description-swagger/src/main/java/org/apache/cxf/jaxrs/swagger/Swagger2Feature.java b/rt/rs/description-swagger/src/main/java/org/apache/cxf/jaxrs/swagger/Swagger2Feature.java index 33ee47c..4679e6e 100644 --- a/rt/rs/description-swagger/src/main/java/org/apache/cxf/jaxrs/swagger/Swagger2Feature.java +++ b/rt/rs/description-swagger/src/main/java/org/apache/cxf/jaxrs/swagger/Swagger2Feature.java @@ -305,7 +305,7 @@ public class Swagger2Feature extends AbstractSwaggerFeature { if (theLicense == null && !licenseWasSet) { if (props != null) { theLicense = props.getProperty(LICENSE_PROPERTY); -if (theLicense.isEmpty()) { +if (theLicense != null && theLicense.isEmpty()) { theLicense = null; } } else {
Re: CXF 3.2?
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
[GitHub] cxf pull request #311: Added switch to disable the generation of a Lifetime ...
GitHub user vpopescu opened a pull request: https://github.com/apache/cxf/pull/311 Added switch to disable the generation of a Lifetime element in a cla⦠Added a boolean to disable the generation of the Lifetime element in the STS response. Default is true (don't disable) to match existing behaviour. Discussed here by a team member: http://cxf.547215.n5.nabble.com/STS-removing-Lifetime-from-response-tc5782461.html You can merge this pull request into a Git repository by running: $ git pull https://github.com/vpopescu/cxf master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cxf/pull/311.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #311 commit 272d085f9e0ff1941341ef68767781c8995ecdee Author: HP Date: 2017-09-05T05:53:26Z Added switch to disable the generation of a Lifetime element in a class derived from AbstractOperation. ---