[wildfly-dev] Re: WFLY-19020: behavior change in persistence unit handling of application client

On 5/17/24 10:27 AM, Scott Marlow wrote: Pasting from the referencing rules for easy reference: " 8.3.3. Application Client Container Class Loading Requirements Components in the application client container must have access to the following classes and resources. * The content of the application client jar file. * The transitive closure of any libraries referenced by the above jar file (as specified in Library Support <https://jakarta.ee/specifications/platform/10/jakarta-platform-spec-10.0#...>). * The transitive closure of any libraries specified by or referenced by the containing ear file (as specified in Library Support <https://jakarta.ee/specifications/platform/10/jakarta-platform-spec-10.0#...>). * The Jakarta EE API classes specified in Jakarta EE Technologies <https://jakarta.ee/specifications/platform/10/jakarta-platform-spec-10.0#... for the application client container. * All required Java SE API classes <https://jakarta.ee/specifications/platform/10/jakarta-platform-spec-10.0#...;. Components in the application client container may have access to the following classes and resources. Portable applications must not depend on having or not having access to these classes or resources. * The Jakarta EE API classes specified in Jakarta EE Technologies <https://jakarta.ee/specifications/platform/10/jakarta-platform-spec-10.0#... for the containers other than the application client container. * Any installed libraries available in the application server. * Other classes or resources contained in the application package, and specified by an explicit use of an extension not defined by this specification. * Other classes and resources that are part of the implementation of the application server. Components in the application client container must not have access to the following classes and resources, unless such classes or resources are covered by one of the rules above. * Other classes or resources in the application package. For example, the application client should not have access to the classes in other application client jar files in the same ear file, nor should it have access to the classes in web applications or Jakarta Enterprise Beans jar files in the same ear file. " The attached https://issues.redhat.com/secure/attachment/13134094/KuchenZutatInheritan... archive contains the KuchenZutatInheritanceClient.jar file that has MANIFEST.MF with: class-Path: KuchenZutatInheritanceEJB.jar My read is that the appclient container should have access to the EJB persistence unit since the EJB is on the appclient deployment classpath.  Still, I think an interesting experiment would be to try removing the KuchenZutatInheritanceEJB.jar from the appclient classpath to see if the persistence unit still deploys (if it does, I think that is a bug worth creating a new WFLY for. Scott