Simon Kitching wrote:
On Sun, 2003-10-05 at 07:26, Jean-Francois Arcand wrote:I'm not absolutely sure (althrouth the solution I've implemented in Tomcat was with the help of the Xerces team). The current implementation will works fine with Xerces 2.1 and lower when you wan to validation both DTD and schema with the same digester instance. The curent implementation contains the "portable way" described in jaxp 1.2 spec. For a reason I can't explain (I'm not following the Xerces dev list), they have changed the way they supports schema & DTD in version 2.3 to 2.5. I think the jaxp spec was unclear about validating both DTD and scheam with the same parser, and that's why we need to set those "unportable" property for now.
Hi Robert,
robert burrell donkin wrote:
hi Jean-Francois
i'm very reluctant to apply a patch that breaks backwards compatibility but i'd be happier to deprecate them.
That was my initial response too. However it seems that the current code is actually broken/unreliable. Is it worse to remove code without the usual deprecation stage, or leave known-broken code in a release?
I'm not sure I would prefer to have an application fail to work correctly than to fail to compile...
Doesn't it really suck that there is no parser-independent way of enabling w3c-standard xml schema support? Is everybody absolutely sure there is no portable way to do this? [NB: I've had a look myself, and this does indeed appear to be the case, though I'm not a JAXP guru].
You can do it actually by calling digester.setFeature or digester.setProperty. Is that what you means?
maybe one solution might be to refactor the setting algorithm into a separate class and then have factory methods for each parse type which create instances that know how to execute the required configuration.+1
Sounds good to me provided everyone is sure there isn't a parser-independent way to do this.
Can this solution be generalised to handle setting of parser-dependent features other than just schema language?
Thanks,
-- Jeanfrancois
Regards,
Simon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
