The extra path-info will confuse things, unless you include a <base href="..."> tag in your <head> element.
If you use the Shell component, this is done for you. -- [EMAIL PROTECTED] http://tapestry.sf.net > Today I encountered the following problem. From my application's home page > I go to the second page using a Page component. The second page is found, > but the rendering is wrong, because the images and css that are fix in the > html-code of the second page are lost. The Url of the css on the first > page is: 'http://webApplicationPath/css/cssName.css'. On the second page > it is 'http://webApplicationPath/page/nameOfTheSecondPage/css/cssName.css' > and the style sheet is not found. It should be the same css on both pages. > > Is this a bug in 2.2-alpha2, I haven't had that problem in alpha1 ? With > alpha1 my URL still uses context=... service=page ... > > Best regards, > > Christian > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
