I have already sent this to the xerces-j-user-mailing list but got no answers, so I am trying this here:
I am in process of delivering a XOM-like java library to XMLSchema called 'endymion', that will be released under LGPL as part of the 'narcissus'-project. The goal of the API is to offer a heavily typed, java-like and simple access to the information embedded in an XMLSchema.
* I need to offer a much more 'deep' error reporting mechanism to report validation errors. With this I mean the ability to get a hold on the related facets / elements / restrictions that caused the error. To do this I would have to change the XMLSchemaValidator and let it use deep errors from within.
I could code this quite easily, but only if the work I put in this could be considered to be included into the xerces cvs, as I otherwise would have to keep my version contantly in sync with the rest of the xerces code. Is this at all an option?
* I see that in CVS there have been several changes / updates with regards to the visibility of fields and methods in several API classes. I was wondering if there is a certain goal or reason for permorming these changes and when they are finished / released. It would be really cool to have some public hooks into the org.apache.xerces.impl.dv.xs.* - value-classes to be able to access the actual values of DecimalDV and others.
Kind regards,
Mik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
