Leon Messerschmidt wrote:
> I don't think that ScreenLoader need to be a pluggable service. You can
> add/remove your own screen factories without changing ScreenLoader.
>
> Although ScreenLoader is a singleton it doesn't need to be initialized and
> it does not need access to ServletConfig or RunData.
>
> Services that allocates resources will not allocate anything if it is never
> called, but ScreenLoader will *always* be called. (You are going to serve
> screens aren't you :-)
>
> Maybe I'm in the wrong here, but according to the definition in the
> package.html file ScreenLoader does not seem to fit into Services.
Yes you misunderstood me Leon. I didn't mean that ScreenLoader should be
a singleton. ScreenLoader delegates the lookup and loading of Screen
classes to the AssemblerFactoryManager implementing class, and *this*
class could be a Service.
It's true that we don't need pluggable implementation, and early
initialization in this class. But making it a Service won't really
hurt anything, so I would do it just for the sake of being consistent
with the rest of the system.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
