You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Christoph Reck (JIRA)" <de...@velocity.apache.org> on 2008/07/10 09:41:31 UTC

[jira] Commented: (VELTOOLS-99) XmlTool

    [ https://issues.apache.org/jira/browse/VELTOOLS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612395#action_12612395 ] 

Christoph Reck commented on VELTOOLS-99:
----------------------------------------

Great to have such a tool now from stock!

I browsed over the code and seems quite complete and a very good start.

OK, it is fixed onto dom4j (adds another jar to the using application), with no #4:JXPath and no #5:DVSL like support - but these would be some nice to have sugars that are not essential for the main purpose. I believe it will be easy to setup a variant with these capabilities! If I get the itch - if ever..., I will post the code.

If I see it correctly the result of $doc.foo.bar will be an XmlTool instance with a text node content  "woogie"? Correct me if not.
So with the new string comparison functionality in velocity 1.5 it will also work to do #if($doc.foo.bar == "woogie")...#end - which in previous versions would require an interpolation to cast it to a string.


> XmlTool
> -------
>
>                 Key: VELTOOLS-99
>                 URL: https://issues.apache.org/jira/browse/VELTOOLS-99
>             Project: Velocity Tools
>          Issue Type: New Feature
>          Components: GenericTools
>    Affects Versions: 2.x
>            Reporter: Nathan Bubna
>             Fix For: 2.0
>
>
> There have always been those interested in a general tool to read and utilize XML content in templates.  Various approaches to this have been taken.  Though i've yet to need this myself, i thought it would be prudent to gather ideas and links to relevant discussion and implementations here, in case someone gets the itch or we want to come up with ideas for something like the GHOP contest.
> Here's a XmlTool that Christoph Reck posted to the mailing list:
> http://velocity.markmail.org/search/?q=XmlTool#query:XmlTool+page:1+mid:rpogtxshsqqoiph7+state:results
> Philippe Collignon created XmlGen (http://xmlgen.sourceforge.net/), which offers a very simple API for walking XML docs in a template.  There was talk of contributing the whole project, but that fizzled.  As it is ASL 2 licensed, we could easily adopt relevant portions or, better, find a way to collaborate and keep the portions we're both interested in in one place.
> DVSL has some useful node selection/handling code that uses Dom4j:
> http://svn.apache.org/repos/asf/velocity/dvsl/trunk/src/java/org/apache/dvsl/dom4j/Dom4jNodeImpl.java
> Anakia, of course, also has some useful xpath/xml handling code:
> http://svn.apache.org/repos/asf/velocity/anakia/trunk/src/java/org/apache/anakia/
> It may also prove useful to somehow combine or connect XML reading with the XML writing stuff proposed in VELTOOLS-97 (https://issues.apache.org/jira/browse/VELTOOLS-97)
> And of course, there's probably a lot of other useful XML handling code out there.  At this point, my favorite API by far is XmlGen's which is very Velocity-ish and intuitive to me.  Since XmlGen is a Texen extension and i hope eventually to get around to making VelocityTools integrate naturally into Texen (as well as DVSL and Anakia), it may be that XmlGen's xml reading API(s) could migrate wholly to VelocityTools.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org