Hi Bernd

If you take a look at web.xml you'll find the following interesting entries:

  <servlet-mapping>
        <servlet-name>Spool</servlet-name>
        <url-pattern>/docroot/*</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
        <servlet-name>Spool</servlet-name>
        <url-pattern>/admindocroot/*</url-pattern>
    </servlet-mapping>

AFAIK the spool servlet just hands out the static contents ie. no jsp parsing what so ever (as you experienced)...

The way I usually handle jsp not belonging to templates is just creating a directory inside the web application dir and putting them there.

Maybe that's also a solution for you?

Cheers, Thomas



On 30.08.2006, at 07:34, Bernd Brenner wrote:

Good Morning :-)

I want to include a simple jsp page (not a template) into my magnolia project.

I tried to put an "example.jsp" into the "/docroot" folder and into the "/templates/jsp" folder. When I call the pages in the browser, only the jsp located in "/templates/jsp" will be executed:

http://localhost:8080/magnoliaAuthor/templates/jsp/example.jsp -> java code executed

http://localhost:8080/magnoliaAuthor/docroot/example.jsp -> java code not executed (just shows blanc jsp code in browser)

Is there something like a different configuration for the two folders?

My question: Is it possible to configure the "docroot" folder to execute jsp pages? I want to put there a couple of jsp pages that have nothing to do with magnolia. It would not be nice to put them to the templates folder - they just are not templates.

As far as I know it is tomcat standard that jsp pages will always be executed whereever they are located (except for the WEB-INF folder).

Thanks in advance,
Bernd

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to