Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Reply-To: <reinhard@apache.org>
From: =?iso-8859-1?Q?Reinhard_P=F6tz?= <reinhard_poetz@gmx.net>
To: <dev@cocoon.apache.org>
Subject: RE: CastorTransformer and CastorSourceConverter 
Date: Wed, 16 Jul 2003 08:56:37 +0200
Message-ID: <000701c34b67$6772fe50$1e01a8c0@WRPO>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <LKENJPKDAIKAPKHEOCMMGELBEEAA.cziegeler@s-und-n.de>
Importance: Normal


From: Carsten Ziegeler

> Reinhard P=F6tz wrote:
> >
> > In the scratchpad we have a CastorTransformer. I'm not sure but I=20
> > think that it is a rather long time there. Is it in use and=20
> stable and=20
> > is it time to move it in the main trunk or can we remove it.
> >
> > I also found a CastorSourceConverter in the portal=20
> framework. What are=20
> > the differences? Can they be unified?
> >
> I don't now the CastorTransformer, but the=20
> CastorSourceConverter. The converter is an avalon component=20
> that "converts" io streams from and to java objects. So, you=20
> can read an xml file using castor and get the mapped objects=20
> and vice versa. I guess, this is a more general approach then=20
> the transformer.
>=20
> In general, I guess as well that they can somehow be unified,=20
> e.g. the transformer could use the source converter. I think=20
> there is also a patch for the transformer in bugzilla.

Thank you Carsten!

Cheers,
Reinhard