Issues Javax EE to Jakarta EE using java-saml

[jacqueskpoty]

It'is impossible to use java-saml with java 17 at this point. Is there any work around? is the community working on releasing a new version with java 17?

[haavar]

What's the issue with running under java 17?

[jacqueskpoty]

Since java 17 many of the classes in javax package are moved to jakarta.
This is causing a big issue.
I recently upgraded my project to Spring Boot 3.2.2 so im forced to use java 17
This upgrade makes java-saml unusable.

[mauromol]

Java 17 itself has nothing to do with the change from Java EE to Jakarta EE.

[jacqueskpoty]

Is there anything being done to support the change from Java EE to Jakarta EE for java-saml?

[mauromol]

There's PR #395 open.

[jacqueskpoty]

@mauromol Thanks. I checked and the PR has been for a year. Hopefully it will be merged soon.

[william00179]

This package can be easily transformed with https://github.com/eclipse/transformer and then used.

I am using this for this package and many others that don't support the jakarta migration.

[paulrutter]

#349 (comment) is another workaround.

[haavar]

How are you guys using the servlet API with the SAML library? Can you not just pass in the parameters, instead of wrapping the request? I've been using jarkarta for a while now, and that did not affect how I used saml core.

[paulrutter]

Java-saml uses javax classes, java-saml-core does not. See https://github.com/SAML-Toolkits/java-saml#the-httprequest

[AbhishekGupta1996]

I’m currently working with the java-saml library and noticed that the Auth class expects parameters using javax.* packages. However, I’ve migrated my project to Java 17 and Jakarta EE, which uses jakarta.* packages, and I’m running into compatibility issues.

Has there been any update or support added for Jakarta EE in the java-saml dependency? If not, does anyone have a workaround or suggestion for using the Auth class with Jakarta EE?

Any guidance would be greatly appreciated.

Thanks!

[paulrutter]

I’m currently working with the java-saml library and noticed that the Auth class expects parameters using javax.* packages. However, I’ve migrated my project to Java 17 and Jakarta EE, which uses jakarta.* packages, and I’m running into compatibility issues.

Has there been any update or support added for Jakarta EE in the java-saml dependency? If not, does anyone have a workaround or suggestion for using the Auth class with Jakarta EE?

Any guidance would be greatly appreciated.

Thanks!

See #349 (comment)

[AbhishekGupta1996]

I’m currently working with the java-saml library and noticed that the Auth class expects parameters using javax.* packages. However, I’ve migrated my project to Java 17 and Jakarta EE, which uses jakarta.* packages, and I’m running into compatibility issues.
Has there been any update or support added for Jakarta EE in the java-saml dependency? If not, does anyone have a workaround or suggestion for using the Auth class with Jakarta EE?
Any guidance would be greatly appreciated.
Thanks!

See #349 (comment)

Thanks @paulrutter , that worked perfectly for me!
Quick question: is it safe to use wrapper conversions to javax.* in a real-time/production project?

[paulrutter]

I don't think it makes any difference. With the wrapper approach you do have both javax and jakarta apis in your classpath, which you wouldn't have with transformations.