wildfly 26.x support lifecycle and wildfly 27 jakarta namespace

[jvi...@gmail.com]

I'm wondering how long will wildfly 26.x still be supported and will at least get new versions with security fixes ?

Just tried to investigate what it would take us to migrate to wildfly 27 and the jakarta namespace change is a frustrating neck breaker I have never exeprienced before. I know this not really something the wildfly team is responsible for...

The namespace change on own written code is not the problem, but if you have a fairly big application also relying on 3rd party libraries and frameworks using the javax namespace you are basically f...ed. You either have to pray for every maintainer of the libs you are using to do the transition, patch every library yourself or completely rewrite parts of the application which is a massive amount of work
For example frameworks like struts2 do not have jakarta ee compatible version yet.

We are using wildfly for our app since jboss 5 and although there were sometimes some challenges to upgrade stuff (mostly if it relied an stuff outside the java ee standard) it was always possible to migrate pretty easy.

I hope this is not the nail in the coffin for the java ee/jakarta ee community, i think the stability, compatibility and longevity of the underlying platform was always a big big plus, that I feel now got taken away from us...I like to stay because i love(d) the java/java ee ecosystem but others might just move on to some more "buzzwordy" language if they have to rewrite anyways...

How are other community members dealing with that challenge ?

[Emmanuel Hugonnet]

Hello,
You could try what Brian described here [1] as a temporary workaround until your libs are migrated.
I don't know about struts 2 project structure but there are quite a few ways to migrate easily to JakartaEE 10 and even keep on providing
artefacts for both JavaEE and JakartaEE (like we did for Apache Artemis for example).
Regards,
Emmanuel

[1]: https://groups.google.com/g/wildfly/c/hVbijKO7do8

> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/wildfly/ba1cc767-5bc7-471f-a079-77c7b8e90940n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/ba1cc767-5bc7-471f-a079-77c7b8e90940n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[jvi...@gmail.com]

Hi thanks,

it helped a bit although it was only enough to run parts of our deployments for now.

Now also came across some other resources that help to get in the right direction:

https://windup.github.io/

https://github.com/eclipse/transformer

Still a long way to go