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

[jira] Resolved: (VELTOOLS-99) XmlTool

     [ https://issues.apache.org/jira/browse/VELTOOLS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Bubna resolved VELTOOLS-99.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.x)
                   2.0

Ok, i found need for processing XML in my templates, so i went ahead and wrote this.  The API is much inspired by XmlGen, but the implementation uses Dom4j under the covers and is largely derived from DVSL's Dom4jNodeImpl.

It does what i need and seems like a good start.   Christoph and Philippe, if you're notice this, i'd love to get your feedback on it.

> 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