| Re: [jakartaee-platform-dev] EE 11 + is there a Jakarta EE portable way for Application Client Containers to identify the client jar in an EAR? |
_______________________________________________We might have enough extensibility with the javatest-appclient-arquillian.xml so stay tuned for an update.On Thu, Sep 19, 2024, 5:47 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:On Thu, Sep 19, 2024, 4:20 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:Quick summary is that I am working on updating the EE 11 Platform TCK (Persistence) tests to be able to deploy correctly (it is a lot of work that we want to complete quickly). In earlier EE releases we had a TCK Porting kit way for implementations to determine vendor system properties to pass in their app client container (e.g. by examining the deployment archive [1]). I do not see anything in the EE 10 Platform Spec about a portable way for identifying the appclient
Edit: please replace "container" with "jar".container in an EAR but maybe that is assumed to be the application archive(s) that contain the application-client.xml file (please point to where that is specified as a requirement if so in the EE 11 Platform specification).
So please let me know the portable way to update the JPA tests that run via Application Client Containers that are packaged as EARs such that EE implementations will automatically know which contained jars are to be deployed by the App Client Container. Perhaps there isn't a portable way and vendors will need to do something special with their javatest-appclient-arquillian.xml implementation.
Scott
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev