to solve the problem of templates... <template:insert page="/jsp/liteHeader.jsp" flush="true"> </template:insert>
using page will put the context path in for you... then you have the problem with images/css/etc. <link rel="stylesheet" href="<html:rewrite page="/style/local.css" />" charset="ISO-8859-1" type="text/css"> works well for us. andrew > -----Original Message----- > From: Cedric Dumoulin [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 01, 2002 10:08 AM > To: Struts Users Mailing List > Subject: Re: Relative URI usage in <struts-template:template tags... > > > > Hi Alex, > > Personally I use absolute paths to avoid such conflict : > <template:put name="content" > content="<%=request.getContextPath()%>/cart/cartContent.jsp" /> > > Behavior that you quote is more natural, but require complex > computation to > implement. Maybe one day. > > Cedric > > > Alex Paransky wrote: > > > I have the following structure for my web site: > > > > <common> > > template.jsp > > > > <cart> > > cart.jsp > > cartContent.jsp > > > > When I use the template:insert tag from cart.jsp, the content is being > > included relative to the location of template.jsp which is in > common, and > > not cart.jsp which is in cart. I have to specify > "../cart/cartContent" in > > my put for it to work correctly. > > > > Here is how cart.jsp looks like today: > > > > <template:insert template="../common/template.jsp"> > > <template:put name="content" content="../cart/cartContent.jsp" /> > > </template:insert> > > > > Would it not be more natural, if all the included content was > relative to > > location of "cart.jsp" and not to the template? So that one could write > > cart.jsp in the following way: > > > > <template:insert template="../common/template.jsp"> > > <template:put name="content" content="cartContent.jsp" /> > > </template:insert> > > > > Is there a way of making this work in the above described fashion? > > > > -AP_ > > www: http://www.alexparansky.com > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
