Some consideration about the xerces DOM implementation 2007-04-24 - By Dick Deneer
Hi Michael,
One last reaction from my side.
Michael Glavassevich wrote:
>
> Well... you can already do that with the JAXP validation API or some
> cleverly written code which uses EventListeners to undo unwanted
> modifications.
>
JAXP is not an option for me, because my design is heavily tied up to xerces
specific features like the grammarpool, XMLEntityResolver,
ExternalSubsetResolver etc.
Michael Glavassevich wrote:
>
> Much more likely to get done if the some of the folks who are interested
> in an implementation in Xerces volunteer to do it. By folks I mean anyone
> not just the existing Xerces developers. There are a fewer active
> developers around here than there used to be with decreasing time
> available to work on the project. We really need more help from the
> community.
>
I hope you will get response to this call. Xerces is geat software, and of
great value to many people.
Thanks again,
Dick Deneer
--
View this message in context: http://www.nabble.com/Some-consideration-about
-the-xerces-DOM-implementation-tf3602407.html#a10166697
Sent from the Xerces - J - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
For additional commands, e-mail: j-dev-help@(protected)
|
|
