Deprecate aegis databinding ?

Hi all, I am not sure if it's the time to deprecate some old cxf things that no one is using, so I write to get your thoughts/ideas here. The first I can think of is aegis databinding. Is the aegis databinding still used by CXF users ? Is it a good time to deprecate and remove in the future

Re: [VOTE] - Release Apache CXF Fediz 1.6.2

+1 On Thu, Mar 21, 2024 at 6:15 PM Colm O hEigeartaigh wrote: > This is a vote to release Apache CXF Fediz 1.6.2. It contains > dependency updates as well as a bug fix for a session timeout in newer > Tomcat instances https://issues.apache.org/jira/browse/FEDIZ-256 > > Artifacts: >

Re: [VOTE] Release CXF 3.6.3 and 3.5.8

+1 On Fri, Mar 8, 2024 at 4:43 AM Freeman Fang wrote: > Hi, > > It’s been a while since the last releases and many issues have been > addressed, so here is the VOTE for CXF 3.6.3 and 3.5.8 > > Staging areas: > https://repository.apache.org/content/repositories/orgapachecxf-1198 >

Re: [VOTE] Release CXF 4.0.4(2nd attempt)

+1 On Thu, Mar 7, 2024 at 8:48 AM Freeman Fang wrote: > It’s been a while since the last release and many issues have been > addressed, so here is the VOTE for CXF 4.0.4. > > Staging area: > https://repository.apache.org/content/repositories/orgapachecxf-1197 > > > Tag: > >

Re: [VOTE] Release CXF 4.0.4

+1 On Wed, Mar 6, 2024 at 5:58 AM Freeman Fang wrote: > It’s been a while since the last release and many issues have been > addressed, so here is the VOTE for CXF 4.0.4. > > Staging area: > https://repository.apache.org/content/repositories/orgapachecxf-1196 > > > Tag: > >

Deprecate jaxws21 frontend in wsdl2java

Hi all, When the "-frontend jaxws21" is passed to wsdl2java tool, it doesn't work and there is error from jaxb xjc: . */wsdl2java -verbose TestService.wsdlLoading FrontEnd jaxws ...Loading DataBinding jaxb ...wsdl2java -verbose TestService.wsdlwsdl2java - Apache CXF

Re: [VOTE] CXF 4.0.3/3.6.2/3.5.7

+1 On Thu, Sep 14, 2023 at 1:49 AM Daniel Kulp wrote: > It’s been three months since the last releases so definitely time to get > more fixes out there. > > Staging areas: > https://repository.apache.org/content/repositories/orgapachecxf-1192/ >

HTTP client backward compatible issue in CXF 4.0.1

Hi all, When I upgraded the CXF 4.0.1 in JBossWS and the some of the tests failed because the client sends out some strange request which mixed the HTTP/1.1 and HTTP/2 in request headers: POST /jaxws-securityDomain2/authz HTTP/1.1 Connection: Upgrade, HTTP2-Settings Content-Length: 207 Host:

Re: [VOTE] CXF 3.5.6, 3.6.0, 4.0.1

+1 On Wed, May 3, 2023 at 5:02 AM Daniel Kulp wrote: > > It’s been quite a while since the last round of releases and a bunch of > work has been done, lots of bug fixes, a couple of new features, etc… > > > Tags: > https://github.com/apache/cxf/releases/tag/cxf-4.0.1 ( >

Re: [RESULT] [VOTE] Apache CXF 4.0.0

Happy new year, everyone ! I see the CXF 4.0.0 release note isn't finalized : https://issues.apache.org/jira/projects/CXF/versions/12351115 , and we didn't announce this release in https://cxf.apache.org/ .

Re: [VOTE] - Release Apache CXF Fediz 1.6.1

+1 On Tue, Dec 20, 2022 at 12:53 AM Colm O hEigeartaigh wrote: > This is a vote to release Apache CXF Fediz 1.6.1. The main features > are dependency updates (e.g. CXF 3.5.5) to pick up CVE fixes: > > Artifacts: > https://repository.apache.org/content/repositories/orgapachecxf-1186/ > Git tag:

Re: [VOTE] Apache CXF 4.0.0

+1. Thanks everyone! On Sun, Dec 18, 2022 at 11:26 PM Daniel Kulp wrote: > This is a vote to release CXF 4.0.0.This is a major release that > completely changes the API from using the older javax.* packages to using > the jakarta.* versions. It also updates everything to more modern >

Re: CXF 4.0.0 jakarta release

7), but many > don’t actually work. None of the JMS samples seem to work at all. > Some are still setup to use activemq (might be OK, but the class path > doesn’t have activemq) and others that are setup for Artemis don’t have > proper spring bean configuration for it and the co

Re: CXF 4.0.0 jakarta release

Thanks for the update, Dan. Are these basic tests failed because Spring6 is built with java17 and it isn't compatible with java11 anymore ? On Mon, Dec 12, 2022 at 11:01 AM Daniel Kulp wrote: > > On Dec 11, 2022, at 9:36 PM, Jim Ma wrote: > > > > Hi Andriy, > > Tha

Re: CXF 4.0.0 jakarta release

xf/pull/1033 > >> >> > >> >> Best Regards, > >> >> Andriy Redko > >> >> > >> >> > I'm done now in terms of any remaining fixes for the next > >> >> > releases...not sure if @Andriy Redko has anything

Re: CXF 4.0.0 jakarta release

else planned? > >> > >> > Colm. > >> > >> > On Wed, Nov 30, 2022 at 10:48 AM Colm O hEigeartaigh > >> > wrote: > >> >> It works for me as well. I'm coordinating with @Andriy Redko on two > >> >> fixes that remain f

Re: [VOTE] CXF 3.5.5 and 3.4.10

+1 On Thu, Dec 8, 2022 at 5:21 AM Daniel Kulp wrote: > > I was only able to get the 3.4 and 3.5 patch releases built today, but I’d > like to go ahead and get the vote started for them. > > > This is a vote to release the latest set of patched for CXF. > > > Staging repositories: > 3.5.5 >

Re: CXF 4.0.0 jakarta release

at would give a week to get any final updates in. > > > > Dan > > > > > > > > > > Thank you guys! > > > > > > > > > Best Regards, > > >Andriy Redko > > > > > > On Sun, Nov 27, 2022, 10:27 PM Jim Ma wro

Re: CXF 4.0.0 jakarta release

ase 4.0.0 even partial release. > > Regards > JB > > On Mon, Nov 7, 2022 at 9:19 AM Jim Ma wrote: > > > > Hi all, > > After 9 months of work, we finally fixed/worked around all issues for > > Jakarta support. Now all the cxf tests are passed: > > https:

Re: CXF 4.0.0 jakarta release

tory). Btw, I believe JakartaEE 9.1 was meant to be used with JDK 8 or > 11; support for JDK 17 is something coming with JakartaEE 10 afair. > > Thanks > > On Tue, Nov 8, 2022 at 1:34 PM Jim Ma wrote: > > > Yes. Spring is optional for CXF runtime for a long time. Now all CX

Re: CXF 4.0.0 jakarta release

;https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > < > https://www.packtpub.com/application-development/java-ee-8-high-performance &

Re: CXF 4.0.0 jakarta release

fully. > > On Mon, Nov 7, 2022 at 12:19 PM Jim Ma wrote: > > > > Hi all, > > After 9 months of work, we finally fixed/worked around all issues for > > Jakarta support. Now all the cxf tests are passed: > > https://ci-builds.apache.org/job/CXF/job/CXF-JDK17/848/ an

Re: [VOTE] - Move Apache CXF DOSGi to the attic

+1 On Tue, Nov 8, 2022 at 10:54 PM Colm O hEigeartaigh wrote: > This is a vote to move Apache CXF DOSGi to the attic. There is very > little activity for many years now (last commit 2.5 years ago - > https://github.com/apache/cxf-dosgi/commits/main). > > Previous discussion thread: >

Re: CXF 4.0.0 jakarta release

ve? If yes, I think we have to make all Spring > > related > > > >>> dependencies optional and document > > > >>> clearly that JDK-17 is needed in case Spring / Spring Boot are > used, > > we > > > >>> surely cannot leave things > > &g

CXF 4.0.0 jakarta release

Hi all, After 9 months of work, we finally fixed/worked around all issues for Jakarta support. Now all the cxf tests are passed: https://ci-builds.apache.org/job/CXF/job/CXF-JDK17/848/ and we can say that CXF successfully migrated to Jakarta namespace(and support Jakarta EE9.1). To get cxf jakarta

Re: [DISCUSS] - Retire CXF DOSGI?

+1. It makes sense to retire it. On Wed, Oct 19, 2022 at 4:49 AM Colm O hEigeartaigh wrote: > Hi all, > > What do you think about moving CXF DOSGI to the attic? There is very > little activity for many years now (last commit 2.5 years ago - > https://github.com/apache/cxf-dosgi/commits/main).

Re: [VOTE] Apache CXF 3.4.9 and 3.5.4

+1 On Wed, Oct 5, 2022 at 5:31 PM Alexey Markevich wrote: > +1 > > On 10/5/22, Jean-Baptiste Onofré wrote: > > +1 (non binding) > > > > Regards > > JB > > > > On Mon, Oct 3, 2022 at 8:05 PM Daniel Kulp wrote: > >> > >> > >> > >> This is a vote to release the latest set of patched for CXF. >

Re: [DISCUSS] CXF 3.5.x and beyond

from my side, thank you. > > > > Best Regards, > > Andriy Redko > > > > On Tue, Sep 27, 2022, 9:31 PM Jim Ma wrote: > >> > >> Hi all, > >> If there is no objection, I will create a branch > "osgi-pre-removal-v4.0" to record the

Re: [DISCUSS] CXF 3.5.x and beyond

dko wrote: > This is great, thanks Jim, I will also take a look shortly. Thanks! > > Best Regards, > Andriy Redko > > On Wed, Sep 21, 2022, 1:02 AM Jim Ma wrote: > >> Hi All, >> I tried to remove the osgi and karaf from CXF with this draft PR : >> https://gith

Re: [DISCUSS] CXF 3.5.x and beyond

>> Best Regards, > >> Andriy Redko > >> > >> JM> Hi Andriy, > >> JM> It looks like we still have to wait for the other dependency jakarta > >> JM> support available, like brave's new release to include this change : > >> JM

Re: [DISCUSS] CXF 3.5.x and beyond

/openzipkin/brave/pull/1344. Do you see any other > JM> dependencies that haven't been released yet except OSGI and Karaf ? > > JM> Thanks, > JM> Jim > > > JM> On Wed, Sep 7, 2022 at 8:11 PM Jim Ma wrote: > > >> Thanks for the informative input, Freeman. > &

Re: [DISCUSS] CXF 3.5.x and beyond

> >> Karaf about this part. > >> And Andriy, you are right, release CXF 4.0 M1 without OSGi/Karaf bit > >> seems the only option we have so far, and I'm +1 for this way > now(Since we > >> don't know how long we need to wait for the proper OSGi spec r

Re: [DISCUSS] CXF 3.5.x and beyond

On Wed, Sep 7, 2022 at 8:11 PM Jim Ma wrote: > Thanks for the informative input, Freeman. > IMO, If we want to decouple OSGI/Karaf, the 4.0 major release is a good > chance to do this job. When OSGI/Karaf jakarta release is ready, > We can look at bringing this back with more

Re: [DISCUSS] CXF 3.5.x and beyond

se CXF 4.0 M1 without OSGi/Karaf bit > seems the only option we have so far, and I'm +1 for this way now(Since we > don't know how long we need to wait for the proper OSGi spec released and > upstream projects can support it). > > Just my 2 cents. > Best Regards > F

Re: [DISCUSS] CXF 3.5.x and beyond

t; JM> have the jakarta namespace artifact released in the near future. > Should we > JM> have some milestone/alpha release > JM> before all these dependencies are available ? And if we want to do a > JM> milestone release, what do you think we should have in > JM

Re: [DISCUSS] CXF 3.5.x and beyond

in this 4.0.0-M1 release ? Thanks, Jim On Wed, Jun 22, 2022 at 10:02 AM Jim Ma wrote: > Thanks Andriy too for driving this and moving forward ! > > On Tue, Jun 21, 2022 at 9:49 AM Andriy Redko wrote: > >> Hey guys, >> >> The Jakarta branch [1] just went int

Re: [VOTE] Apache CXF 3.5.3 and 3.4.8

+1 On Sat, Jun 25, 2022 at 12:18 AM Daniel Kulp wrote: > > > This is a vote to release the latest set of patches for CXF. > > > Staging repositories: > https://repository.apache.org/content/repositories/orgapachecxf-1180/ < >

Re: [DISCUSS] CXF 3.5.x and beyond

ly appreciated. > > Thank you! > > [1] https://github.com/apache/cxf/pull/912 > [2] https://issues.apache.org/jira/browse/CXF-8371 > > Best Regards, > Andriy Redko > > COh> +1 from me. > > COh> Colm. > > COh> On Thu, May 26, 2022 at 2:40 AM

Re: [VOTE] - Release Apache CXF XJC 4.0.0

+1 On Fri, May 27, 2022 at 6:17 PM Alexey Markevich wrote: > +1 > > On 5/27/22, Colm O hEigeartaigh wrote: > > This is a vote to release Apache CXF XJC 4.0.0. This is a major new > > release with support for the jakarta namespace. > > > > Issues fixed: > > >

Re: [DISCUSS] CXF 3.5.x and beyond

scope of dependencies on > >> Spring, even > >> in 3.4.x / 3.5.x release lines. > > >> Thank you. > > >> [1] https://issues.apache.org/jira/browse/CXF-5477 > >> [2] https://github.com/apache/cxf/tree/poc-remove-spring-bp > > >> B

Re: [VOTE] - Release Apache CXF Build Utils 4.0.0

+1 On Mon, May 23, 2022 at 3:52 PM Colm O hEigeartaigh wrote: > This is a vote to release Apache CXF Build Utils 4.0.0. It contains a > security fix to disable DocTypes during XML parsing and an update to > Java 11, with some other minor fixes. > > Artifacts: >

Re: [VOTE] - Release Apache CXF XJC Utils 3.3.2

+1, thanks, Colm! On Fri, May 20, 2022 at 8:41 PM Andriy Redko wrote: > +1, thanks a lot, Colm! > > Best Regards, > Andriy Redko > > COh> This is a vote to release Apache CXF XJC Utils 3.3.2. > > COh> Issues fixed: >

Re: Jakarta build hangs on test

It looks this hang issue is fixed : https://ci-builds.apache.org/job/CXF/job/pipeline/job/CXF-8371/41/#showFailuresLink Regards, Jim On Thu, May 12, 2022 at 9:19 AM Jim Ma wrote: > Hi Andriy, > I'll have a look today and get back to you later. > > Thanks, > Jim > > On Thu,

Re: Jakarta build hangs on test

Hi Andriy, I'll have a look today and get back to you later. Thanks, Jim On Thu, May 12, 2022 at 8:26 AM Andriy Redko wrote: > Hey Jim, > > After this commit [2] the Jakarta builds are started to hang [2] (and > eventually fail). I have > not checked the reason but I could confirm that

Re: Copied classes in cxf-rt-management.jar with JDK11

> Thanks! > Freeman > > On Thu, Apr 21, 2022 at 2:20 AM Jim Ma wrote: > >> I think we can remove this profile from 3.4.x and 3.5.x too. There is no >> reason we should still keep this, right ? >> I tried to build 3.4.x/3.5.x with jdk11, and the Export-Package entry i

Re: Copied classes in cxf-rt-management.jar with JDK11

t; > I mean remove it from CXF 4.x which is JDK11 minimum. > > Freeman > > On Wed, Apr 20, 2022 at 8:45 PM Jim Ma wrote: > >> Hi Freeman, >> Are you saying we can remove this java9-plus profile completely from >> 3.4.x to 4.x? >> >> Cheers, >

Re: Copied classes in cxf-rt-management.jar with JDK11

r JDK8 compatible anymore), I believe we are > safe to remove java9-plus profile in management/pom.xml all together. > > Cheers > Freeman > > On Tue, Apr 19, 2022 at 10:34 PM Jim Ma wrote: > >> Hi Freeman, >> Do you know why we don't require this with JDK8 and only

Re: Copied classes in cxf-rt-management.jar with JDK11

ache.cxf.tracing* > + > > true > > This fine-grained export package can avoid including the package from > cxf-core module. > > Best

Re: Copied classes in cxf-rt-management.jar with JDK11

Thanks Andriy. Jira is filled :https://issues.apache.org/jira/browse/CXF-8695 and PRs are sent. On Sun, Apr 17, 2022 at 9:28 AM Andriy Redko wrote: > Hey Jim, > > This is interesting, I believe it is not needed, only some compiler args > need > tailoring (for JDK-11) but the classes should not

Copied classes in cxf-rt-management.jar with JDK11

When building cxf-rt-management 3.5.1 with JDK11, some api classes are copied to the jar file. It looks like these classes are copied by the maven-bundle-plugin from java9-plus profile : *java9-plus[9,) org.apache.felix

Re: Releases soon?

/jira/browse/CXF-8668 > COh> https://issues.apache.org/jira/browse/CXF-8683 > > COh> Colm. > > COh> On Wed, Apr 6, 2022 at 11:33 AM Jim Ma wrote: > > >> +1 > > >> On Tue, Apr 5, 2022 at 8:59 PM Colm O hEigeartaigh > wrote: > > >>>

Re: Releases soon?

+1 On Tue, Apr 5, 2022 at 8:59 PM Colm O hEigeartaigh wrote: > Hi, > > We've received a JIRA request to get new releases out due to the > recent Spring CVE issue. I think it's reasonable due to the publicity > surrounding the issue, and also we have quite a few issues fixed since > the last

Re: Systest failures with wss4j-3.0.0-SNAPSHOT

t;> Your branch is behind CXF master with regards several commits. I think > >> it would be better if we just worked off one official branch at CXF. > >> @Andriy Redko maybe we should just incorporate > >> https://github.com/apache/cxf/tree/opensaml4 i

Re: Systest failures with wss4j-3.0.0-SNAPSHOT

ook at what's failing with WSS4J 3.0.0? > > Colm. > > On Wed, Mar 23, 2022 at 12:42 PM Jim Ma wrote: > > > > Thanks for the quick fix, Colm. > > > > It seems there is another failure under services/sts/systests/advanced: > > > > [INFO] Running org.apache.cxf.

Re: Systest failures with wss4j-3.0.0-SNAPSHOT

Wed, Mar 23, 2022 at 7:15 PM Colm O hEigeartaigh wrote: > The SAML failures were caused by a hard-coded String in SAMLUtils, I > fixed it in CXF master here: > > https://github.com/apache/cxf/commit/1e90f53f720b76c2dbac910e58ef0b291f98c032 > > Colm. > > On Tue, Mar 22, 2022

Re: Systest failures with wss4j-3.0.0-SNAPSHOT

trying this out. Thanks, Jim On Tue, Mar 22, 2022 at 5:18 PM Colm O hEigeartaigh wrote: > Hi Jim, > > Which branch are you testing this on in CXF? > > Colm. > > On Mon, Mar 21, 2022 at 7:26 AM Jim Ma wrote: > > > > Hi Colm, > > After I upgraded wss4j ve

Systest failures with wss4j-3.0.0-SNAPSHOT

Hi Colm, After I upgraded wss4j version to 3.0.0-SNAPSHOT(jakarta version) in CXF, I got the following ws-security systests failures. Could you please help look at if there is still something we need to fix in wss4j ? Or we need to fix it in CXF ? Thanks, Jim

Re: [Proposal] CXF OSGI Jakarta EE 9.x support

tps://github.com/apache/cxf/tree/CXF-8371. Thanks, Jim On Fri, Mar 4, 2022 at 6:42 PM Grzegorz Grzybek wrote: > Hello > > As long-term OSGi supporter, I'd like to give my +1 for CXF 4.0.0 (?) with > OSGi bits moved to slower-paced github.com/apache/cxf-osgi repo (modules). > > As

[Proposal] CXF OSGI Jakarta EE 9.x support

Hi, I took more time to look at more things about Jakarta EE9.x support work from last week. Like Spring integration code, now OSGI relevant code is in different maven modules : ./core/src/main/java/org/apache/cxf/bus/osgi

Re: [DISCUSS] CXF 3.5.x and beyond

> > Thank you. > > [1] https://issues.apache.org/jira/browse/CXF-5477 > [2] https://github.com/apache/cxf/tree/poc-remove-spring-bp > > Best Regards, > Andriy Redko > > JM> I accidentally clicked the send button, please ignore my previous > email > JM> a

Re: Change default branch to main

+1 On Tue, Feb 1, 2022 at 8:59 PM Colm O hEigeartaigh wrote: > Hi, > > Most other Apache projects I work on (Camel, ActiveMQ, Karaf, etc.) > have switched to use main as the default branch, to align with what > the default branch is for new projects on GitHub etc. I'd like to > propose

Re: [DISCUSS] CXF 3.5.x and beyond

om/apache/cxf/tree/poc-remove-spring-bp > > Best Regards, > Andriy Redko > > JM> I accidentally clicked the send button, please ignore my previous > email > JM> and look at this reply. > > JM> On Sat, Jan 29, 2022 at 7:58 PM Jim Ma wrote: > > > &g

Re: [DISCUSS] CXF 3.5.x and beyond

I accidentally clicked the send button, please ignore my previous email and look at this reply. On Sat, Jan 29, 2022 at 7:58 PM Jim Ma wrote: > > > > On Mon, Dec 27, 2021 at 10:49 PM Andriy Redko wrote: > >> Hey guys, >> >> A bunch of good things have

Re: [DISCUSS] CXF 3.5.x and beyond

; is JDK17 baseline for Spring Framework & Co, that could be a bummer > but > >> I > >> >> have the feeling that > >> >> it will be lowered to JDK11. Thank you. > > >> >> Best Regards, > >> >> Andriy Redko > > >

Re: Release 3.5.0 next week?

+! On Thu, Dec 9, 2021 at 2:25 AM Romain Manni-Bucau wrote: > +1 > > Romain Manni-Bucau > @rmannibucau | Blog > | Old Blog > | Github < > https://github.com/rmannibucau> | > LinkedIn

Re: [VOTE] Apache CXF 3.4.5 and 3.3.12

+1 On Thu, Sep 30, 2021 at 7:46 AM Freeman Fang wrote: > +1 (binding) > Thanks Dan! > > Freeman > > On Wed, Sep 29, 2021 at 5:00 PM Daniel Kulp wrote: > > > > > This is a vote to release CXF 3.4.5 and 3.3.12. We have fixed over 34 > > issues and it’s been over 2 months since the last

Re: [DISCUSS] CXF 3.5.x and beyond

Wed, Sep 8, 2021 at 8:55 AM Jim Ma wrote: > > > On Tue, Sep 7, 2021 at 4:56 AM Andriy Redko wrote: > >> Hey Jim, >> >> No, we don't have a branch just yet, primarily because we depend on the >> few >> snapshots in 3.5.0/master. >> >> @Colm

Re: Releases next week?

+1 for 3.4.5 and 3.3.12 release. On Fri, Sep 24, 2021 at 1:41 PM Colm O hEigeartaigh wrote: > Hey Andriy, > > If possible I'd like a little more time on 3.5.0 (a month?). I'd love > to get new major releases of XML Security and WSS4J out. But we could > get the 3.4.x + 3.3.x patch releases out

Re: [DISCUSS] CXF 3.5.x and beyond

rta ee9 will come in Q4 2022 : > >> JM> > >> > https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6 > > >> JM> On Fri, Sep 3, 2021 at 6:20 PM Romain Manni-Bucau < > >> rmannibu...@gmail.com> > >>

Re: [DISCUSS] CXF 3.5.x and beyond

og/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6 > > JM> On Fri, Sep 3, 2021 at 6:20 PM Romain Manni-Bucau < > rmannibu...@gmail.com> > JM> wrote: > > > > > >> Le ven. 3 sept. 2021 à 11:30, Jim Ma a écrit : > > > > &g

Re: [DISCUSS] CXF 3.5.x and beyond

On Fri, Sep 3, 2021 at 6:20 PM Romain Manni-Bucau wrote: > > > > Le ven. 3 sept. 2021 à 11:30, Jim Ma a écrit : > >> >> >> On Wed, Aug 25, 2021 at 9:39 PM Romain Manni-Bucau >> wrote: >> >>> >>> >>> Le mer. 25 août 2021 à 13:

Re: [DISCUSS] CXF 3.5.x and beyond

On Wed, Aug 25, 2021 at 9:39 PM Romain Manni-Bucau wrote: > > > Le mer. 25 août 2021 à 13:39, Jim Ma a écrit : > >> >> >> On Fri, Aug 20, 2021 at 2:10 PM Romain Manni-Bucau >> wrote: >> >>> >>> >>> Le jeu. 19 août 2021

Re: [DISCUSS] CXF 3.5.x and beyond

On Fri, Aug 20, 2021 at 2:10 PM Romain Manni-Bucau wrote: > > > Le jeu. 19 août 2021 à 22:45, Andriy Redko a écrit : > >> Hi Romain, >> >> Sorry for the delayed response. I have been thinking about your (and Jim) >> suggestions >> and came to surprising conclusion: do we actually need to

Re: [DISCUSS] CXF 3.5.x and beyond

On Wed, Aug 11, 2021 at 8:26 PM Andriy Redko wrote: > Hey Jim, Romain, > > Thank you guys, I think Romain's suggestion to move 3.5.x to JDK-11 > baseline is good idea, we would > still be maintaining 3.4.x for a while, covering JDK-8 based deployments. > Regarding Jakarta, yes, I > certainly

Re: [DISCUSS] CXF 3.5.x and beyond

On Wed, Aug 11, 2021 at 8:26 PM Andriy Redko wrote: > Hey Jim, Romain, > > Thank you guys, I think Romain's suggestion to move 3.5.x to JDK-11 > baseline is good idea, we would > still be maintaining 3.4.x for a while, covering JDK-8 based deployments. > Regarding Jakarta, yes, I > certainly

Re: [DISCUSS] CXF 3.5.x and beyond

On Wed, Aug 11, 2021 at 10:05 AM Andriy Redko wrote: > Hey guys, > > I would like to initiate (or better to say, resume) the discussion > regarding CXF 3.5.x and beyond. > The 3.5.x has been in the making for quite a while but has not seen any > releases yet. As far as > I know, we have only

Re: [VOTE] Apache CXF 3.4.3 and 3.3.10

+1 On Tue, Mar 16, 2021 at 4:59 AM Daniel Kulp wrote: > > This is a vote to release CXF 3.4.3 and 3.3.10. We have fixed over 20 > issues and it’s been almost 3 months since the last releases. > > > Staging repositories: > https://repository.apache.org/content/repositories/orgapachecxf-1164/

release 3.3.10 soon ?

There are a couple of important fixes and dependency upgrades in 3.3.x branch. Any plan to cut a 3.3.10 release ? Thanks, Jim

Re: [VOTE] CXF 3.4.2/3.3.9

+1. On Thu, Dec 24, 2020 at 4:00 PM Alexey Markevich wrote: > +1 > > On 12/24/20, Romain Manni-Bucau wrote: > > +1 (non binding) > > > > Romain Manni-Bucau > > @rmannibucau | Blog > > | Old Blog > >

Re: CXF-8378: Backward compatible issue in 3.4.1 and 3.3.8

t; with the fix, so users can upgrade to that version instead if they are > using CXFAuthenticator. > > Colm. > > On Thu, Nov 26, 2020 at 1:53 AM Jim Ma wrote: > >> Hi Colm, >> Just to add more things, if cxf client with CXFAuthenticator is running >> in a co

Re: CXF-8378: Backward compatible issue in 3.4.1 and 3.3.8

can we add some note and let the community know this backward compatible issue in 3.3.8 and 3.4.1 ? Cheers, Jim On Mon, Nov 23, 2020 at 3:58 PM Jim Ma wrote: > Hi Colm, > I think this commit [1] caused the regression. We have some tests for > CXFAuthenticator in CXF, but they ar

Re: CXF-8378: Backward compatible issue in 3.4.1 and 3.3.8

im On Fri, Nov 20, 2020 at 10:08 PM Colm O hEigeartaigh wrote: > Hi Jim, > > Do you know which CXF commit caused the regression. Do we have no tests > for CXFAuthenticator? > > Colm. > > On Fri, Nov 20, 2020 at 11:19 AM Jim Ma wrote: > >> When

CXF-8378: Backward compatible issue in 3.4.1 and 3.3.8

When upgrade cxf to 3.3.8/3.4.1, the cxf client with CXFAuthenticator throws NoClassDefFoundError like following : java.lang.NoClassDefFoundError: org/apache/cxf/common/util/ReflectionUtil at org.apache.cxf.transport.http.ReferencingAuthenticator.tryWith(ReferencingAuthenticator.java:125) at

Re: [VOTE] Apache CXF 3.4.0

+1 On Fri, Aug 21, 2020 at 5:56 PM Colm O hEigeartaigh wrote: > +1. > > Colm. > > On Fri, Aug 21, 2020 at 7:16 AM Romain Manni-Bucau > wrote: > > > +1 > > > > Le ven. 21 août 2020 à 08:12, Jean-Baptiste Onofre a > > écrit : > > > > > +1 (non binding) > > > > > > Regards > > > JB > > > > > > >

Re: [VOTE] CXF 3.3.7 and 3.2.14

+1 On Thu, Jun 25, 2020 at 2:53 AM Dennis Kieselhorst wrote: > +1 > > Thanks > Dennis >

Re: [VOTE] CXF 3.3.6 and 3.2.13

The maven-plugins/wadl2java-plugin/target/it/wadl-generate-rx/build.log has this failure: [ERROR] Plugin org.apache.cxf:cxf-wadl2java-plugin:3.3.6 or one of its dependencies could not be resolved: Could not find artifact org.apache.cxf:cxf-wadl2java-plugin:jar:3.3.6 Looks like this requires

Re: [VOTE] CXF 3.3.6 and 3.2.13

I tried to build cxf 3.3.6 tag with "mvn clean install -Pfastinstall" and get these failures . [INFO] Build Summary: [INFO] Passed: 0, Failed: 2, Errors: 0, Skipped: 0 [INFO] -[ERROR] The following builds failed:[ERROR] *

Re: [VOTE] Apache CXF 3.3.5 and 3.2.12

+1 On Sat, Jan 11, 2020 at 6:29 AM Daniel Kulp wrote: > After a couple of hiccups due to LDAP downtime, I was finally able to get > the builds staged. These releases are long overdue due to the > holidays. Over 30 JIRA issues have been fixed. > > > Tags: > Buildutils-3.4.4: > >

Re: Packaging javax.xml.ws as jakarta.xml.ws

If we have to rename package for JAX-RS, JSONB , JSONP in CXF , then why not for JAX-WS in a major version ? If we leave it behind, we'll lose chance to evolve JAX-WS api in the future. On Wed, Nov 27, 2019 at 2:35 PM David Blevins wrote: > Thanks for the feedback, Romain. > > So everyone has

Re: [VOTE] Apache CXF 3.2.11

+1 On Fri, Oct 25, 2019 at 3:29 AM Jeff Genender wrote: > +1 > > Jeff > > > On Oct 24, 2019, at 9:34 AM, Daniel Kulp wrote: > > > > Colm pointed out to me that we also need a 3.2.11 release. Since > that’s also been 2 months and we fixed 11 JIRA’s, it makes sense. > > > > It’s been over 2

Re: [VOTE] Apache CXF 3.3.4

+1 On Tue, Oct 22, 2019 at 10:57 PM Jeff Genender wrote: > +1 > > Jeff > > > On Oct 21, 2019, at 1:19 PM, Daniel Kulp wrote: > > > > It’s been over 2 months since 3.3.3 was released. We fixed 20 JIRAS. > > > > Staging area: > >

Re: [VOTE] CXF 3.2.10, CXF 3.3.3, and buildutils 3.4.3

+1 On Fri, Aug 9, 2019 at 3:08 PM Alexey Markevich wrote: > +1 > > On 8/8/19, Romain Manni-Bucau wrote: > > +1 (non binding) > > > > Le jeu. 8 août 2019 à 20:57, Dennis Kieselhorst a > écrit : > > > >> +1 > >> > >> Thanks! > >> > >> > > >

LoggingFeature with slf4j

Do you remember why we need slf4j dependency in cxf-rt-features-logging ? Is it because it needs support MDC in https://github.com/apache/cxf/blob/master/rt/features/logging/src/main/java/org/apache/cxf/ext/logging/slf4j/Slf4jEventSender.java ? Can the slf4j logger be replaced with cxf's

Re: Dropping JDK9 / JDK10 jobs from Jenkins

+1 On Thu, May 23, 2019 at 1:58 PM Jean-Baptiste Onofré wrote: > Good idea. +1 > > Regards > JB > > Le 23 mai 2019 à 07:00, à 07:00, Dennis Kieselhorst a > écrit: > >Hi Andriy! > > > >> I think we could drop CXF's JDK9 [0] and JDK10 [1] jobs from Jenkins > >> since these JDKs are officially

Re: Time to release CXF 3.2.9 ?

On Fri, Apr 19, 2019 at 4:11 PM Colm O hEigeartaigh wrote: > Can this JIRA be resolved? https://issues.apache.org/jira/browse/CXF-7990 > Yes. I already updated it to resolved. > > +1 from me. > > Colm. > > On Fri, Apr 19, 2019 at 4:08 AM Jim Ma wrote: > >&

Time to release CXF 3.2.9 ?

Looks we have bunch of issues fixed and improvements since CXF 3.2.8 . Is it time to start a CXF 3.2.9 release ? Thanks, Jim

Re: and Wrapped style

Hi Dan and Colm, Do you have any thoughts on this ? Thanks, Jim On Wed, Mar 6, 2019 at 2:26 PM Jim Ma wrote: > When I tried wsdl2java tool to generate this wrapper element and the > output is a doc-lit-bare style

and Wrapped style

When I tried wsdl2java tool to generate this wrapper element and the output is a doc-lit-bare style method : CXF

Re: Jakarta EE TCKs and compatibility logo

It's a good thing CXF get TCK tests passed. If the logo is not a complicated thing to request, it's better to have. Do we only need to pass standalone JAXWS and JAXRS TCK instead of EE TCK ? On Thu, Feb 28, 2019 at 7:29 AM Colm O hEigeartaigh wrote: > Is anyone interested in taking this on? > >

Re: CXF 3.1.18 release

+1 On Mon, Dec 3, 2018 at 5:54 PM Colm O hEigeartaigh wrote: > OK fair enough. I propose that this might be the last release of 3.1.x > though. > > Colm. > > On Mon, Dec 3, 2018 at 8:14 AM Jim Ma wrote: > > > Hi Colm, > > I need these two fixes : >

  1   2   >