on 9/26/2000 11:58 AM, "Leon Messerschmidt" <[EMAIL PROTECTED]> wrote:
> Any suggestions about loader chains? How about something like this in
> TR.properties:
>
> screen.loader=org.apache.turbine.modules.screenLoader
> screen.loader=org.apache.turbine.modules.anotherLoader
> screen.loader=org.apache.turbine.python.pythonLoader
> screen.loader=com.somebody.myLoader
>
> We'll need something like a "master loader" class that cycles through these
> loaders until a screen is found or take appropriate error steps. Won't be to
> difficult to implement. We will probably need to do the same for actions.
>
> The administrator can then simple add/remove comments from these lines to
> include/exclude a screen loader.
>
> Other thoughts?
>
> ~ Leon
Yes. This is acceptable. In fact, if you want to go so far as to convert the
Loaders into Services, I would be highly +1 on that. They are the last thing
that still remain to be done as services.
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
