Raphael Luta wrote:
> We have no problems with the Service infrastructure but a lot of code
> sits in the CVS that *should* be Turbine services but currently are not
> and are in the process of being moved as service.
> During this process, we still need to initialize the components that are not
> yet services and this is done by overriding the Turbine servlet init() method.
>
> When all the components are moved, this init() should be empty and thus
> we can remove the subclass.
>
> The only alternative I see to this process is writing a new service that
> would only initialize all the other components without providing any real
> "service" method, but I find this solution much more a perversion of the
> Turbine service model than the subclass one.
I feel exactly the opposite. For me, writing a temporary wrapper service
seems
to be much less intrusive action.
Initializing other subsystems is a very nice 'service' itself, isn't it?
Move your ininitalization code from Layout into this wrapper service
(JetspeedInitService?) and avoid creating the subclass alltogether.
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]
