I believe turbine uses jakarta-commons configuration, so you might want to
escape your commas otherwise commas will represent list delimeters.
sv
On Wed, 11 Feb 2004, Gerry Duprey wrote:
> Howdy Jeff,
>
> That was it - thanks!
>
> Do the use of comma instead of / apply to the TurbineResources.properties file
> too?
>
> I'd like to move my login screen to a subdir as well as my Login action.
> Could I use commas both for the template and the Login action/class as defined
> in the properties file?
>
> Thanks again!
>
> Gerry
>
>
> Jeff Painter wrote:
> > How are you accessing these screens in the subdirectories?
> >
> > from your example I would call as
> >
> > <a href="$link.setPage("email,main.vm")">main</a>
> > ^^ - that is a comma
> >
> > or similarly on the backend
> >
> > data.setScreenTemplate( "email,main.vm ");
> >
> > make sure you aren't trying to call as email/main.vm as this violates
> > the way turbine builds links.. slashes indicate parameters are being
> > passed - commas are used for building your directory tree
> >
> > hth,
> > Jeffery Painter
> >
> >
> > On Wed, 11 Feb 2004, Gerry Duprey wrote:
> >
> >
> >>Howdy,
> >>
> >>As our application gets a bit bigger, we are starting to use a number of
> >>subdirectories in the modules/screens directory. However, whenever I put a
> >>screen in a subdirectory, an attempt to access that screen throughs an
> >>exception in the PageLoader class.
> >>
> >>For example, if I have a screen called
> >>
> >>/usr/local/templates/modules/screens/email/main.vm
> >>
> >>I'll get an exception like this
> >>
> >>Requested Page not found: Default
> >>Turbine looked in the following modules.packages path:
> >>[SOpen.common.turbine.modules, org.apache.turbine.modules]
> >>
> >>at org.apache.turbine.modules.PageLoader.getInstance(PageLoader.java:207)
> >>at org.apache.turbine.modules.PageLoader.exec(PageLoader.java:136)
> >>at org.apache.turbine.Turbine.doGet(Turbine.java:796)
> >>at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> >> ... etc
> >>
> >>If I move "main.vm" up a level (into .../modules/screens), things
> >>work fine. Right now, there is no code behind the main.vm template
> >>(everything is being accessed via pull services).
> >>
> >>It's almost seems like I have to create a Default page loader if I want to use
> >>subdirectories? But that doesn't seem right. As I understand it, Turbine
> >>will look in SOpen.common.turbine.modules.screens.email.main, then look for
> >>the default, etc, etc and eventually drop back to the normal default page
> >>(VelocityPage).
> >>
> >>Can someone shed any light on this? If I keep all the heirarchies "flat",
> >>everything works (but things get messy). I'm hoping I'm just missing
> >>something really obvious :-)
> >>
> >>Gerry
> >>
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
