Re: CXF 4.0.0 jakarta release

Since a large majority of the sample are now working with just a few exceptions, we’re likely OK to do the 4.0 release and we can log bugs for the couple of remaining. I’ll try and build the release sometime this weekend so that we can get it fully released before everyone (including me)

Re: CXF 4.0.0 jakarta release

Hey guys, We're getting closer, here is what's left: DK>> jaxrs/basic_oidc DK>> jaxrs/big_query DK>> corba (weird ORB errors with java17, missing transaction classes with java11) DK>> js_browser_client_java_first (ClassNotFoundException: org.eclipse.jetty.util.resource.FileResource) It is

Re: CXF 4.0.0 jakarta release

Fixed these ones: DK> jms_spring_config - hangs on client stop DK> jms_spec_demo - server doesn't start, JNDI, org.apache.activemq.jndi.ActiveMQInitialContextFactory (not artemis) DK> jms_pubsub - broker doesn't start And will pick these ones: DK> jax_rs/websocket - gives "WARNING: Websocket

Re: CXF 4.0.0 jakarta release

Fixed (as part of [1]) all GraalVM samples: DK> jaxws_graalvm DK> jaxws_graalvm_dynamic DK> jax_rs/graalvm_basic Also fixed: DK> jax_rs/description_openapi_v3_spring - classpath? Jackson not found DK> jax_rs/description_openapi_v3_web - classpath? Jackson not found DK>

Re: CXF 4.0.0 jakarta release

I finished going through all the samples.This is what’s left: Problems: jax_rs/description_openapi_microprofile_spring - spring config or claspath issue java.lang.ClassNotFoundException: org.eclipse.microprofile.openapi.models.servers.ServerVariables

Re: CXF 4.0.0 jakarta release

I looked at these 3 corba example failures. The hello-world example has been fixed and the other two examples still have this failure: Caused by: org.omg.CORBA.MARSHAL: FINE: 00810007: Underflow in BufferManagerReadStream after last fragment in message at jdk.proxy3.$Proxy73.endOfStream

Re: CXF 4.0.0 jakarta release

I fixed: sts (some spring bean definition issues) Colm. On Tue, Dec 13, 2022 at 1:15 AM Andriy Redko wrote: > > Thanks Dan, > > Here is my update. > > I have fixed: > ws_notification (jms broker issues) > ws_transaction (spring test runner doesn't actually run the test, not sure > why) >

Re: CXF 4.0.0 jakarta release

Thanks Dan, Here is my update. I have fixed: ws_notification (jms broker issues) ws_transaction (spring test runner doesn't actually run the test, not sure why) I will be working on: jaxws_graalvm jaxws_graalvm_dynamic Not looked yet: corba (weird ORB errors with java17, missing

Re: CXF 4.0.0 jakarta release

> > I passed through all samples to make sure they are compilable and buildable, > but I only > run a handful of them, it would be great to check that all samples do > actually work. > I can take *jms* and *jaxrs* ones, may take a few days though. Sounds like a > plan? If > yes, I will

Re: CXF 4.0.0 jakarta release

Hi Dan, I passed through all samples to make sure they are compilable and buildable, but I only run a handful of them, it would be great to check that all samples do actually work. I can take *jms* and *jaxrs* ones, may take a few days though. Sounds like a plan? If yes, I will create an

Re: CXF 4.0.0 jakarta release

> Yes, as Jim mentioned, most of our tests need JDK-17 to run (because of > Spring 6), > we also need JDK-17 to compile (same reason), but when Spring is not involved > (it is > optional by and large), JDK-11 is sufficient. We do have a number of samples > (bundled > with distribution) that

Re: CXF 4.0.0 jakarta release

Hi Dan, Yes, as Jim mentioned, most of our tests need JDK-17 to run (because of Spring 6), we also need JDK-17 to compile (same reason), but when Spring is not involved (it is optional by and large), JDK-11 is sufficient. We do have a number of samples (bundled with distribution) that run on

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, > > Thanks for the quick update.

Re: CXF 4.0.0 jakarta release

On Dec 11, 2022, at 9:36 PM, Jim Ma wrote: > > Hi Andriy, > Thanks for the quick update. Good to see this is running with the jenkins > pipeline and all tests are green. > Did it include all things for the CXF 4.0.0 release ? I didn’t do the 4.0.0 release as I kind of ran out of time. My

Re: CXF 4.0.0 jakarta release

Hi Andriy, Thanks for the quick update. Good to see this is running with the jenkins pipeline and all tests are green. Did it include all things for the CXF 4.0.0 release ? Thanks, Jim On Mon, Dec 12, 2022 at 10:06 AM Andriy Redko wrote: > Hi Jim, > > I disabled this build (and >

Re: CXF 4.0.0 jakarta release

Hi Jim, I disabled this build (and https://ci-builds.apache.org/job/CXF/job/CXF-JDK19/ as well) because we run pipeline matrix [1] against both JDKs. These builds were quite useful when the main branch was unstable, but the pipeline should be sufficient now. Please let me know if you have

Re: CXF 4.0.0 jakarta release

Did we already start the 4.0 release work ? I saw the CI build for CXF 4.0.0 is disabled now : https://ci-builds.apache.org/job/CXF/job/CXF-JDK17/ and last build result was 7 days ago. On Wed, Dec 7, 2022 at 8:46 PM Andriy Redko wrote: > Hi Colm, > > I still wait for review on [1], if you

Re: CXF 4.0.0 jakarta release

Hi Colm, I still wait for review on [1], if you or/and Dan could take a look, would be great. The [2] could go in today but no user response on [3], may need a bump to next version. Thank you. [1] https://github.com/apache/cxf/pull/1033 [2] https://issues.apache.org/jira/browse/CXF-8799 [3]

Re: CXF 4.0.0 jakarta release

Hi Andriy, What's the status of these open issues? Can they be merged today or else bumped to the next release? Colm. On Fri, Dec 2, 2022 at 6:17 PM Andriy Redko wrote: > > Hey guys, > > I have only these 3 issues to wrap up [1], [2], [3], for all of them > pull requests are opened, waiting

Re: CXF 4.0.0 jakarta release

Hey guys, I have only these 3 issues to wrap up [1], [2], [3], for all of them pull requests are opened, waiting for minor changes / confirmations fixes work. @Dan @Colm appreciate your input on [4] please, this is to eliminate the leak of the REMOVED_MARKER. Thanks! [1]

Re: CXF 4.0.0 jakarta release

I'm done now in terms of any remaining fixes for the next releases...not sure if @Andriy Redko has anything 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 for

Re: CXF 4.0.0 jakarta release

It works for me as well. I'm coordinating with @Andriy Redko on two fixes that remain for 3.5.x/3.4.x and then we should be good to go. Colm. On Wed, Nov 30, 2022 at 10:10 AM Jim Ma wrote: > > Thanks Andriy and Dan ! > > On Mon, Nov 28, 2022 at 10:28 PM Andrey Redko wrote: > > > Works for me,

Re: CXF 4.0.0 jakarta release

Thanks Andriy and Dan ! On Mon, Nov 28, 2022 at 10:28 PM Andrey Redko wrote: > Works for me, thanks a lot Dan! > > Best Regards, > Andriy Redko > > On Mon, Nov 28, 2022, 8:45 AM Daniel Kulp wrote: > > > > > > > > > I don't think anything blocking is left, +1 to move forward! @Colm @Dan > >

Re: CXF 4.0.0 jakarta release

Works for me, thanks a lot Dan! Best Regards, Andriy Redko On Mon, Nov 28, 2022, 8:45 AM Daniel Kulp wrote: > > > > > I don't think anything blocking is left, +1 to move forward! @Colm @Dan > do > > we want to drop 4.0.0 only or make 3.4.x / 3.5.x releases as well? With > > 4.0.0 out and

Re: CXF 4.0.0 jakarta release

> > I don't think anything blocking is left, +1 to move forward! @Colm @Dan do > we want to drop 4.0.0 only or make 3.4.x / 3.5.x releases as well? With > 4.0.0 out and 3.6.0 getting ready to be out soon (hopefully), the 3.4.x is > approaching EOL quickly, could be the last release. I was

Re: CXF 4.0.0 jakarta release

Hi Jim, I don't think anything blocking is left, +1 to move forward! @Colm @Dan do we want to drop 4.0.0 only or make 3.4.x / 3.5.x releases as well? With 4.0.0 out and 3.6.0 getting ready to be out soon (hopefully), the 3.4.x is approaching EOL quickly, could be the last release. Thank you

Re: CXF 4.0.0 jakarta release

Hi Andriy, Can we start the release work if there isn't the major thing left we need to include in CXF 4.0.0 release ? @Daniel Kulp Can you please help do the release when it's convenient for you? Thanks, Jim On Mon, Nov 14, 2022 at 1:18 PM Jean-Baptiste Onofré wrote: > +1 to release

Re: CXF 4.0.0 jakarta release

+1 to release 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://ci-builds.apache.org/job/CXF/job/CXF-JDK17/848/

Re: CXF 4.0.0 jakarta release

Regarding cxf-core split, correct, we won't be able to make it in 4.0.0 but dependencies should be formalized as optional [1] so we won't bring them in unless Spring 6 / Spring Boot 3 is on the picture. Thanks! [1] https://issues.apache.org/jira/browse/CXF-8791 Best Regards, Andriy Redko

Re: CXF 4.0.0 jakarta release

Here we are [1], Dan has created 4.0.0 migration guide a while back, I filled it a bit. Thanks! [1] https://cwiki.apache.org/confluence/display/CXF20DOC/4.0+Migration+Guide Best Regards, Andriy Redko AR> Yes, I will create the page shortly and share on the list. AR> Best Regards, AR>

Re: CXF 4.0.0 jakarta release

Hi Jim, I am not aware of any but @Colm is the source of truth here :-) Thanks! Best Regards, Andriy Redko > We can probably include this upgrade in the CXF 4.1 or later version after > it's released and get into WSS4j. > AFAIK, there is no CXF or WSS4j issue blocked by the OpenSAML 5.0.0

Re: CXF 4.0.0 jakarta release

Yes, I will create the page shortly and share on the list. Best Regards, Andriy Redko JM> +1 to document this when we tag the release. There is a migration guide for JM> each release like: https://cxf.apache.org/docs/35-migration-guide.html. JM> Can we add this update in the 4.0 migration

Re: CXF 4.0.0 jakarta release

+1 to document this when we tag the release. There is a migration guide for each release like: https://cxf.apache.org/docs/35-migration-guide.html. Can we add this update in the 4.0 migration guide ? On Wed, Nov 9, 2022 at 12:28 AM Alessio Soldano wrote: > +1 > > I would suggest to deal with

Re: CXF 4.0.0 jakarta release

On Tue, Nov 8, 2022 at 9:01 PM Romain Manni-Bucau wrote: > Hi, > > Ok so just to clarify it means > 1. the cxf-core split (soap, rs, integration) is postponed > 4.x > +1. > 2. the compiler setting is updated to add release (current setup is only > source/target which does not guarantee that

Re: CXF 4.0.0 jakarta release

We can probably include this upgrade in the CXF 4.1 or later version after it's released and get into WSS4j. AFAIK, there is no CXF or WSS4j issue blocked by the OpenSAML 5.0.0 upgrade. @Colm O hEigeartaigh @Andriy Redko WDYT ? On Mon, Nov 7, 2022 at 9:25 PM Misagh wrote: > Hello all, > > If

Re: CXF 4.0.0 jakarta release

+1 I would suggest to deal with this in documentation, restricting runtime jdk support to JDK17+ is actually going to create problems to some integration (Spring is effectively optional already), while not really giving us much (if you know you use Spring, just use JDK17, no need for it to be

Re: CXF 4.0.0 jakarta release

Hi, Ok so just to clarify it means 1. the cxf-core split (soap, rs, integration) is postponed > 4.x 2. the compiler setting is updated to add release (current setup is only source/target which does not guarantee that compiled with a jdk > version set in pom run on a lower jdk). Romain

Re: CXF 4.0.0 jakarta release

Yes. Spring is optional for CXF runtime for a long time. Now all CXF binary classes/artifacts are all JDK-11 version (class major version 55) as Andriy mentioned we set target/source to JDK-11. I believe this setting on CXF at the moment is the best option: - Users don't need to upgrade the

Re: CXF 4.0.0 jakarta release

Hello, FWIW, Spring isn't mandatory for CXF, cxf-core only depends on spring optionally and we don't need to have spring artifacts on the classpath if we don't want to use spring/spring boot features, and this has been the case for a very long time. Freeman On Mon, Nov 7, 2022 at 1:22 PM

Re: CXF 4.0.0 jakarta release

I was more referencing the long awaited split of cxf-core (it is still the same old content than for the early jaxws time and without a modular design - this is where spring comes from mainly IIRC) so for a 4.0.0 this sounds like a big awaited features (don't start by bringing 1.4M said

Re: CXF 4.0.0 jakarta release

Hi Romain, Thanks a lot for the feedback, just to clarify: we won't be dropping Spring (this is basically another "few months long" effort), it is merely to try to not bring any dependency with JDK-17 baseline (== Spring / Spring Boot at this moment) by default. It would definitely require more

Re: CXF 4.0.0 jakarta release

Think Java 11 is a good baseline as of today - at least to enable Jakarta vendors to use CXF as an implementation and pass tck. +1 to drop spring if it bothers to get a first 4.0.0 release out, we can catch up later like other dropped integrations and core should be exploded anyway, it is way too

Re: CXF 4.0.0 jakarta release

+1 to release CXF 4.0.0. And +1 to release using JDK17 as baseline since we upgraded to Spring 6 and Spring Boot 3. Thanks to all guys involved in this long process! Freeman On Mon, Nov 7, 2022 at 11:10 AM Andriy Redko wrote: > +1 to move forward with release (or milestone), but before that,

Re: CXF 4.0.0 jakarta release

+1 to move forward with release (or milestone), but before that, there is one issue which I would like to bring up and agree us upon. The initial discussion for Jakarta / 4.0.0 [1] concluded on having JDK-11 as a baseline. At the same time, there is a misalignment with Spring 6 / Spring Boot 3

Re: CXF 4.0.0 jakarta release

+1 to release, there are too much forks out there already so better to release partially than not release at all IMHO Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: CXF 4.0.0 jakarta release

Hello all, If possible, I'd like to ask that you allow v4 to ship with a new release of wss4j that would contain this change: https://github.com/apache/ws-wss4j/pull/62 At the moment, OpenSAML v5 is not released yet, but it is anticipated to be GA before end of this year, hopefully. On Mon, Nov

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