In short, no.  If you consider a URI:
protocol:port//path/to/resource?QueryString.  The QueryString in the Jasper
log is this same query string and doesn't have anything to do with compiling
the JSP.  Its possible to create a servlet that responds to all requests
that contain it and take a parameter of the remainder of the request.  In
the example above, the servlet's address might be path/to and take the value
of /resource as a parameter.  This is the PathInfo and, again, it doesn't
affect compiling.

        What little of the stack trace you have included is very common, but
I can't remember the answer right now.  Search the mailing list archives and
the answer should be there.

        Randy

-----Original Message-----
From: Kemp Randy-W18971 [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 14, 2001 10:27 AM
To: '[EMAIL PROTECTED]'
Subject: Is the path set correctly


When I run Tomcat 3.2 on Solaris 5.6 with Apache, and try to operate the
Tomcat examples:

http://pdsweb.ecg.csg.mot.com:8080/examples/jsp/dates/date.jsp

I get Error: 500
Location: /examples/jsp/dates/date.jsp
Internal Servlet Error:
org.apache.jasper.JasperException: Unable to compile class for JSP

or

Root cause: 
java.lang.IllegalArgumentException: Unknown argument

When I look at the Jasper logs, I see:

2001-03-14 07:22:59 - JspEngine --> /jsp/dates/date.jsp
2001-03-14 07:22:59 -        ServletPath: /jsp/dates/date.jsp
2001-03-14 07:22:59 -           PathInfo: null
2001-03-14 07:22:59 -           RealPath:
/usr2/jakarta-tomcat-3.2.1/webapps/examples/jsp/dates/date.jsp
2001-03-14 07:22:59 -         RequestURI: /examples/jsp/dates/date.jsp
2001-03-14 07:22:59 -        QueryString: null
2001-03-14 07:22:59 -     Request Params: 
2001-03-14 07:22:59 - Classpath according to the Servlet Engine is:
/usr2/jakarta-tomcat-3.2.1/webapps/examples/WEB-INF/classes

Could the Pathinfo being null and the QueryString being null indicate
incorrect path settings on Unix, thereby contributing to the problem? 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to