Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
From: "Reinhard Poetz" <reinhard@apache.org>
To: <dev@cocoon.apache.org>
Subject: RE: [RT] Implementing Cocoon Blocks
Date: Fri, 19 Sep 2003 19:31:07 +0200
Message-ID: <001201c37ed3$cf8fe8a0$1e01a8c0@WRPO>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Importance: Normal
In-Reply-To: <CEC03C59-EA74-11D7-AAC5-000393CFE402@codeconsult.ch>


From: Bertrand Delacretaz

> Le Jeudi, 18 sep 2003, =E0 21:09 Europe/Zurich, Reinhard Poetz a =
=E9crit :
>=20
> > ...I understand that I can't load a class from another block. My
> > question:
> > Is it possible to load classes from "Cocoon core" (whatever we will
> > consider as core) from within my block via "new" or are=20
> there arguments
> > against it?...
>=20
> I think loading classes directly via new (as opposed to factories + =20
> interfaces) should be discouraged as much as possible, as it creates =20
> unnecessary coupling.
>=20
> Depending on the classloading mechanisms that are implemented, =20
> selective filtering of what is allowed could be implemented easily I =20
> think [1].
>=20
> Do you have examples where direct instantation via "new" is required?

e.g. line 341 in the HTMLGenerator=20

   throw new ProcessingException("Exception in
HTMLGenerator.generate()",e);

(org.apache.cocoon.ProcessingException)

How can I do this in the generator in the future?

Cheers,
Reinhard