Missing -jakarta edition for versions newer than 4.0.20

#38754

Why are jakarta versions of downloads for 4.0.20+ missing? Aren’t the jakarta versions built using the same CI / CD workflows?
We are paying customers and need the fixes in 4.0.20fx2 (and later) and we have recently converted all our Java EE applications to run on Jakarta EE, so we really need the Jakarta version!

Thanks in advance,
Avonova Norway.

#38758

Hi! Unfortunately jakarta version build is not fully automated and still requires a manual merge and a repeating or some human-involved QA steps. Synchronizing the Jakarta version is on our short-term roadmap, but before that we were going to release v4.0.20fx3.

If it is critical for you, we’ll publish v4.0.20fx2-jakarta early next week

#38759

Hi!

Early next week sounds lovely 😉 !

Best regards,
Avonova Norway

#38951

Hi!

Due to some important bug fixes provided in fx3 (which affects us), we have resorted to use the v4.0.20fx3-jakarta-SNAPSHOT release. Will the final version of 4.0.20fx3 be available anytime soon?

Thanks in advance,
Avonova Norway

#41302

Hello!

This is a problem for us as well. Could you please consider creating a jakarta package for the 4.1.0 as well?

Thanks,
Palle

#41825

And for 4.1.1….

You say “Get the latest PD4ML v4 build from the software download area, including Jakarta builds.” in your release-download page. But there is non ..jakarta.jar

In the standard jar there are javax and jakarta packages. But using it in a jakarta server (wildfly 32) the javax – Classes are tried to be loaded. Is there a possibilty to set an environment flag, so your lib recognizes that it ist running in an jakarta?
Oder other solution?

Best regards
Tom Herzberger

#41929

Hello Tom,

Since v4.0.21 there are no separate -jakarta and javax builds any more. The release notes for that version say the separation between the jakarta and javax versions ends, and the library works with both. So the standard jar is the right one for WildFly 32, and you don't need a separate "-jakarta" download. This also covers the 4.0.20fx3-jakarta and 4.1.0 requests earlier in this thread. The wording on the download page is outdated, and I'll pass that on.

You don't need an environment flag either, and I don't see one in the code. PD4ML tries the javax and the jakarta servlet resource providers one after the other. A provider whose servlet API isn't on the classpath is skipped. On WildFly 32 only the jakarta classes exist, so the javax ones can't load there and are simply ignored. When you pass the request and response, use the Jakarta objects:

PD4ML pd4ml = new PD4ML(); // jakarta.servlet.http.HttpServletRequest / HttpServletResponse are accepted pd4ml.useHttpRequest(request, response);

If you see an actual error or a failing conversion, and not just a javax class name in a log or trace, please send me:
– the exact PD4ML version (4.1.1?),
– the full stack trace or log output,
– how you call PD4ML (the servlet, the JSP taglib, or standalone code).

That will show which class is really failing.

Best regards,
PD4ML Support

[Author]

Posts