I figured out where the problem was (at least for my case) when I was trying to create an integration test. (I'm still stuck with the integration test).
I have a hierarchical project/module structure. So, it is like MyProjects - Project1 - Project2 - Project3 For the test cases inside Project1, I need to manually set the context-path to "Project1/src/main/webapp". Otherwise, Testify looks into "MyProjects/src/main/webapp". For integration test, I ran into another issue that after I manually set the context-path, it still can not find the webdefault.xml file because of the same reason - it looks into the MyProjects/src/test/conf dir, not Project1/src/test/conf. Is there anywhere I can rest the conf dir? Thanks, D. On 6/9/10 9:15 AM, "Bryan Lewis" <br...@maine.rr.com> wrote: > I'm on an older version of testify, 1.0.0. Maybe that's a clue. > > > On Wed, Jun 9, 2010 at 8:26 AM, paha <ch_pa...@yahoo.com> wrote: > >> >> Doesn't work for me either. Neither PageTester nor Testify (based on it) >> seem >> to handle asset:context: properly. I have no other explanation, why the >> same >> things work in tapestry itself and don't work in PageTester >> -- >> View this message in context: >> http://old.nabble.com/Testify-unable-to-locate-the-%40IncludeStylesheet-tp288 >> 23942p28829603.html >> Sent from the Tapestry - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
