Re: psychopath API changes (was Re: [Fwd: Re: [Wtp-wst-dev] Dates Times..and Duration fixes])
I didn't read all the details from your linked threads, but be sure you
are familar with our WTP Policy on API and deprecation.
In gist, once released, we want to never break adopters, API used or not.
And the rest of the Policy document explains what that means in a little
Hope it helps set the expectation ... its serious stuff.
Mukul Gandhi <mukul.gandhi@xxxxxxxxxx>
"Web Standard Tools developer discussions." <wtp-wst-dev@xxxxxxxxxxx>
09/21/2009 11:50 PM
psychopath API changes (was Re: [Fwd: Re: [Wtp-wst-dev] Dates Times..and
I asked question on xerces-dev list, about PsychoPath API changes, and
it's impact on Xerces-J.
Here is a link to this xerces-dev thread,
The imp point as I wrote in xerces thread is, that it's nice if PsychoPath
deprecates the APIs, and not drop any public APIs suddenly (unless it's
Any comments please, from the perspective of PsychoPath project and how we
can help adopters like Xerces?
Sent by: "Web Standard Tools developer
09/17/2009 07:23 Subject
PM [Fwd: Re: [Wtp-wst-dev] Dates
Times..and Duration fixes]
Please respond to
----- Message from Mukul Gandhi <mukul_gandhi@xxxxxxxxx> on Thu, 17 Sep
2009 06:45:17 -0700 (PDT) -----
To: Jesper Steen Møller <jesper@xxxxxxxxxxxxx>
cc: David Carver <d_a_carver@xxxxxxxxx>
Subject: Re: [Wtp-wst-dev] Dates Times..and Duration fixes
Thanks for your mail.
I have been missing the discussions on wtp-wst-dev lately, because I was
not subscribed on it. Now I am subscribed to wtp-wst-dev, and hope to read
the discussions there, and would try to respond on time.
I looked at the API changes you have proposed at the link on, wtp-wst-dev.
The changes seem to change significantly (a bit at least :)) the
APIs. It also seems to me, that an end user Java program (like say
source code), needing to perform XPath 2.0 evaluations, using PsychoPath
would need to get modified to use the new APIs, that you have proposed.
The current plan at Xerces-J seems to be, is that we would use a lesser
compliant PsychoPath processor, which is posted on Xerces-J repository
(which runs on min JRE 1.3 level). Xerces-J Users wishing to use a more
compliant PsychoPath processor (I believe, a 100% compliant processor
sometime in future..), need to download it directly from www..eclipse.org
site. Such users obviously shall, use JRE 1.5 level (or 1.4 level, when we
port PsychoPath to JRE 1.4).
If the API changes you are proposing goes into PsychoPath, then Xerces-J
users desiring to use the latest eclipse.org version of PsychoPath, I
would face problems using the latest PsychoPath. Xerces-J wouldn't work
with latest PsychoPath, because some of PsychoPath's APIs would have
changed (as proposed at the link, you have cited). To use the newer
PsychoPath APIs, Xerces-J PsychoPath calls would also need changing .
I am thinking how Xerces-J might like to handle this change ? At the
moment (and also for the dec 09 release), I think Xerces-J would ship with
min JRE 1.3 support.
The option I think might work for Xerces-J is, in future Xerces-J can
users to select PsychoPath version (an old one, or the latest one[with
newer APIs]) via some property, and Xerces-J would have to provide two
versions of PsychoPath calls (one complying to JRE 1.3 version, and one
These are my personal option, about how Xerces-J should evolve along with
PsychoPath. I need to ask the larger Xerces-J developer community, to get
consesus on xerces-dev list. I am thinking to do it shortly. Could you
please suggest, what needs to be asked on xerces-dev forum with regards to
the PsychoPath API changes you have proposed, and I'll post a question on
Another option with Xerces-J is, that Xerces-J users can easily use
PsychoPath upto WTP 3.2M2 release, without requiring any API changes at
Xerces end. I think, it would be nice, if PsychoPath can comply to 100%
with the spec (and we have a milestone release from Eclipse WTP with
100%[or very near to that] spec compliance for PsychoPath, with currently
available old APIs), and then we start with the API changes, that you have
proposed. What your and Dave's opinion about this?
Regarding the technical merits of the API changes, you have proposed, I
find the ideas ok (+1 from me for this :)), that you proposed on the
wtp-wst-dev list. If Dave doesn't have objections, these changes are fine
Regarding the JRE 1.4 port work for PsychoPath, I have yet to start it
formally. I think, I should attempt this, when PsychoPath reaches about
100% compliance to the spec.. I think, I need to manage duplicacy of
for PsychoPath JRE 1.4 port work.
--- On Wed, 9/16/09, Jesper Steen Møller <jesper@xxxxxxxxxxxxx> wrote:
> From: Jesper Steen Møller <jesper@xxxxxxxxxxxxx>
> Subject: Re: [Wtp-wst-dev] Dates Times..and Duration fixes
> To: "Mukul Gandhi" <mukul_gandhi@xxxxxxxxx>
> Cc: "David Carver" <d_a_carver@xxxxxxxxx>
> Date: Wednesday, September 16, 2009, 2:50 PM
> Hi Mukul,
> Great news on the success with XML Schema 1..1 (I read your
> blog, as well).
> Could I get you to look at my proposed API changes for
> My questions are these:
> - What is your reaction to the proposed changes (+1/0/-1)
> - If we make these changes and bump the version number to
> 2.0, during M3, how badly will that interfere with you work
> in Xerces?
> - How is the probe into the 1.4 port going, are you going
> to address this before the december release of Xerces?
> Regarding error messages: It might be possible to get some
> more info out of the parser, but it is not too easy due to
> the strict separation between the lexer and the parser.
> As for type errors and dynamic errors, there are some major
> bugs in how especially type errors are reported. These are
> going to be fixed this week, i.e. for M2.
wtp-wst-dev mailing list