Right, the TR.props file says of the "module.packages" property:
# This is the "classpath" for Turbine. In order to locate your own # modules, you should add them to this path... This comment is unintentionally (I assume :-) deceptive. It's not really a classpath, it's really more like an "import list". Your server CLASSPATH also needs to point to the classes. <>< gary -----Original Message----- From: Eric Dobbs [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 26, 2002 9:34 AM 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 05:55 AM, Lang, Cliff wrote: > [Fri Feb 15 08:04:12 EST 2002] -- ERROR -- Turbine.handleException: > > Requested Screen not found: > Turbine looked in the following modules.packages path: > [org.myproject.main.modules, org.apache.turbine.flux.modules, > org.apache.turbine.modules] Typically this means your screens are not in this directory: tdk/webapps/myproject/main/modules/screens/ Or it means the names are not matching. For example, if you are going to this url: http://localhost:8080/myproject/servlet/myproject/template/Foo.vm Turbine will be looking for Foo.java in the above directory. If neither of those are the source of your problem, you'll have to give more details. Hope that helps. -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]>
