playframework / playframework/playframework
`Play.XML` should use ThreadLocal SAXParser
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Scala
- Stars
- 12.6k
- Forks
- 4k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 29
Description
Apache xerces uses a lot of Class.forName to create SaxParser object, which will call ClassLoader.loadClass for every xml parsing.
And this will block each other, then leads to bad performance for a high load system.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Play.XML entry point and trace how Apache Xerces creates SAXParser instances during XML parsing. Measure concurrent parsing and inspect class-loading behavior first; done means preserving XML parsing behavior while avoiding repeated parser creation or class loading under load.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100