McClelland, Mark wrote:
> I was able to get Jetspeed to work on WebLogic 6.1 (beta), but only by
> moving /WEB-INF/templates to /templates, changing config files to point
> to the relocated templates directory, and doing a global replace of
> "/WEB-INF/templates" to "/templates" in the templates directory -- to
> fix all of the full-path taglib headers. It appears that WebLogic does
> not allow page-forwards into the WEB-INF directory, where Tomcat does.
>
> Have other people run into the same problem? Is there a setting in
> WebLogic to allow page-forwards into the WEB-INF directory? If not, the
> Jetspeed development team may want to consider changing the default
> configuration, pulling the templates directory out of WEB-INF. I don't
> see any notable security risk in being able to browse templates
> directly... maybe I'm overlooking something?
>
> I can post the details of my WebLogic build if anyone is interested.
>
Thanks for this information, moving the templates directory one level
up will probably happen in Jetspeed 1.3a2 if we can find a good portable way
to avoid people browsing them (in theory webapp container security can
handle this if correctly implemented by all the containers...)
On the other hand, if you use Velocity as the default layout
engine, ie set in TR.p
services.TemplateService.default.extension=vm
instead of jsp, Weblogic should accept the templates in WEB-INF/templates
since Velocity does not dispatch requests as JSP does, only reads the
template files.
I'd really appreciate if someone could confirm that this indeed works.
--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
