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
WFLY-15546 Move WildFly Preview to a native Jakarta namespace variant of the jpa subsystem module #14866
Conversation
… of the jpa subsystem module Signed-off-by: Scott Marlow <smarlow@redhat.com>
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.
Hello @scottmarlow , looking at the "Wildfly Preview - Linux - JDK 17" traces, the wildfly-jpa subsystem is still being transformed there:
[19:42:41] : [Step 2/5] [INFO] EE9: transformed wildfly-jpa-jakarta-26.0.0.Beta1-SNAPSHOT.jar
There is still something in the subsystem which is being transformed. I had similar issues when I worked on JSF, take a look at this comment to know how you can check what's pending:
ee-9/source-transform/pom.xml
Outdated
@@ -49,6 +49,7 @@ | |||
<module>ee</module> | |||
<module>ee-security</module> | |||
<module>jpa/spi</module> | |||
<module>jpa/subsystem</module> |
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.
Minor formatting issue
Signed-off-by: Scott Marlow <smarlow@redhat.com>
I do not see a comment at https://github.com/wildfly/wildfly/blob/main/ee-9/feature-pack/pom.xml#L322. Was it the following line that you uncommented?
|
Signed-off-by: Scott Marlow <smarlow@redhat.com>
Ups, yes, this code is changing very quickly, yes uncomment the |
@scottmarlow https://gist.github.com/bstansberry/5df0cbd64ae3b35c6a60964b00058f0b shows the details about why wildfly-jpa-jakarta is being transformed. |
Some of what I see:
And:
So to complete the transformation of |
@ropalka FYI. This looks like another case where the rules that get applied for source transformation don't handle things that class transformation does. I'm not asking you to do anything about this; just giving you an fyi so you have context if we ever attack this issue. @scottmarlow I suggest you fix this in the existing code by loading the BeanManager and ValidatorFactory classes and checking the beginning of the FQCN of the loaded class. If it's 'jakarta' use that in the constants, otherwise use javax. My assumption there is we want the constants to vary between jakarta and javax. :). If not what the Galleon plugin transformation is doing is wrong, and then the fix would be to break up those strings so they no longer match the transformation rule. |
…n doesn't currently cover Signed-off-by: Scott Marlow <smarlow@redhat.com>
Looks better now with your suggested changes @bstansberry!
Thanks @yersan for helping with ^! |
@scottmarlow My guess is the test failures relate to "jakarta" not being handled in https://github.com/wildfly/wildfly/blob/main/jpa/subsystem/src/main/java/org/jboss/as/jpa/classloader/TempClassLoader.java#L73 Because of that the jakarta.persistence.Entity associated with entityClass in the test != the real one because it has a different defining classloader. |
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.
Need to resolve test failures.
Thanks @bstansberry for letting me know. I see @scottmarlow already fixed it. Yes, there are sometimes some tweaks needed to make things work. |
…g. spec api) classes as not to be loaded by temp classloader. Signed-off-by: Scott Marlow <smarlow@redhat.com>
Thanks, @scottmarlow! |
https://issues.redhat.com/browse/WFLY-15546
Signed-off-by: Scott Marlow smarlow@redhat.com