You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Peter Donald <pe...@apache.org> on 2002/07/09 15:05:36 UTC
Fwd: ECM vs Fortress and the CM
---------- Forwarded Message ----------
Subject: ECM vs Fortress and the CM
Date: Tue, 9 Jul 2002 22:53:00 +1000
From: Peter Donald <pe...@apache.org>
To: ant-dev@jakarta.apache.org
Hi,
Does the ECM still require that components be Composable rather than
Serviceable? If so when is this going to be fixed? If no plans can I go in
and hack it in? Or is Cocoon moving to Fortress sooner so I should not
bother?
--
Cheers,
Peter Donald
*------------------------------------------------*
| Trying is the first step to failure. |
| So never try, Lisa - Homer Jay Simpson |
*------------------------------------------------*
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
-------------------------------------------------------
--
Cheers,
Peter Donald
The big mistake that men make is that when they turn thirteen or fourteen and
all of a sudden they've reached puberty, they believe that they like women.
Actually, you're just horny. It doesn't mean you like women any more at
twenty-one than you did at ten. --Jules Feiffer (cartoonist)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: ECM vs Fortress and the CM
Posted by Berin Loritsch <bl...@apache.org>.
> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org]
>
> I'm happy to use something better than ECM.
> Stefano is publicy saying that he is evaluating the Avalon
> containers to
> replace ECM.
>
> I don't know what we'll use, but I wouldn't touch ECM anyway ;-)
Thank's to Marcus, Fortress now has experimental support for lifecycle
extension--something that Cocoon may need.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: ECM vs Fortress and the CM
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Berin Loritsch wrote:
>>From: Peter Donald [mailto:peter@apache.org]
>>---------- Forwarded Message ----------
>>From: Peter Donald <pe...@apache.org>
>>To: ant-dev@jakarta.apache.org
>>
>>Hi,
>>
>>Does the ECM still require that components be Composable
>>rather than Serviceable? If so when is this going to be
>>fixed? If no plans can I go in and hack it in? Or is Cocoon
>>moving to Fortress sooner so I should not bother?
>
>
>
> ECM should be considered deprecated.
>
> There is an incredible amount of duplication of code if you
> want a ServiceManager version of the ECM.
>
> Fortress provides the smoothest migration path, although it is
> not polished yet.
>
> I cannot vouch for the Cocoon team at this time on their
> plans to use Fortress.
I'm happy to use something better than ECM.
Stefano is publicy saying that he is evaluating the Avalon containers to
replace ECM.
I don't know what we'll use, but I wouldn't touch ECM anyway ;-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: ECM vs Fortress and the CM
Posted by Berin Loritsch <bl...@apache.org>.
> From: Peter Donald [mailto:peter@apache.org]
> ---------- Forwarded Message ----------
> From: Peter Donald <pe...@apache.org>
> To: ant-dev@jakarta.apache.org
>
> Hi,
>
> Does the ECM still require that components be Composable
> rather than Serviceable? If so when is this going to be
> fixed? If no plans can I go in and hack it in? Or is Cocoon
> moving to Fortress sooner so I should not bother?
ECM should be considered deprecated.
There is an incredible amount of duplication of code if you
want a ServiceManager version of the ECM.
Fortress provides the smoothest migration path, although it is
not polished yet.
I cannot vouch for the Cocoon team at this time on their
plans to use Fortress.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>