Readonly DOM level 1 implementation wraping TAX.
Entry point is a set of {@link Wrapper.wrap} methods.
Why Wrapper?
Another alternative i.e. let TAX directly implement DOM
intefaces would polute TAX API and cause schizofreny.
Status
Prototype that doe not handle refs, PIs, comments etc. It should
prove concept only.
Why so Many new
Claim: Latest HotSpot has very optimalized new
and
authors suggest to leave classical pool approach.
Consequence: This implementation uses very lightweight wrappers
therefore only drawback it increased garbage production. It should
be also handled in latest HotSpot implementations.