> But I am not sure how to tie this in with the screens,
> do I have 3
> subclasses from VelocitySecureScreen in subdirectories that match the
> pattern on the template subdirectories?
com.yourapp.app.modules.screens.{directory_structure_under_screens}.Template
Name.class
or if you want all screens in that directory to use the same screen class:
com.yourapp.app.modules.screens.{directory_structure_under_screens}.Default.
class
> Is this the best
> approach? Will it
> carry over to Turbine 3?
>From what I know, Turbine 3 will support the classic turbine layout,
navigation and screen methodology as an option. However, I think the push
will be to use the valve architecture T3 implements to provide for things
like view control (templates), template security, etc.
I personally have use a single screen class for my entire application. The
isAuthorized() method checks a custom xml file (using the template's name)
via a session tool/service combination to figure out whether or not the
template is secure and if it is secure, I use the session tool to validate
the current users ACL against the requirements for that template. This
allows quite a it more flexibility then having to hard code security into
individual screen classes.
If you are relying heavily on code in your screen classes, I would highly
recommend moving that logic into pull tools. I say this because (someone
correct me if I'm wrong) that appears to be the T3 way of doing things as
opposed to screen classes.
Scott
> -----Original Message-----
> From: David Wynter [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 10, 2002 4:14 AM
> To: Turbine-User
> Subject: How to approach 3 roles with separate screens?
>
>
> I have been through the archives to see how to best approach
> my requirement.
> I find I am still missing something.
>
> I currently have a single role with one permission and use a
> pull tool and
> just one subclass of VelocitySecureScreen for all the screens
> used by that
> role. I need to add 2 more roles (all need security) each
> with a single
> permission each with unique screens (there are no screens
> which are shared
> by the roles).
>
> I found the mail in the archive
> http://marc.theaimsgroup.com/?l=turbine-user&m=101043436816718&w=2
> This suggests using subdirectories for weak and secure
> screens. I assume I
> can use the same approach and have 3 template sub-directries,
> one for each
> role. But I am not sure how to tie this in with the screens,
> do I have 3
> subclasses from VelocitySecureScreen in subdirectories that match the
> pattern on the template subdirectories? Is this the best
> approach? Will it
> carry over to Turbine 3?
>
> thanks
>
> David
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
