The way I got Tomcat to parse .js files is like so :-

I've got Apache forwarding all relevant requests to Tomcat, which handles
the jsp and servlet stuff.
I've got Tomcat to parse all .js files as jsp files.
I then setup Apache to only forward .js files from a certain directory to
Tomcat.  So for example all .js files in the directory
/javascripts/jsp-scripts/ get forwarded to Tomcat, while all .js files in
/javascripts/normal-scripts/ are served as normal by Apache (with no
involvement from Tomcat).

Just thought it might be useful !!

Tarwinder Dhak

-----Original Message-----
From: Marc Ponschab [mailto:ponschab@isys-software.de]
Sent: Tuesday, November 06, 2001 3:04 PM
To: Tomcat Users List
Subject: Re: Classloader TC3.3


I think making JspInterceptor configurable would be the best solution.
This give the possibility to parse also *.js files or someone can serve
jsp's named *.html and so on.

Marc


Larry Isaacs wrote:

> While trying to fix the "useJspServlet" problem, I'll
> at least make it easier to enable the JspServlet in
> a web application without having to copy jars.
>
> I'll also take a look to see if JspInterceptor can be made
> configurable for other than JSP.  If that doesn't
> prove practical, I try to come up with how it might be
> customized into a MyCssInterceptor.
>
> Cheers,
> Larry
>
> -----Original Message-----
> From: Marc Ponschab [mailto:ponschab@isys-software.de]
> Sent: Tuesday, November 06, 2001 3:09 AM
> To: Tomcat Users List
> Subject: Re: Classloader TC3.3
>
>
> Thanks for your answer,
>
> is there cuurently any possibility mapping other extensions than *.jsp
> to get the hook in JspInterceptor?
> It seems to be more effective rather than invoking the JspServlet.
>
> Marc
>
>
> Larry Isaacs wrote:
>
>
>>You aren't making a mistake, other than thinking you made a
>>mistake.  This is probably the simplest solution if you
>>want to make use of Jasper's JspServlet.
>>
>>To improve performance, Tomcat 3.3 doesn't use Jasper's
>>JspServlet.  Instead JSP's are translated (using Jasper) and
>>compiled by the JspInterceptor.  The resulting JSP servlet is
>>then served with the same overhead as a regular servlet.  A
>>side effect of this is that the JspServlet isn't visible to web
>>applications by default.
>>
>>Note that the useJspServlet="true" option for the JspInterceptor
>>currently trips on this same problem of the JspServlet not being
>>visible to webapps.  We are currently working on fixing this for
>>Tomcat 3.3.1.
>>
>>Cheers,
>>Larry
>>
>>
>>
>>>-----Original Message-----
>>>From: Marc Ponschab [mailto:ponschab@isys-software.de]
>>>Sent: Monday, November 05, 2001 10:15 AM
>>>To: tomcat-user@jakarta.apache.org
>>>Subject: Classloader TC3.3
>>>
>>>
>>>Hi,
>>>
>>>i've problems understanding the classloader hierarchy in Tomcat 3.3.
>>>In my webapps, i use for generating dynamic CSS-sheets the following
>>>entries:
>>>
>>><servlet>
>>>    <servlet-name>
>>>        css
>>>    </servlet-name>
>>>    <servlet-class>
>>>        org.apache.jasper.servlet.JspServlet
>>>    </servlet-class>
>>></servlet>
>>><servlet-mapping>
>>>    <servlet-name>
>>>        css
>>>    </servlet-name>
>>>    <url-pattern>
>>>        *.css
>>>    </url-pattern>
>>></servlet-mapping>
>>>
>>>This works fine with tomcat 3.2.x and also Tomcat 4, but tomcat 3.3
>>>requires at least the following JARs in the $TOMCAT_HOME/lib/apps
>>>directory to avoid ClassNotFound-Exceptions:
>>>jasper.jar, crimson.jar, xalan.jar, tools.jar
>>>But i think this cannot be the proper solution, so: what's my
>>>misstake?
>>>
>>>Thank you in advance, Marc
>>>



--
To unsubscribe:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands: <mailto:tomcat-user-help@jakarta.apache.org>
Troubles with the list: <mailto:tomcat-user-owner@jakarta.apache.org>


--
To unsubscribe:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands: <mailto:tomcat-user-help@jakarta.apache.org>
Troubles with the list: <mailto:tomcat-user-owner@jakarta.apache.org>