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).
I had tried digging into ScreenLoader, but gathered no information,
because it was a null call to ScreenLoader - then it would fail over as
it is supposed to, to the VelocityErrorTemplate.
Thanks for the help, Cliff
-----Original Message-----
From: Eric Dobbs [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 1:16 PM
To: Turbine Users List
Subject: Re: Repost: -- no responses yet: Turbine screens (*.java) files
not being processed Turbine.handleException - "Requested Screen not
found"
On Tuesday, February 26, 2002, at 03:43 PM, Lang, Cliff wrote:
> Not exactly, put I didn't think it mattered for PullTools as long as
> your reference is correct in the TR.props file.
I think you are correct about PullTools.
The problems you are describing are pretty
weird, and pretty uncommon.
I think the most likely culprits are typos in
the config file, or in the file names, or files
not being located in the correct directories.
If you are *completely* convinced you have all
those things correct then I suggest you start
hacking the ScreenLoader and logging the files
it's trying to find, as a place to continue
with your debugging efforts.
Sorry I can't help more.
-Eric
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
