Re: [DISCUSS] CXF 3.5.x and beyond

Hey Andriy, Sounds like a workable plan. If 4.0.0 is still ongoing once TomEE 9 is released, I'd help there before moving onto any potential 4.1 work. I'd expect TomEE 10 work to go far into next year, so there's no immediate time pressure -- just trying to get a feel for how it might all

Re: [DISCUSS] CXF 3.5.x and beyond

Thanks David. I think the most efficient way for CXF team is to focus on 4.0.0. We have a few blockers along the way which we are working on. To put it in perspective, there are modules which are excluded from the builds at the moment, no equivalent replacement of the dependencies in Jakarta

Re: [DISCUSS] CXF 3.5.x and beyond

> On Oct 8, 2022, at 8:21 PM, Andriy Redko wrote: > > I was thinking about that as well, since Jakarta EE 10 is already out [1]. If > I am not mistaken, > we haven't discussed the future Jakarta plans yet, trying to address major > 4.0.0 migration issues. > Personally I was thinking that

Re: [DISCUSS] CXF 3.5.x and beyond

Hey David, I was thinking about that as well, since Jakarta EE 10 is already out [1]. If I am not mistaken, we haven't discussed the future Jakarta plans yet, trying to address major 4.0.0 migration issues. Personally I was thinking that having 4.1.x release dedicated to Jakarta EE 10 is

Re: [DISCUSS] CXF 3.5.x and beyond

Jumping into a random spot in this thread. My understanding of the current state of 4.0.0 is: - Targets Java 17 due to Spring deps - Targets Jakarta EE 9 / Jakarta Rest 3.0 The trick for us on the TomEE side is that Jakarta EE 9.1 requires support for Java 11. We're still using 3.5.x with

Re: [DISCUSS] CXF 3.5.x and beyond

Hey Colm, All skipped projects are listed here [1], the test cases (for now) don't have JIRAs but will be fixed at some point (hopefully - very soon), I am not sure we need separate tickets for that since we don't silence/ignore them. Thanks! [1] https://issues.apache.org/jira/browse/CXF-8724

Re: [DISCUSS] CXF 3.5.x and beyond

Hey Jim, Yes, the maven-plugins/wadl2java-plugin is blocked by [1], no Jakarta release. Thanks! [1] https://github.com/highsource/jaxb2-basics Best Regards, Andriy Redko JM> I already created a branch for the pre-removal and merged this osgi removal JM> change to the main branch . JM> For

Re: [DISCUSS] CXF 3.5.x and beyond

I already created a branch for the pre-removal and merged this osgi removal change to the main branch . For these test failures and skipped modules, I'll have a look and fill a JIRA for them after I resolve the grizzly jakarta upgrade : https://issues.apache.org/jira/browse/CXF-8716. @Andriy

Re: [DISCUSS] CXF 3.5.x and beyond

Hi, No objection from me either. Apart from OSGi, could we make sure that all the gaps are recorded in JIRA? * Test failures in cxf-rt-mp-client - https://issues.apache.org/jira/browse/CXF-8758 * Test failures in cxf-systests-transports-undertow,cxf-systests-jaxws (websocket related) -

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Jim, No objections 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 changes before the osgi and karaf removal, then > merge the this PR

Re: [DISCUSS] CXF 3.5.x and beyond

Hi all, If there is no objection, I will create a branch "osgi-pre-removal-v4.0" to record the changes before the osgi and karaf removal, then merge the this PR https://github.com/apache/cxf/pull/999 to the main branch. Thanks, Jim On Thu, Sep 22, 2022 at 9:06 PM Andrey Redko wrote: > This is

Re: [DISCUSS] CXF 3.5.x and beyond

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://github.com/apache/cxf/pull/999 >

Re: [DISCUSS] CXF 3.5.x and beyond

Thanks Jim, I will take a close look! Freeman On Wed, Sep 21, 2022 at 4:02 AM Jim Ma wrote: > Hi All, > I tried to remove the osgi and karaf from CXF with this draft PR : > https://github.com/apache/cxf/pull/999 > . > This mainly removed the osgi

Re: [DISCUSS] CXF 3.5.x and beyond

Hi All, I tried to remove the osgi and karaf from CXF with this draft PR : https://github.com/apache/cxf/pull/999 . This mainly removed the osgi code,test, examples and dependency, but for some class like SpringBus which deeply coupled with osgi:

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Jim, That is correct, I am working on https://issues.apache.org/jira/browse/CXF-8717 as part of Jetty 11 migration, the Atmosphere implementation seems to be fine. Thanks. Best Regards, Andriy Redko JM> Thanks for the update, Andiry. You already did a lot of work on third party JM>

Re: [DISCUSS] CXF 3.5.x and beyond

+1 for this way, it's much easier. Thanks! Freeman On Fri, Sep 9, 2022 at 3:55 PM Andriy Redko wrote: > Hi Jim, > > It sounds easier, requiring less efforts, I agree. > Colm, Freeman, are you on board with this approach guys? > Thanks! > > Best Regards, > Andriy Redko > > JM> Hi Andriy, >

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Jim, It sounds easier, requiring less efforts, I agree. Colm, Freeman, are you on board with this approach guys? Thanks! Best Regards, Andriy Redko JM> Hi Andriy, JM> From what I looked at last time, it seems it's difficult to decouple these JM> osgi/karaf integration code from cxf core

Re: [DISCUSS] CXF 3.5.x and beyond

Thanks for the update, Andiry. You already did a lot of work on third party jakarta support ! Just to understand the CXF Jakarta support work status, are these issues we can start without waiting for the dependency release ? https://issues.apache.org/jira/browse/CXF-8716

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Andriy, >From what I looked at last time, it seems it's difficult to decouple these osgi/karaf integration code from cxf core and create a new project to put it into a separate repository. IMO, we can create a branch before we remove these integration codes, and later we can look at this branch

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Jim, Yeah, we may need some time, I am also finalizing work on the Wiremock (https://github.com/wiremock/wiremock/pull/1942), we use it in tests extensively. One of the largest efforts is migration to Jetty 11, I have started on that already but have difficulties with WebSockets migration,

Re: [DISCUSS] CXF 3.5.x and beyond

Hey guys, Thanks a lot for bringing the clarity on possible timelines. @Jim, how do you want  to proceed with that? Do you think it is good idea to move off Apache Karaf integration  into separate repository altogether (we discussed that a few times as well)? Should we  preserve the

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Andriy, It looks like we still have to wait for the other dependency jakarta support available, like brave's new release to include this change : https://github.com/openzipkin/brave/pull/1344. Do you see any other dependencies that haven't been released yet except OSGI and Karaf ? Thanks, Jim

Re: [DISCUSS] CXF 3.5.x and beyond

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 improvement and refactor work to make it loosely coupled with core code.

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Jim, Sorry for the late reply, just back from vacation. About the OSGi part, the main problem is that the OSGi R9 spec which will support Jakarta namespace is in progress and isn't released yet(and I don't think there is a concrete release date for OSGi R9 spec in the new future). Before OSGi

Re: [DISCUSS] CXF 3.5.x and beyond

For OSGI and Karaf Jakarta native, I remembered I talked with Freeman about this topic several months ago and got to know there won't be Jakarta namespace support work in the future. I don't know if this has changed. Freeman, do you have some update on this ? On Tue, Aug 23, 2022 at 6:43 AM

Re: [DISCUSS] CXF 3.5.x and beyond

Hey Jim, I think these [1], [2], [3] (Swagger 1.x, OSGi and Karaf) are real blockers. For Swagger 1.x, we could go ahead and drop the support altogether, this is quite isolated feature. OSGi and Karaf are not, those penetrated very deep into core. What worries me, if we drop everything

Re: [DISCUSS] CXF 3.5.x and beyond

After we merged the jakarta branch to default branch main branch, do we need to create some plan to do a future 4.x release? There are a couple of to-do things under https://issues.apache.org/jira/browse/CXF-8371 umberbralla, and for some of them we can't do more things because of the jakarta

Re: [DISCUSS] CXF 3.5.x and beyond

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 into master, HUGE THANKS everyone for > tremendous effort! Please > note, it is still work in progress, the things to be done are tracked

Re: [DISCUSS] CXF 3.5.x and beyond

Hey guys, The Jakarta branch [1] just went into master, HUGE THANKS everyone for tremendous effort! Please note, it is still work in progress, the things to be done are tracked under [2], feel free to add more items or pick the existing ones. The master builds still have some tests failing,

Re: [DISCUSS] CXF 3.5.x and beyond

Thanks guys, the branch is created: https://github.com/apache/cxf/tree/3.6.x-fixes Best Regards, Andriy Redko COh> +1 from me. COh> Colm. COh> On Thu, May 26, 2022 at 2:40 AM Jim Ma wrote: >> Hi Andriy, >> A good plan. I agree with all these changes and support versions. >> Thanks, >>

Re: [DISCUSS] CXF 3.5.x and beyond

+1 from me. Colm. On Thu, May 26, 2022 at 2:40 AM Jim Ma wrote: > > Hi Andriy, > A good plan. I agree with all these changes and support versions. > > Thanks, > Jim > > On Mon, May 23, 2022 at 12:45 AM Andriy Redko wrote: > > > Hey folks, > > > > While the work on 4.x / Jakarta is slowly but

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Andriy, A good plan. I agree with all these changes and support versions. Thanks, Jim On Mon, May 23, 2022 at 12:45 AM Andriy Redko wrote: > Hey folks, > > While the work on 4.x / Jakarta is slowly but steadily moving forward, it > is > time to think about next 3.x release line. As we

Re: [DISCUSS] CXF 3.5.x and beyond

Hey folks, While the work on 4.x / Jakarta is slowly but steadily moving forward, it is time to think about next 3.x release line. As we discussed in this thread, it seems we agreed on 3.6.x to be next javax.* based release, with JDK-11 as the baseline. We have new Spring Boot 2.7.0 just

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Andriy, I took some time to look at the CXF java11 support and spring decoupling last week. Here are some thoughts and initial work: 1) Use cross compile to support java11 . We can simply change in pom.xml to 11. This will allow the maven compiler plugin to build cxf with java11. 2) We can

Re: [DISCUSS] CXF 3.5.x and beyond

Hey Jim, Yeah, it was just an example of some particular issue related to Spring usage to scan classes, multiple alternative exists, just has to be done in non-breaking way. But @Christian did the real work in that direction. Thanks! Best Regards, Andriy Redko JM> Thanks for the quick

Re: [DISCUSS] CXF 3.5.x and beyond

Thanks for the quick update , Andriy. On Sun, Jan 30, 2022 at 12:55 AM Andriy Redko wrote: > Hey Jim, > > AFAIR this particular topic has popped up several times, a few issues > exist [1] I am not sure if I understood this issue correctly : we now use spring utility class to scan the

Re: [DISCUSS] CXF 3.5.x and beyond

Hey Jim, AFAIR this particular topic has popped up several times, a few issues exist [1] and @Christian even did the POC several years ago [2] in attempt to remove some of the hard Spring dependencies (I don't know the outcomes to be fair but I suspect it turned out to be much more difficult

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 happened at the end of this year. The

Re: [DISCUSS] CXF 3.5.x and beyond

On Mon, Dec 27, 2021 at 10:49 PM Andriy Redko wrote: > Hey guys, > > A bunch of good things have happened at the end of this year. The 3.5.0 > out and we are in a good > shape to kick off Jakarta support: the Spring 6 milestones and Spring Boot > 3 snapshots are already > available. There are

Re: [DISCUSS] CXF 3.5.x and beyond

Hey guys, A bunch of good things have happened at the end of this year. The 3.5.0 out and we are in a good shape to kick off Jakarta support: the Spring 6 milestones and Spring Boot 3 snapshots are already available. There are tons of things to fix and address, I have created this draft pull

Re: [DISCUSS] CXF 3.5.x and beyond

I will check it out shortly, thanks a lot Jim! Best Regards, Andriy Redko JM> @Andriy, I finally get time to back on this task. I just sent a PR as you JM> suggested : https://github.com/apache/cxf/pull/855 JM> and labeled it with "work-in-progress". JM> If anyone has any idea to improve

Re: [DISCUSS] CXF 3.5.x and beyond

@Andriy, I finally get time to back on this task. I just sent a PR as you suggested : https://github.com/apache/cxf/pull/855 and labeled it with "work-in-progress". If anyone has any idea to improve this, feel free to comment, update or replace it with another PR. Thanks, Jim On Wed, Sep 8,

Re: [DISCUSS] CXF 3.5.x and beyond

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 do you have an idea regarding xmlschema 2.3.0 release timelines? > @Dan do you have an idea regarding neethi

Re: [DISCUSS] CXF 3.5.x and beyond

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 do you have an idea regarding xmlschema 2.3.0 release timelines? @Dan do you have an idea regarding neethi 3.2.0 release timelines? At worst, you could create a new branch for

Re: [DISCUSS] CXF 3.5.x and beyond

Thanks for more updates , Andriy. Is there a place/workspace branch, I can send a PR for this change? On Fri, Sep 3, 2021 at 9:20 PM Andriy Redko wrote: > Hey Jim, > > Thanks a lot for taking the lead on this one. Just want to chime in on a > few points. Indeed, as > per previous discussion in

Re: [DISCUSS] CXF 3.5.x and beyond

Hey Jim, Thanks a lot for taking the lead on this one. Just want to chime in on a few points. Indeed, as per previous discussion in this thread, it seems like it make sense to provide only the subset of shaded modules with Jakarta namespace. Also, it was confirmed yesterday that Spring

Re: [DISCUSS] CXF 3.5.x and beyond

Good point, Romain. We need to look at what to do to make sure all artifacts are included and transformed if this becomes a cxf module. BTW, Spring 6 GA supports jakarta ee9 will come in Q4 2022 : https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6 On

Re: [DISCUSS] CXF 3.5.x and beyond

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:39, Jim Ma a écrit : >> >>> >>> >>> On Fri, Aug 20, 2021 at 2:10 PM Romain Manni-Bucau < >>> rmannibu...@gmail.com> wrote: >>> Le

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 à 22:45, Andriy Redko a écrit : >>> Hi Romain, Sorry for

Re: [DISCUSS] CXF 3.5.x and beyond

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 à 22:45, Andriy Redko a écrit : >> >>> Hi Romain, >>> >>> Sorry for the delayed response. I have been thinking about your (and >>> Jim) suggestions

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

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 officially > release anything > to shade/overwrite javax <-> jakarta?

Re: [DISCUSS] CXF 3.5.x and beyond

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 officially release anything to shade/overwrite javax <-> jakarta? Generally, we could shade Spring or/and any other dependency but we

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Colm, Thank you, for 3.5.0, we are waiting for Apache Karaf 4.3.3 to be released so you definitely have time. I think ideally, it would be great to have 3.5.0 in September, how does it look from your perspective? Certainly +1 to phase out 3.3.x release line. Thank you. Best Regards,

Re: [DISCUSS] CXF 3.5.x and beyond

Hi, I don't have strong views either way, but it seems like the majority favour having one more release of CXF with JDK 8 support. Andriy, when do you anticipate we could release CXF 3.5.0 by? I need to release new major versions of Santuario + WSS4J first, but there is not a huge amount of work

Re: [DISCUSS] CXF 3.5.x and beyond

I'm not sure I see why you need spring to start this work. The expected is there already so spring module can still rely on javax, be made jakarta friendly using shade plugin or alike and that's it until a spring native integration is there. Worse case cxf-spring will not be usable with jakarta -

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Jim, I will try to answer your questions, other guys will definitely share more thoughts, please see mine inlined. >> What's the task for JDK-17 LTS preparation ? Do we need to support build >> 3.5.0 with JDK-17 ? Build + All tests are green. Apache Karaf 4.3.3 will support JDK17 so our

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

Hi, Thanks for sharing. IMHO, option #1 is probably the most convenient. Regards JB On 11/08/2021 14:26, 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

Re: [DISCUSS] CXF 3.5.x and beyond

I’m very strongly in favor of Option #1 at this point, with a “release note” mentioning that 3.5.x will be the last series to support Java8. I know we have plenty of services running with Java8 and have several customers that are still targeting Java8. I really think we need to keep Java8 as

Re: [DISCUSS] CXF 3.5.x and beyond

Sorry for not being very clear. No, for Jakarta 4.x branch we definitely can move to JDK11. Thanks! Freeman On Wed, Aug 11, 2021 at 11:05 AM Andrey Redko wrote: > Thanks a lot Feeman, this is basically the Option #1, or you suggest to > stay on JDK-8 for Jakarta 4.x branch as well? Thank you.

Re: [DISCUSS] CXF 3.5.x and beyond

Hi Andriy, Thanks so much for your summary! I actually think we should support JDK8 as long as possible, given the fact that CXF is widely used, and some users are not that fast to adopt new JDK versions. Also CXF has started to support JDK11(even more recent JDK versions) for a while, so any

Re: [DISCUSS] CXF 3.5.x and beyond

Le mer. 11 août 2021 à 14:27, Andriy Redko a écrit : > 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

Thanks for the summary Andriy, I like #3 Option #3: - release 3.5.0 in preparation to JDK-17 LTS, use JDK-11 as baseline - move master to 4.x to continue the work on supporting Jakarta 9.0+, with JDK-11 as the minimal required JDK version (Jetty 11, ...) + maintaining 3.4.x for JDK-8

Re: [DISCUSS] CXF 3.5.x and beyond

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 remember the discussion regarding the build time approach,

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: [DISCUSS] CXF 3.5.x and beyond

Hi Andriy, commented inline Le mer. 11 août 2021 à 04:05, Andriy Redko a écrit : > 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

[DISCUSS] CXF 3.5.x and beyond

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 pending upgrade to Apache Karaf 4.3.3 (on SNAPSHOT now) so be