Hi all, I have done some study yesterday and today, about what's currently happening with PsychoPath APIs, and here are the issues I think, exist with PsychoPath in relation to Xerces-J.
The PsychoPath XPath 2.0 engine available with, Eclipse WTP 3.2M1 milestone release, works fine with current Xerces-J SVN code. (ref: http://download.eclipse.org/webtools/downloads/ http://download.eclipse.org/webtools/downloads/drops/R3.2/S-3.2M1b-20090814143519/) PsychoPath with Eclipse WTP 3.2M1, has 96% spec compliance (ref: http://intellectualcramps.blogspot.com/2009/08/psychopath-11m1-available.html). <problem> The problem actually comes up with current PsychoPath development code base, which will likely become part of Eclipse WTP 3.2M2 and eventually, Eclipse WTP 3.2. The current PsychoPath development code base has made some API changes, which are not compatible with the current Xerces-J SVN code. Xerces-J assertions calls to PsychoPath APIs (on current PsychoPath development code base, which I tested locally) give error, currently. At present, the impact of PsychoPath API changes are minor, to Xerces-J. for e.g, the following method call, in Xerces-J class AbstractPsychoPathImpl.java: nodeEvalRS.add(new ElementType(contextNode, fDynamicContext.node_position(contextNode))); now needs to be written like: nodeEvalRS.add(new ElementType(contextNode)); and this is the only problem, which Xerces-J currently has, to integrate with the current PsychoPath development code. But in future, PsychoPath might do widespread API changes, which we don't know at present. </problem> my simple question is, how should we handle these PsychoPath API changes at Xerces-J end? Should we request PsychoPath project to do something about this? Or can we (and how) handle this independently at Xerces-J end? I suggest the option to use a system property with Xerces-J, to handle this. But I am not sure, if that's good enough for this situation. Any opinions, please? -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
