You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by bu...@apache.org on 2004/01/02 01:56:23 UTC

DO NOT REPLY [Bug 25859] New: - WarParser.parseWebContext() insufficient

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25859>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25859

WarParser.parseWebContext() insufficient

           Summary: WarParser.parseWebContext() insufficient
           Product: Cactus
           Version: Nightly Build
          Platform: All
        OS/Version: Windows XP
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Other
        AssignedTo: cactus-dev@jakarta.apache.org
        ReportedBy: topping@digidemic.com


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.

---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org