You only need one java class per top level directory, so if you have
your templates stored in src/templates
screens/Index.vm
screens/admin/Index.vm
One screen package module will work <package.prefix>.screens.Default
This class does not have to do much, but it is a reasonable place to
implement a security policy, if desired.
john mcnally
Will Glass-Husain wrote:
>
> Hi,
>
> As a new Turbine user, I read Jon Steven's article on the Pull MVC model.
> Makes a lot of sense to me (this is how I've been working with Velocity for
> the last 6 months).
>
> http://jakarta.apache.org/turbine/turbine-2/pullmodel.html
>
> But Turbine's default implementation appears to be a Push model, where every
> Velocity page requires a Java class. However, I'd like to enable my
> template designers to add new navigational links without requiring the
> programmer to write a new Java class.
>
> Is there a built-in structure that enables this, or do I implement my own
> additional framework? I searched the docs, but didn't see an obvious
> recommended solution. What's the "Best Practice" here?
>
> Thanks,
>
> WILL
> _______________________________________
> Forio Business Simulations
> Will Glass-Husain
> (415) 440-7500 phone
> (415) 235-4293 mobile
>
> [EMAIL PROTECTED]
> www.forio.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
