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

Elliotte Rusty Harold resolved XERCESJ-1657.
--------------------------------------------
    Resolution: Fixed

> Update website
> --------------
>
>                 Key: XERCESJ-1657
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1657
>             Project: Xerces2-J
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Ortwin Glueck
>            Priority: Major
>
> The Xerces Website's first sentence is: Welcome to the future!
> This suggests that Xerces is a modern XML parser that is better than the 
> JDK's built-in parser. However, the last Xerces release was in 2010. Also the 
> shipped xml-apis.jar contains an ancient (2009) version of the APIs found in 
> any modern JDK (JAXP).
> I have found no hint in the documentation that people ususally don't need 
> Xerces for XML processing. Only hints how to drop all the Xerces jars into 
> the endorsed folder, causing a massive downgrade of the XML infrastructure to 
> stoneage in modern JDKs.
> I don't know if Xerces is actually something useful for a lot of people 
> today. If it is, the website should clearly state those use cases. If it 
> isn't then the website should have a big fat warning that this code is 
> subject to bitrot and putting it into endorsed will negatively impact the 
> functionality of their JDK.
> For many years Xerces was useful and necessary. But since the JDK started 
> shipping all these things in a stable way, this is no longer the case. But 
> the Internet is still full of references and false hints to Xerces. Please 
> finally admit that this project is effectively dead, outdated and legacy.
> Keeping the website as is,  leads people into a false corner and wastes 
> uncountable hours of valuable developer time wordwide.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to