So if I have something like this in my webapps web.xml:
<servlet-mapping>
<servlet-name>SSIServlet</servlet-name>
<url-pattern>/artifacts/specificpathtopagebuild/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ArtifactServlet</servlet-name>
<url-pattern>/artifacts/*</url-pattern>
</servlet-mapping>
Doesn't the first servlet-mapping take precedence? Also, the ssi jars
aren't packaged up as part of my webapp, do they need to be?
Can someone shed some/any light on this for me?
-----Original Message-----
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 17, 2006 9:45 AM
To: Tomcat Users List
Subject: RE: Tomcat 4.1.30 + SSI + CruiseControl
I _think_ I know what's going wrong now, but I could really use some
expert advise:
In the web.xml for cruisecontrol, I have the following mappings:
<servlet>
<servlet-name>ArtifactServlet</servlet-name>
<servlet-class>net.sourceforge.cruisecontrol.servlet.FileServlet</servle
t-class>
<init-param>
<param-name>rootDir</param-name>
<param-value>E:\work\artifacts</param-value>
</init-param>
</servlet>
(and later there's the mapping)
<servlet-mapping>
<servlet-name>ArtifactServlet</servlet-name>
<url-pattern>/artifacts/*</url-pattern>
</servlet-mapping>
Because the SSI config stuff is configured at the top most level and any
of the .html files I want to have SSI expanded upon are in /artifacts/*,
they are going to get handed off to the ArtifactServlet. Is there
anyway to have them do both? Maybe if I had a SSI servlet configured in
cruisecontrol's web.xml that looked at a url-pattern of
/artifacts/somepath/*.html? Does this become an ordering thing (do I
need to put it before or after the ArtifactsServlet mapping)?
-----Original Message-----
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Monday, October 16, 2006 5:51 PM
To: users@tomcat.apache.org
Subject: Tomcat 4.1.30 + SSI + CruiseControl
Hello board, I have a somewhat tricky (to me at least) question about
tomcat configuration.
We are using CruiseControl to build a strictly html site alongside our
other java products and recently, they've wanted to activate SSI.
In the past, CruiseControl (CC) has made it's artifacts directory (which
sits here E:\work\artifacts) available via:
http://server:8080/cruisecontrol/artifacts/...
I have tomcat installed in C:\jakarta-tomcat-4.1.30.
I've properly activated SSI and can see it working if this particular
project's files are copied to the examples (or cruisecontrol) webapp
directory. BUT - when I follow the artifacts link to these pages, the
SSI code is ignored (and treated as comments).
So - if the files being displayed via tomcat are NOT in the webapp
directory, the SSI stuff is ignored? Is there any way to change this?
Isn't this some sort of policy file change (which is magic to me)?
In a nutshell again:
A webapp installed here:
C:\jakarta-tomcat-4.1.30\webapps\cruisecontrol
can't expand the SSI code in files here:
E:\work\artifacts\pageBuild\latest
I can see the html files (they are displayed properly), but the SSI
stuff isn't rendered.
Any help would be huge (I've done a work around I'm not proud of)!
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
