cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Pötz <>
Subject CastorTransformer and CastorSourceConverter
Date Wed, 16 Jul 2003 06:19:42 GMT

In the scratchpad we have a CastorTransformer. I'm not sure but I think
that it is a rather long time there. Is it in use and stable and is it
time to move it in the main trunk or can we remove it.

I also found a CastorSourceConverter in the portal framework. What are
the differences? Can they be unified?


-----Original Message-----
From: Tony Edwards [] 
Sent: Wednesday, July 16, 2003 1:16 AM
To: ''
Subject: RE: Beans as input for cocoon

I'm using the Castor transformer to convert a large, nasty bean into xml
and then into HTML/PDF. 
It works really well, seems fast (the slowest bit is the bean accessing
the database to get its data) and best of all it manages to convert all
ArrayLists and other complex types.
I initially use an XSP action to instantiate the bean and connect to the
datasource and populate the bean, then I pass this though the Castor
Transformer. I use the same mapping file that comes with the example
because the bean is so huge it would take too long to even come up with
a mapping file but Castor ignores all mappings it can't find or aren't
there and outputs elements based on the Bean field names. Excellent!

-----Original Message----- 
From: Alexander Schatten [] 
Sent: Wednesday, 16 July 2003 1:29 AM 
Subject: Re: Beans as input for cocoon 

Uwe Gerger wrote: 
>we have some Java-beans wich contains the data we wish to transform
>cocoon into PDF. Is there a way how we can get the data from the bean 
>into cocoon? Maybe there is a special bean-transformer or something
Hm, a BeanGenerator could be a nice idea? but where would this bean get 
the data from? it would be initialized by the generator, so is "empty"; 
off course you could read a file or something in the bean constructor or

access a database; but for both things there seem to be more elegant 
in fact you can access beans from within XSP scripts or actions, maybe 
this is a convenient solution. 


To unsubscribe, e-mail: 
For additional commands, e-mail: 

View raw message