That would be the simple answer, but I would like to keep the .js extension
keep to the standard for javascript files.
There must be a way for tomcat to compile files that don't end in a .jsp
extension.
Thanks.
Tarwinder Dhak
-----Original Message-----
From: Burkard Endres [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 03, 2001 10:55 AM
To: [EMAIL PROTECTED]
Subject: AW: Tomcat 321 won't parse other than .jsp files
simply rename your .js file to .jsp?
-----Ursprüngliche Nachricht-----
Von: Tarwinder Dhak [mailto:[EMAIL PROTECTED]]
Bereitgestellt: Montag, 3. September 2001 11:33
Bereitgestellt in: tomcat-user
Unterhaltung: Tomcat 321 won't parse other than .jsp files
Betreff: Tomcat 321 won't parse other than .jsp files
Hi,
I'm writing a web application that uses some javascript (in an external
file
menu.js) that displays some dynamic menus. Each of these menu options
then
goes to a specific URL.
What I want to do is insert some JSP elements into the menu.js file so
that
when the client requests the file, all URLs go through the
request.encodeURL() method to append any session data to the URLs. The
problem is that Tomcat only seems to want to compile files with a .jsp
extension.
I've got Tomcat running through APJ13 with apache (mod_jk.so), and have
used
the jkmount directive in the mod_jk config file to forward all *.js
requests
to Tomcat, but tomcat won't compile it. It just sends me the raw text
instead.
Basically, what I would like to know is how to get tomcat to compile
files
that have JSP elements in them, but do not have the .jsp extension.
Thanks in advance for your help.
Regards
Tarwinder Dhak
[EMAIL PROTECTED]
Transact Group
Development
Legal Disclaimer: Internet email communications are not secure and
therefore the NetInvest Group does not accept legal responsibility for
the contents of this message. Any views or opinions presented are solely
those of the author and do not necessarily represent those of the
NetInvest Group unless otherwise specifically stated.
winmail.dat
