I have manged, barring some challenges, to get the TCK passing with Tomcat 11. However, that required various configuration steps that seem rather hacky. I suspect I am not quite doing things the right way. I'd like to understand the right way to do these things so I can submit a PR to add the necessary configuration to the TCK to run with Tomcat.
I added to tomcat-11 profile to tck/pom.xml. This appears to the the correct way to do things so I am not concerned about these.
The configuration changes I am concerned about are:
arquillian.xml. Placed in tck/common/src/main/resources, sets the user name and password required to deploy the test WARs to Tomcat. Also sets a number of system properties required by the tests.
tomcat-users.xml. Placed in tck/common/src/main/resources, used to configure the user required to deploy the test WARs to Tomcat. Also creates a user required by some tests.
ProviderConfiguration.xml. It was necessary to modify this file as the application context identifier needed to be changed to match the naming used by Tomcat.
Pointers to better/correct ways for each of the above welcome.
I have manged, barring some challenges, to get the TCK passing with Tomcat 11. However, that required various configuration steps that seem rather hacky. I suspect I am not quite doing things the right way. I'd like to understand the right way to do these things so I can submit a PR to add the necessary configuration to the TCK to run with Tomcat.
I added to
tomcat-11profile totck/pom.xml. This appears to the the correct way to do things so I am not concerned about these.The configuration changes I am concerned about are:
arquillian.xml. Placed intck/common/src/main/resources, sets the user name and password required to deploy the test WARs to Tomcat. Also sets a number of system properties required by the tests.tomcat-users.xml. Placed intck/common/src/main/resources, used to configure the user required to deploy the test WARs to Tomcat. Also creates a user required by some tests.ProviderConfiguration.xml. It was necessary to modify this file as the application context identifier needed to be changed to match the naming used by Tomcat.Pointers to better/correct ways for each of the above welcome.