cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: Source and SourceResolver confusion
Date Wed, 04 Sep 2002 06:42:45 GMT
Nicola Ken Barozzi wrote:
>
> Carsten Ziegeler wrote:
> >
> >>-----Original Message-----
> >>From: Bruno Dumon [mailto:bruno@outerthought.org]
> >>Sent: Tuesday, September 03, 2002 5:23 PM
> >>To: cocoon-dev@xml.apache.org
> >>Subject: Source and SourceResolver confusion
> >>
> >>
> >>I'm a bit confused about the Source & SourceResolver in HEAD. Apparently
> >>the org.apache.cocoon.environment.Source has been deprecated, but the
> >>org.apache.cocoon.environment.SourceResolver is not (and still returns
> >>deprecated cocoon Source objects).
> >
> > Yes, this is true. We can't deprecate the SourceResolver as it is one
> > of the main arguments for the setup() methods for actions,
> generators etc.
>
> Which is why we should start using standard service(ServiceManager sm)
> and other standard Avalon ones instead.
>
At the time, the interfaces for Action, Generator etc were defined, there
was no SourceResolver in excalibur and noone thought of making this
a component.

> The Component would have gotten the serviceManager and no interfaces
> would have changed (although the implementation yes.)
>
Yep, that's right - but unfortunately it's the way it is now and we
shouldn't change the core interfaces (we could do this for a 3.0
version).

Carsten


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message