On Wed, 2007-09-12 at 13:25 -0400, Alessandro Bologna wrote: > In any case, what I am really interested is what are the best practices > using Velocity to render complex, quite unstructured, namespace > qualified XML contents.
Your going to run into problems with DVSL/Anakia if your content is unstructured > What was your approach? XSL is the tool for the job. best, -Rob > > Thanks in advance for your responses. > > Alessandro > > > > > > > > > On 9/11/07, Alessandro Bologna <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > my apologies in advance if this is an FAQ, but I couldn't find an answer > > in the documentation, so I decided to write to the list. > > > > In the CMS project I am working on, we are considering using velocity to > > generate "pre-cooked" template based web pages, using XML as data source. > > > > In other words, the data to be published is essentially XML, with elements > > such as <article>, <headline>, <deck>, <body> etc, with some elements > > containing quite unstructured XHTML (i.e variable number of <p/>, <div/> > > etc), and other containing refences to other elements via id/refid. > > > > This data has to be processed to generate static HMTL files that are then > > pushed to Apache for serving them. > > > > Question #1 > > It seems that there are two main options: using XMLEasyBean or/and DVSL. > > Are there any other alternatives? > > > > Question #2 > > In both cases, it seems that XML namespaces are not supported (I am > > getting an empty output if my source contains namespace qualified XML > > elements), am I doing something wrong? > > > > Question #3 > > Any idea of performances, compared to say, XSLT? > > > > Thanks > > Alessandro Bologna > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
