-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate Woodstox 7.0.0 #25003
Integrate Woodstox 7.0.0 #25003
Conversation
Needs to be investigated what's really failing here. |
It fails because Metro is proteted against major version updates:
@lukasj what shall we do to update metro? Widen the protection rules or just update Metro to Woodstox 7.0.0 (the major version change is due to JDK 8 support) |
@arjantijms give me some final version of Grizzly which has fixed eclipse-ee4j/grizzly#2205 so I can actually build metro with the latest jakarta APIs |
Can you try with 4.1.0-M1? If that works we can release a final. |
@lukasj note that ideally the 7.0.0 upgrade of Woodstox would also be allowed for the Jakarta EE 10 version of Metro. |
@arjantijms try metro 4.0.4 from staging |
@@ -88,7 +88,7 @@ | |||
<!-- Jakarta SOAP (with Attachments) | |||
<jakarta.xml.soap-api.version>3.0.0-RC2</jakarta.xml.soap-api.version> | |||
--> | |||
<webservices.version>4.0.3</webservices.version> | |||
<webservices.version>4.0.4</webservices.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm, looking at other deps, it will probably fail again unless EL-API gets updated to 6.0.0 and Servlet-API to 6.1.0; XML-WS related APIs should be updated to their latest versions too, but should not cause any troubles if not given their updates are fully backward compatible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can't update those in GF 7 to those versions, since they are Jakarta EE 11 dependencies.
GlassFish 8 is for Jakarta EE 11, GlassFish 7 is for Jakarta EE 10.
What we really need is a Metro / WebServices with Jakarta EE 10 dependencies (so no Expression Language 6 and no Servlet 6.1), but with WoodStox 7.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lukasj Can you do a Metro / Webservices 4.0.4 with only WoodStox updated to 7 (or, even better, just widen the protection in OSGi to include 6 and 7). Then do a Metro / Webservices 4.1.x for Jakarta EE 11?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. Try 4.0.4 again. It should be ok for use in EE 10 as well as 11 now. Given EE 10 requires SE 11, I see no point in keeping woodstox 6.x allowed.
anyway XML-WS related APIs should be updated to their latest versions note remains valid; <jakarta.xml.soap-api.version>3.0.0-RC2</jakarta.xml.soap-api.version>
is definitely wrong even for EE 10 final
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 3.0.0-RC2 only seems to occur in a comment:
<!-- Jakarta SOAP (with Attachments)
<jakarta.xml.soap-api.version>3.0.0-RC2</jakarta.xml.soap-api.version>
-->
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is in server.log of the clustered instance. I have no idea why the test passed locally. Some cached dependency on CI from staging repo ?
Caused by: java.lang.ClassNotFoundException: jakarta.servlet.ServletContainerInitializer not found by org.glassfish.metro.webservices-osgi [299]
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591)
at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1976)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
... 96 more
]]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
org.glassfish.* is being cached on the CI indeed. If Metro uses that and Lukas re-staged 4.0.4, that might be the issue.
There is a job to clear the cache.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lukasj can we release metro / webservices 4.0.4 to Maven Central?
With WoodStox 7.0.0 and Metro / WebServices 4.0.4 and jakarta.xml.ws-api 4.0.2:
Seems we still have some way to go. @dmatej any idea? |
|
And this is in server.log:
|
Aha, and yet one ... bit weird it goes after the previous one. So it seems the problem is that GlassFish 7 depends on older jakarta annotation 2.1.1.:
|
Rebased to master and removed the revert - and voila! Magic happened, both admin-tests and application-tests pased locally with JDK21 and JDK11. |
That's not a problem. Annotations 2.1 is the right version for EE 10. Annotations 3.0 is for EE 11, which GlassFish 7 cannot support (Annotations removed @ManagedBean, which is required in EE 10). |
The issue with Annotations seems resolved after the rebase (yasson?). Yeah, maybe the cache cleanup could help ... it was executed in December for the last time ... lets go for it now ... |
Changes: https://github.com/FasterXML/woodstox/blob/master/release-notes/VERSION