Details
Major Description
Hi, thanks for a great tool!
WarParser.parseWebContext() is not sufficient for the needs of all
deployments. We are using the jboss3x container configuration with a jboss-
web.xml file defining the context root at "/". But this makes the application
untestable, since the only option for WarParser.parseWebContext() is to use
the root name of the war file for the context name to be looked up.
Because of the age of the application, it is impractical to change the the app
under testing to a context other than root. Even so, doing so would violate
the tenet of not changing the app for testing.
Given that multiple containers can exist with different methods of determining
the web context, the loop over containers in CactusTask.execute should clone
deployableFile, then give the container a shot at renaming the context. This
seems to be the most sane way of changing things. Alternately, a
configuration element for the ant target could be created, but that seems less
desirable without built-in intelligence at the container level.