Jon Stevens wrote:
>
> on 1/17/01 12:41 PM, "[EMAIL PROTECTED]"
> <[EMAIL PROTECTED]> wrote:
>
> > Actually, I was not talking about this RunData issue because it's true that
> > the RunDataFactory can be made configurable and produces subclasses of RunData
> > (not currently implemented though).
> >
> > The issue I refered to was that any service referencing RunData in its
> > interface
> > inherited a dependency through this class to ECS, Turbine User and
> > AccessController,
> > Turbine Template system, etc... It's definitely an issue when you're talking
> > componentization.
>
> Right, but a service itself doesn't have to have a RunData object passed
> into it...I guess I'm not seeing the real problem here...
>
Careless use of RunData as a convenience parameter is one of the main
cause of strong tying between Turbine components.
There are also way too many direct references to the Turbine servlet.
For example, TurbineSecurity inherits a dependency on ECS through
the use of Criteria in the SecurityService interface !
(Criteria -> TurbineDB -> DBConnection -> ServletUtils ->
Turbine -> RunData -> ECS )
If you don't want your components to be used outside of the complete
Turbine framework than you don't have to mind, but if you want people
to be able to pick only the part of Turbine they're interested in
then this need to be fixed...
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
