[ 
https://issues.apache.org/jira/browse/LANG-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536119
 ] 

Gary Gregory commented on LANG-359:
-----------------------------------

IMO, XML should be outside the scope of [lang]. When I think of [lang], I think 
of what's missing from the java.lang package or a close relative (java.text). 
Now, I know that we have some XML and HTML tidbits in there already, but I 
think that it should stop there. 

I've had a lot of experience with XML libraries and when we pick a tech for a 
given project, whether it is Xerces, Xalan, JAXB, JDOM, XFire, etc, we usually 
end up with some small util or framework code for that project that sits on top 
of one of those tech. But it is usually not generic enough to contribute back 
to the project.

For me, XML is a giant land on a different continent. Then if you start talking 
about XML Schemas and transformations (XSLT), you are entering yet another 
universe of code. For me [lang] is not for this purpose.

Speaking of duplicating code, another way to look at it is: what do you see 
missing from Xerces, Xalan, JAXB, JDOM? Would it not be better to improve those 
XML projects?

> Add an XMLUtils class
> ---------------------
>
>                 Key: LANG-359
>                 URL: https://issues.apache.org/jira/browse/LANG-359
>             Project: Commons Lang
>          Issue Type: New Feature
>            Reporter: Ahmed Mohombe
>
> Please add an XMLUtils class that deals with most common functions required 
> in working with XML. Working directly with the w3 DOM is a PITA, and almost 
> every project that needs XML, implements it's own utility classes, hence much 
> repeating and code duplication.
> IMHO this (commons-lang) is the best place for such an utility cause it would 
> be similar to StringUtils (used so much that everybody wishes it were part of 
> the JDK :) )
> Thanks in advance,
> Ahmed.

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

Reply via email to