You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Pier Fumagalli <pi...@betaversion.org> on 2003/02/10 16:57:00 UTC
Deprecation of the Avalon classes...
Folks... Avalon deprecated ComponentManager in favor of ServiceManager, but
in the 2.1 codebase, although we import the new libraries, all the kit still
relies on the Composable interface...
It looks like that around 80/100 classes implement the deprecated stuff,
should we go around and change those?
Pier
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Deprecation of the Avalon classes...
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Pier Fumagalli wrote, On 10/02/2003 16.57:
> Folks... Avalon deprecated ComponentManager in favor of ServiceManager, but
> in the 2.1 codebase, although we import the new libraries, all the kit still
> relies on the Composable interface...
Err, maybe you missed the discussion. The result is that Avlaon removed
the @deprecated tag on Composable.
> It looks like that around 80/100 classes implement the deprecated stuff,
> should we go around and change those?
Look in the deprecated dir. There are loads of deprecated classes that
the core still depends upon! There is a swotch to make the core compile
without them (and fail), look in the buildfile.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Deprecation of the Avalon classes...
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 10/2/03 16:07, "Leo Sutic" <le...@inspireinfrastructure.com> wrote:
>
>
>> From: Pier Fumagalli [mailto:pier@betaversion.org]
>>
>> Folks... Avalon deprecated ComponentManager in favor of
>> ServiceManager, but in the 2.1 codebase, although we import
>> the new libraries, all the kit still relies on the Composable
>> interface...
>>
>> It looks like that around 80/100 classes implement the
>> deprecated stuff, should we go around and change those?
>
> No.
>
> ComponentManager etc. are not deprecated anymore. We removed the
> deprecation from the classes.
I built the JavaDocs from Saturday, and the deprecations were there... I
might have got something whako... :-)
> See this thread on cocoon-dev:
>
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&w=2&r=1&s=re-precating&q=
> b
>
> and that one on avalon-dev:
>
> http://marc.theaimsgroup.com/?l=avalon-dev&w=2&r=1&s=re-precating&q=b
Yup... Just came back from a loooong time of not being involved, and still
have to learn my way on what's happening ....
(Let's see if those freaks now actually do compile without whining)...
Pier
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Deprecation of the Avalon classes...
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> From: Pier Fumagalli [mailto:pier@betaversion.org]
>
> Folks... Avalon deprecated ComponentManager in favor of
> ServiceManager, but in the 2.1 codebase, although we import
> the new libraries, all the kit still relies on the Composable
> interface...
>
> It looks like that around 80/100 classes implement the
> deprecated stuff, should we go around and change those?
No.
ComponentManager etc. are not deprecated anymore. We removed the
deprecation from the classes.
See this thread on cocoon-dev:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&w=2&r=1&s=re-precating&q=
b
and that one on avalon-dev:
http://marc.theaimsgroup.com/?l=avalon-dev&w=2&r=1&s=re-precating&q=b
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org