Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Mass update to components for Cocoon 2.2
Date: Thu, 23 Oct 2003 10:37:59 +0200
Message-ID: <84F0A43A4248CE45B5C0E20F4C40779C667C4F@naomi.webworks.nl>
Thread-Topic: Mass update to components for Cocoon 2.2
Thread-Index: AcOZP1dNjILNXm5fSw6QODOqsojp6AAAH6vA
From: "Unico Hommes" <Unico@hippo.nl>
To: <dev@cocoon.apache.org>

=20

>=20
> -----Original Message-----
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]=20
> Sent: donderdag 23 oktober 2003 10:29
> To: dev@cocoon.apache.org
>=20
> Another question :)
>=20
> Currently with ECM we have to implement the Component=20
> interface even if we only use Serviceable (because of the=20
> internal handling with the proxies etc.)
>=20

I think the latest ECM release did not require this anymore? At least I
am running components do not implement Component. Though I think there
is an issue when using ServiceSelector in this way.

> Do we still need this with Fortress? I guess: no.
>=20

I did hesitate when I removed it but I couldn't think of a reason why
not to, I know it is not required by Fortress.

-- Unico