JettyRunner's contextpath in Tap5's AbstractIntegrationTestSuite

[Jim Tomlinson <ji...@u.washington.edu>]

Any thought to allowing the test auther to set the desired webapp 
context-path in AbstractIntegrationTestSuite's JettyRunner member? We're 
having a bit of trouble because we can't (it's currently hardcoded to 
"/"), as our authorization scheme looks at the context path (we'll have 
multiple applications with different context paths, with access 
controlled by the same auth code; context-path is part of our 
authorization determination). Since AbstractIntegrationTestSuite.setup() 
(where the JettyRunner is constructed with the hard-coded context-path) 
is private, we can't just extend AbstractIntegrationTestSuite. We'll 
probably have to just use our own, modified copy of 
AbstractIntegrationTestSuite for now, but making setup() protected, or 
allowing the test author the ability to set/pass-in-on-constructor the 
context-path would be better, IMHO. I can post a patch, if need be. Thanks.

- Jim

-- 
------------- UW Office of Information Management -------------
Jim Tomlinson                          Office:   (206) 685-6449
Sr Applications System Engineer        University of Washington
-------------------- Rome Development Team -------------------- 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org