Thanks for the reply. That is indeed what I need to do. I had been having trouble with Default.java & just discovered why.... I have my source divided up into multiple folders like the following to allow for a little easier separation of the different pieces of the site:
Org.co.web | |----modules | |----actions | |----screens | |----admin | |----actions | |----screens | |----staff | |----actions | |----screens However, apparently Turbine only looks for Default.java files in the "modules" directory. I tried puting Default.java in staff.screens.staff, staff.screens, and staff subdirectories but none worked. When I put Default.java in modules.screens.staff, Things worked as expected. So, problem solved (I'll just put the default.java files in subdirectories of the modules dir), but shouldn't the staff subdirectories work as well? Them not doing so kind of screws up my attempt at fully partitioning the different applications. -d -----Original Message----- From: Gedin Frederic [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2003 12:33 PM To: Turbine Users List Subject: Re: Suggestions for secure pages without screen classes? Gaasch, Derek wrote: > > >Hello, I'm trying to determine the best design for implementing the >following, and would appreciate any thoughts any of you have for similar >situations: > > > >I have multiple turbine sites, some accessible to anyone who finds it, >others will require different levels of access. For instance > > > >- http://site/web/servlet/web/index.vm is a public accessible site > >- http://site/web/servlet/web/site2,index.vm is a public accessible site > >- http://site/web/servlet/web/admin,index.vm is only for administrators > >- http://site/web/servlet/web/staff,index.vm is an intranet only for staff > > > >For many templates on each of these sites, I don't require Screen Classes... >so my question is has anyone encountered this & come up with a clever design >(or is there one I just don't know about) for implementing an isAuthorized >check based on turbine context without creating screen classes that extend >velocitySecureScreen for each template? > > > >Any thoughts or suggestions will be appreciated! > > > >-d > > > > > > I suggest that you create in the appropriate place a class named Default which inherits from VelocitySecureScreen. If Turbine is not able to find a screen class for your templates, it will then apply the Default class. Hope this helps Fr�d�ric --------------------------------------------------------------------- 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]
