Raphael Luta wrote:
> > 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.
> >
>
> In that case, I may mis-understand what you're doing with services.
>
> My understanding of the Turbine service system is that it provides a way
> to register initable singleton components that can be accessed from
> other classes and provide well defined functionalities, usually through
> an interface declaration independant of the actual implementations.
>
> The typical service package pattern being:
> <service>/
> <service_interface>.java
> <service_implementation>.java
> <static_service_accessor>.java
>
> If this is a correct definition and the real intent of the service
> framework, what is the point of a JetspeedInitService with an empty
> service interface and which can't be used by any other classes ?
In my opinion, methods that are implicitly called by the framework
itself
provide *a service* no less important that methods explicitly called by
the application.
> It's a hack in my book.
Agreed, this is hack. But subclassing Turbine servlet is a *way* worse
and uglier hack in mine.
> If my defintion is incorrect, I definitely like to know what your definition
> is but I think the name "service" is then misleading : you should rather use
> "component" to define those classes without implying that these classes may
> be of use for others classes (which is something I associate with "service").
See above.
> In any case, whatever implementation method is used for this transitional
> period, it won't be in the code in one month so this argument is really
> for the sake of discussion.
You are right, but the subject of subclassing Turbine servlet pops up on
this list from time to time, and usually people who ask questions about
it show far less understanding of Turbine than you do.
My goal is not irritating you, but showing that the problem in Jetspeed
can be solved without setting example of such a bad practice. If people
start subclassing Turbine in their own applications, it will only yield
more trouble for them and in effect to Turbine maintainers...
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]
