You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xerces.apache.org by Andy Clark <an...@apache.org> on 2000/03/31 01:45:20 UTC
Upcoming Changes to Xerces-J
This note is to update all of the Xerces-J developers regarding
some upcoming changes. We are going to be changing the internal
architecture of the parser to enable XML Schema support. The
changes will only affect the internals.
Since this change is more than just a simple branch and merge,
we are going to be phasing the updates into the main CVS branch.
However, before doing so we will tag the current source base
and you'll be able to extract based on the tag, if you need to.
I'll post the tag name when it happens.
The update will have the following phases:
PHASE 1: Adding new files
PHASE 2: Modifying existing files
PHASE 3: Removing old files
Commits aren't atomic in CVS but between phases the repository
should (cross fingers) remain in a clean, compilable state.
After the phases, the parse should be roughly equivalent to
the current Schema support but updated to the February draft.
Once the code is in the main branch of the repository, we can
attack the problem of moving towards full XML Schema support.
--
Andy Clark * IBM, JTC - Silicon Valley * andyc@apache.org
Re: Upcoming Changes to Xerces-J
Posted by Wong Kok Wai <wo...@pacific.net.sg>.
I thought, with the Crimson contribution, the legal issues are resolved. Looks
like I'm wrong. :-(
Mike Pogue wrote:
> Look at the CVS repository. It's there!
>
> But, we will not distribute it as part of a normal build,
> until the legal issues surrounding our ability to freely redistribute it
> are resolved. This is because the current JAXP license isn't clear
> as to whether an Open Source implementation (which might be a superset of the
> spec, for example) is OK.
>
> Sun is aware of the issue, and is working on it. In the mean time, consider
> this code "experimental" and "not implementing JAXP".
>
> Mike
>
Re: Upcoming Changes to Xerces-J
Posted by Mike Pogue <mp...@apache.org>.
Look at the CVS repository. It's there!
But, we will not distribute it as part of a normal build,
until the legal issues surrounding our ability to freely redistribute it
are resolved. This is because the current JAXP license isn't clear
as to whether an Open Source implementation (which might be a superset of the
spec, for example) is OK.
Sun is aware of the issue, and is working on it. In the mean time, consider
this code "experimental" and "not implementing JAXP".
Mike
Wong Kok Wai wrote:
>
> Is it possible to have a release that supports JAXP?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Upcoming Changes to Xerces-J
Posted by Edwin Goei <Ed...@eng.sun.com>.
Sean Champ wrote:
>
> what is JAXP?
>
> (esp: would you have any tutorial links about it?)
See http://java.sun.com/xml -- particularly the right sidebar.
Re: Upcoming Changes to Xerces-J
Posted by Sean Champ <s-...@postoffice.pacbell.net>.
what is JAXP?
(esp: would you have any tutorial links about it?)
Wong Kok Wai wrote:
>
> Is it possible to have a release that supports JAXP?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Upcoming Changes to Xerces-J
Posted by Wong Kok Wai <wo...@pacific.net.sg>.
Is it possible to have a release that supports JAXP?
Re: Upcoming Changes to Xerces-J
Posted by Mike Pogue <mp...@apache.org>.
There's a lot of work going on in the Schema area right now...
It's very likely that the latest CVS stuff is in an inconsistent state, for at
least another few days. You can watch the progress in CVS itself, but it's all
Schema stuff going in, to match the latest draft specs.
Hang in there! When there's something working (barely), there will be a post here.
Mike
"George T. Joseph" wrote:
>
> I haven't seen a status in a while. The current CVS tree compiles OK but
> produces errors and stack traces for even the simplest schema data. Should it
> be working?
>
> I don't have the time to help with specific coding tasks, but I could help
> test/debug.
>
> george
>
> -----Original Message-----
> From: Andy Clark [mailto:andyc@apache.org]
> Sent: Wednesday, April 05, 2000 14:30
> To: xerces-j-dev@xml.apache.org
> Subject: Re: Upcoming Changes to Xerces-J
>
> The merge is complete. The new pipeline architecture is in place
> but we are not yet up to the Schema support that we had before. We
> will be working feverishly now to move towards complete Schema
> support. I'll keep everyone informed of progress.
>
> If anyone wants to help, let me know.
>
> --
> Andy Clark * IBM, JTC - Silicon Valley * andyc@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
RE: Upcoming Changes to Xerces-J
Posted by "George T. Joseph" <gt...@peakin.com>.
I haven't seen a status in a while. The current CVS tree compiles OK but
produces errors and stack traces for even the simplest schema data. Should it
be working?
I don't have the time to help with specific coding tasks, but I could help
test/debug.
george
-----Original Message-----
From: Andy Clark [mailto:andyc@apache.org]
Sent: Wednesday, April 05, 2000 14:30
To: xerces-j-dev@xml.apache.org
Subject: Re: Upcoming Changes to Xerces-J
The merge is complete. The new pipeline architecture is in place
but we are not yet up to the Schema support that we had before. We
will be working feverishly now to move towards complete Schema
support. I'll keep everyone informed of progress.
If anyone wants to help, let me know.
--
Andy Clark * IBM, JTC - Silicon Valley * andyc@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Upcoming Changes to Xerces-J
Posted by Andy Clark <an...@apache.org>.
The merge is complete. The new pipeline architecture is in place
but we are not yet up to the Schema support that we had before. We
will be working feverishly now to move towards complete Schema
support. I'll keep everyone informed of progress.
If anyone wants to help, let me know.
--
Andy Clark * IBM, JTC - Silicon Valley * andyc@apache.org
Re: Upcoming Changes to Xerces-J
Posted by Andy Clark <an...@apache.org>.
Andy Clark wrote:
> Since this change is more than just a simple branch and merge,
> we are going to be phasing the updates into the main CVS branch.
> However, before doing so we will tag the current source base
> and you'll be able to extract based on the tag, if you need to.
> I'll post the tag name when it happens.
The merging of the internal re-architecture for Schema support
has begun. You'll start seeing some commit messages for these
changes soon. If you need to extract the *earlier* source code
*after* these changes take effect, use the tag "Xerces-J_1_0_3_Schema".
For example:
> cvs update -r Xerces-J_1_0_3_Schema
--
Andy Clark * IBM, JTC - Silicon Valley * andyc@apache.org