Details
Description
It is currently difficult to ensure all containers' are coded properly such that classpath entries indeed exist when they start. Troubleshooting is manual, as we have to dig through cargo.log looking to see if it work.
Please create a Samples TestCase that can do this.
One approach could be to make a new samples war called classpath-war. This war's index.jsp would return successfully if it can load the class identified by the system property class.to.search.for
ex. Class.forName(System.getProperty("class.to.search.for"))
in the samples pom, we could setup this property to be something known, but not normally a part of a java container (ex. derby's driver).
In the unit test, it could configure a classpath entry and then pass the property class.to.search.for to the container before running the test.