On Friday, March 1, 2002, at 06:13 AM, Lang, Cliff wrote:
> I found the issue -
> A call in the Default.vm layout template to: $page.setStyleSheet(). The
> reference was incorrect. (Template creator used full URL-relative path,
> instead of the shorter application relative path:
> $page.setStyleSheet("/myapp/servlet/myapp/style.css") vs.
> $page.setStyleSheet("/myapp/style.css")).
>
> This action of blowing up with "Class not found" seems rather severe
> when a class wasn't missing. Nothing was noted in the velocity.log upon
> template generation, and the templates were being created properly
> generated (minus the style sheet).
Now it makes sense.
The style sheet tag in the page causes the browser to
initiate a separate request to the server. That
requested URL was like this:
http://<server>/myapp/servlet/myapp/style.css
So Turbine was being incorrectly invoked to process
the style sheet. The ParameterParser could not find
a value for 'screen' nor for 'template', which is
probably why you were seeing nulls when debugging
ScreenLoader.
I would expect your templates to be generated
correctly. The problems are happening in a separate
request to the server.
I'm not sure what else Turbine could do to report a
different error. From the servlet's point of view it
was just handling a malformed URL and reporting the
problems as it would normally. I agree that the error
doesn't help you locate the problem very well, but I
don't know what should be done differently. Those
errors are appropriate in most circumstances.
-Eric
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
