cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DURDINA Michal" <>
Subject RE: Design of unmarshaling sitemap component
Date Fri, 30 Jul 2004 07:15:35 GMT
> -----Original Message-----
> From: Hunsberger, Peter [mailto:Peter.Hunsberger@STJUDE.ORG]
> Sent: Thursday, July 29, 2004 7:06 PM
> To:
> Subject: RE: Design of unmarshaling sitemap component
> DURDINA Michal <> writes:
> > Hi,
> > I would like to discuss the design problem of the sitemap 
> > component. My plan is to develop special let's call it 
> > transformer for transforming sources for pages written or 
> > generated by analysts (model) to dynamic pages generating 
> > required results (implementation). The form of model is 
> > custom XML according to given XMLSchema and the 
> > implementation pages should be in form of jxtemplates (or xsp).
> > 
> > The transformation should go like this:
> > 
> > pipeline:
> >             additional data
> >                    |
> > modelXML -> populated modelXML -> computed model -> 
> jxtemplate source
> > 
> > The intent of the pipeline is to generate executable source 
> > from model that will generate required dynamic page. The 
> > trick is that the computed modelXML is not trivial and should 
> > be implemented as Java OM. 
> Wow.  You're overall requirements sounds a lot like ours so I'm
> interested in how you reached this design?  Given your use of 
> jxtemplate
> I can't see that it's performance driven? If not, why not just keep
> everything in XML from end to end and use XSLT to derive the computed
> model?  
> <snip>Castor/java implementation issues</snip>

Yes, keeping everything in XML and using XSLT would also realize the transformation. Given
that it would involve a XSL stylesheet that will do all the computations. Such a stylesheet
would not be easy to write and it will be probably too complex to maintain. Using Java for
computation on input XML should be more straightforward and using jxtemplate for outputing
the resulting XML gains from clear view how the resulting XML will look like. Performance
was not the main requirement as the source generation occures only once and then it is cached
although this should perform better than XSLT.

I already started the implementation and have first version of such a component implemented
as a transformer (case A.). I hope it will meet my requirements and we will profit form this
kind of concept.

Thank you for comment,

View raw message