Hi Michael, I agree with you. Are you suggesting that we can probably design and implement a new Xerces specific property, something like those described at http://xerces.apache.org/xerces2-j/properties.html for selecting the XPath flavor (something like "native, full & both" that I wrote earlier) for XML Schema 1.1 CTA evaluations?
Though I'm also fine with keeping the current implementation as it is (i.e use Xerces native XPath support as default, and fall back to PsychoPath engine if the XPath expressions are more generic). We might also wait for Xerces adopters to show enough interest in this matter, before we do such a design change into Xerces. On Wed, Nov 24, 2010 at 12:39 AM, Michael Glavassevich <[email protected]> wrote: > I'm really not a fan of using system properties to configure the parser. See > my last response on a request [1] to add one to Xerces. Users should be > setting their preferences per parser/validator instance (through JAXP API > setProperty() calls) so that they don't affect the configuration of > parsers/validators being used by other applications within the JVM. > > Also not sure we want to expose this complexity (i.e. the choices we make > internally on which XPath processor to use) to the user. Ideally Xerces > would make the best choices for each of the XPath expressions in their > schema and then the user doesn't need to worry about such details. > > Thanks. > > [1] http://issues.apache.org/jira/browse/XERCESJ-1455 > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [email protected] > E-mail: [email protected] -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
