[
https://issues.apache.org/jira/browse/VELTOOLS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558453#action_12558453
]
Nathan Bubna commented on VELTOOLS-99:
--------------------------------------
Re #1: Did you see the syntax that XmlGen offers?
(http://xmlgen.sourceforge.net/) It uses 1a (of your options above), and also
handles non-xpath navigation very well.
Re #2: I'm openminded here, with biases toward whatever work has already been
done :).
Re #3: I'd certainly like to support something like $xml.parse('foo.xml') as
well as the Anakia/XmlGen type method of configuring xml docs to be available
under a specified key.
Re #4: JXPath sounds very cool, though i don't really know that we need to be
able run xpath agains JDOM or POJOs from within the template, at least not via
$xml. That might be better for an separate XpathTool.
Re #5: I don't know, nor am i sure i understand how that would be used. Can
you give a usecase or example?
P.S. better whitespace control would be great, but i don't think that has
anything to do with an XmlTool ;-)
> 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.x
>
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
