>The problem is, there is no standard API for PSVI, so the way of >getting such information could change 5 minutes later.
I expect it to change, eg when the DOM abstract-schema APIs are released... but I really hoped there was something Xerces was providing as a semi-official prototype solution. >For prototyping, I suggest you have your own version of ElementPSVImpl Which has its similar fragility problems, since that's an internal object and is also subject to change... and which doesn't seem to have a clean mechanism for plugging in the replacement/subclass other than rewriting portions of the schema validator. I'd _really_ rather see an official mechanism provided by Xalan's PSVI support, even if it is subject to change in the future. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
