Robert Koberg wrote:
Hi - see comments below
- how are namespaces handled? how do you declare them? Is XPath
fully supported (uses Jaxen perhaps?)?
- are there modes and named templates?
- can you do something like:
#if ($foo)
#match("foo")$context.applyTemplates()#end
#else
#match("*")$context.applyTemplates()#end
#end
- can you use the XML nodes in a conditional. For example say I have
a source like:
<foo bar="something"/>
Can an if be like an XSL if testing the existence of the bar
attribute like:
#if (@bar)
do something...
#end
I'm not sure that a template engine should be a "serious XML
tranformation tool", but I suppose that's the beauty of software
marketing - you can always just reposition if there isn't uptake in
current incarnation.
The point of DVSL is to have a separate tool to handle the XML
processing, and just invoke velocity templates for output formatting.
The intent was to replace anakia, which is really just a procedural
approach to rendering our xml-based documentation system.
Yep, any chance of answering the questions above?
Sorry - did in a separate email.
<snip/>
I would be surprised as well. But were I doing serious XML
processing, I wouldn't be using a templating engine for anything but
templating.
Yep, I would use XSL/SAX/[some]DOM for serious XML processing. I was
trying to get to the limits/functionality/ability of DVSL. From the
(lack of) response from Geir, I don't think DVSL should be compared to
(marketed as) XSL.
No, and it generally isn't, but XSL is what it was patterned after, so
being able to say "like XSL" helps people grok it...
I think that the top blub is pretty honest :
http://jakarta.apache.org/velocity/dvsl/index.html
geir
best,
-Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
