cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Russell <>
Subject Re: Which is easier XSP vs. Transformer (Cocoon 2)
Date Wed, 20 Dec 2000 09:39:58 GMT
On Tue, Dec 19, 2000 at 10:40:41PM -0500, Berin Loritsch wrote:
> Paul Russell wrote:
> > On Tue, Dec 19, 2000 at 03:48:53PM -0500, Berin Loritsch wrote:
> > > We have a project, and we want to be able to create a mapping
> > > between a generic form XML file and database/EJB entries.
> > > We are using Cocoon 2 on NT 4, IBM WebSphere 3.5 SP2.
> > I don't totally follow what you're after, but have you looked at
> > Castor <URL:>? It's one of Intalio's open
> > source efforts, and looks very good. I'm looking at using it to
> > ease the development overhead for BMP, but it also handles java object
> > to XML mapping.
> I'm after setting up a namespace to do dynamic form processing/presentation.
> I want to use one XML page to describe the form, and a second XML page
> to describe how to map it to the persistent data layer--maybe a third to
> describe access issues.
> So, back to the question in the title:
> Which is easier to develop: an XSP page that reads multiple sources,
> or create a Transformer like the SQL transformer.  I like the ability
> to manage the mappings and configurations in the Sitemap.

I *think* your best bet may well to be to wait for the Actions proposal
to come to fruition. I *think* actions would cover what you're asking
for nicely. Failing that, I'd be tempted to use the transformer option,
semantically dubious though it is.


Paul Russell                                 Email:
Technical Director                             Tel:  +44 (0)20 8553 6622
Luminas Internet Applications                  Fax:  +44 (0)870 28 47489
This is not an official statement or order.    Web:

View raw message