You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xml-commons-dev@xerces.apache.org by Norman Walsh <nd...@nwalsh.com> on 2005/04/13 16:33:03 UTC
CVS Resolver supports XML Catalogs 1.1
/ Norman Walsh <nd...@nwalsh.com> was heard to say:
| The XML Catalogs spec has been revised by the OASIS Entity Resolution
| Technical Committee. We've added two new entry types. As it turns out,
| one of them was the test case I used for extensibility, so it won't
| be hard to implement the new types :-)
I checked in the updated code this morning. The resolver now supports
systemIdSuffix and uriSuffix as defined in the XML Catalogs V1.1
Committee Specification.
And I added the bare beginnings of a JUnit test framework. I don't
really understand JUnit and Ant integration so I don't think it works
unless your CLASSPATH is setup right. I'd like to fix that,
suggestions welcome.
I also fixed (believe I've fixed :-) 8 of the 10 bugs that were
reported over the last (embarrassed gulp) several years.
I don't know how often the Commons work is packaged up for release,
but I'd sure appreciate feedback from others about the stability of
the new code before it gets shipped off in a real release.
I haven't really had a chance to investigate
http://issues.apache.org/bugzilla/show_bug.cgi?id=23178
and I think, though I can't verify, that I've fixed
http://issues.apache.org/bugzilla/show_bug.cgi?id=26631
confirmation one way or the other most gratefully accepted.
| Is there a process for rewrites? Suppose I spent some time working on
| it, what would I do with the result? Just check the refactored code in
| on top of the existing code? Put the new design in a branch? Put the
| old design in a branch? Give it a new set of package names? What's the
| Right Answer in xml-commons?
After giving it more thought, I think the right answer is to leave it
alone. No one is agitating for the rewrite and the classes are easy
enough to use in the common case.
I fear that changing the API in radical ways will just make everyone's
life harder and perhaps slow the deployment of Catalog support. That
seems like a high price to pay just to sweep some of my niave coding
under the rug.
That said, if there's a groundswell of support for a more modern API,
I'd be happy to work on it.
Be seeing you,
norm
--
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
Re: CVS Resolver supports XML Catalogs 1.1
Posted by Neil Graham <ne...@ca.ibm.com>.
Thanks David,
This looks to me exactly like the right thing to do.
Cheers!
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
David Crossley <cr...@apache.org>
05/06/2005 01:13 AM
To
Norman Walsh <nd...@nwalsh.com>
cc
commons-dev@xml.apache.org
Subject
Re: CVS Resolver supports XML Catalogs 1.1
Norman Walsh wrote:
> / Neil Graham was heard to say:
> |
> | Of the various components of xml-commons, I know Xerces-J only uses
> | Resolver and XML-APIS at the moment; we don't use which, for instance.
I
> | think Xalan-J only uses XML-APIS. So it seems to me like it would
make
> | sense to make the components as autonomous as possible; if you only
need
> | XML-APIS, for instance, you should not need to carry around a NOTICES
file
> | about public-domain material from Arbortext.
> |
> | So I'd suggest we establish separate NOTIZCES files for each of the
> | subcomponents from the start.
>
> Tell me where you want the notices file and I'll be happy to move the
> notice to there.
I gather that the NOTICES file needs to go at the top-level of
the distribution beside the LICENSE file.
I added a file at java/src/org/apache/xml/resolver/NOTICE-resolver.txt
--David
Re: CVS Resolver supports XML Catalogs 1.1
Posted by David Crossley <cr...@apache.org>.
Norman Walsh wrote:
> / Neil Graham was heard to say:
> |
> | Of the various components of xml-commons, I know Xerces-J only uses
> | Resolver and XML-APIS at the moment; we don't use which, for instance. I
> | think Xalan-J only uses XML-APIS. So it seems to me like it would make
> | sense to make the components as autonomous as possible; if you only need
> | XML-APIS, for instance, you should not need to carry around a NOTICES file
> | about public-domain material from Arbortext.
> |
> | So I'd suggest we establish separate NOTIZCES files for each of the
> | subcomponents from the start.
>
> Tell me where you want the notices file and I'll be happy to move the
> notice to there.
I gather that the NOTICES file needs to go at the top-level of
the distribution beside the LICENSE file.
I added a file at java/src/org/apache/xml/resolver/NOTICE-resolver.txt
--David
Re: CVS Resolver supports XML Catalogs 1.1
Posted by Norman Walsh <nd...@nwalsh.com>.
/ Neil Graham <ne...@ca.ibm.com> was heard to say:
| Hi David and all,
|
| Of the various components of xml-commons, I know Xerces-J only uses
| Resolver and XML-APIS at the moment; we don't use which, for instance. I
| think Xalan-J only uses XML-APIS. So it seems to me like it would make
| sense to make the components as autonomous as possible; if you only need
| XML-APIS, for instance, you should not need to carry around a NOTICES file
| about public-domain material from Arbortext.
|
| So I'd suggest we establish separate NOTIZCES files for each of the
| subcomponents from the start.
Tell me where you want the notices file and I'll be happy to move the
notice to there.
Be seeing you,
norm
--
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
Re: CVS Resolver supports XML Catalogs 1.1
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi David and all,
Of the various components of xml-commons, I know Xerces-J only uses
Resolver and XML-APIS at the moment; we don't use which, for instance. I
think Xalan-J only uses XML-APIS. So it seems to me like it would make
sense to make the components as autonomous as possible; if you only need
XML-APIS, for instance, you should not need to carry around a NOTICES file
about public-domain material from Arbortext.
So I'd suggest we establish separate NOTIZCES files for each of the
subcomponents from the start.
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
David Crossley <cr...@apache.org>
04/22/2005 11:59 PM
To
Michael Glavassevich/Toronto/IBM@IBMCA
cc
commons-dev@xml.apache.org
Subject
Re: CVS Resolver supports XML Catalogs 1.1
Michael Glavassevich wrote:
> On the subject of the 2.0 license, I noticed in a recent commit of the
> resolver code [1] an attribution notice was added to the bottom of the
> license text. Shouldn't this be placed in a NOTICE file rather than the
> source code?
That is right Michael. I had actually started writing
a response wondering the same.
There are various products at xml-commons. Should they
all share the same NOTICE file. Anyway, we will start
with one and perhaps later we can split it.
I will start a NOTICE file at the top-level and people
can add as they see fit.
Norm can you please move to that.
See an example file at
http://www.apache.org/licenses/example-NOTICE.txt
How should this file be used? At Apache Forrest we have
only been adding to it when licensing conditions of the
supporting product require attribution.
--David
> [1]
>
http://cvs.apache.org/viewcvs.cgi/xml-commons/java/src/org/apache/xml/resolver/Catalog.java?r1=1.14&r2=1.15&diff_format=h
>
> David Crossley <cr...@apache.org> wrote on 04/13/2005 11:24:39 PM:
>
> > Norman Walsh wrote:
> > > I don't know how often the Commons work is packaged up for release,
> > > but I'd sure appreciate feedback from others about the stability of
> > > the new code before it gets shipped off in a real release.
> >
> > XML Commons Resolver can be shipped separately.
> > That is what we did with the 1.1 version. It can go out
> > anytime that we are ready. While a bit of testing is
> > happening, i will try to get the website updated so
> > that we can document some of the new features and fixes.
> >
> > I just updated the old Apache License headers to be
> > Apache License 2.0 and added some missing ones.
> > It is a new requirement that all releases must be so.
> >
> > The new resolver is working nicely for me in
> > my local version of Apache Forrest and i just
> > committed the updated jar, so we will see how our
> > other developers go with it.
> >
> > We are not using any new features yet of course.
> > I am just saying that it works as a drop-in replacement
> > for the previous version.
> >
> > --David
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
Re: CVS Resolver supports XML Catalogs 1.1
Posted by David Crossley <cr...@apache.org>.
Michael Glavassevich wrote:
> On the subject of the 2.0 license, I noticed in a recent commit of the
> resolver code [1] an attribution notice was added to the bottom of the
> license text. Shouldn't this be placed in a NOTICE file rather than the
> source code?
That is right Michael. I had actually started writing
a response wondering the same.
There are various products at xml-commons. Should they
all share the same NOTICE file. Anyway, we will start
with one and perhaps later we can split it.
I will start a NOTICE file at the top-level and people
can add as they see fit.
Norm can you please move to that.
See an example file at
http://www.apache.org/licenses/example-NOTICE.txt
How should this file be used? At Apache Forrest we have
only been adding to it when licensing conditions of the
supporting product require attribution.
--David
> [1]
> http://cvs.apache.org/viewcvs.cgi/xml-commons/java/src/org/apache/xml/resolver/Catalog.java?r1=1.14&r2=1.15&diff_format=h
>
> David Crossley <cr...@apache.org> wrote on 04/13/2005 11:24:39 PM:
>
> > Norman Walsh wrote:
> > > I don't know how often the Commons work is packaged up for release,
> > > but I'd sure appreciate feedback from others about the stability of
> > > the new code before it gets shipped off in a real release.
> >
> > XML Commons Resolver can be shipped separately.
> > That is what we did with the 1.1 version. It can go out
> > anytime that we are ready. While a bit of testing is
> > happening, i will try to get the website updated so
> > that we can document some of the new features and fixes.
> >
> > I just updated the old Apache License headers to be
> > Apache License 2.0 and added some missing ones.
> > It is a new requirement that all releases must be so.
> >
> > The new resolver is working nicely for me in
> > my local version of Apache Forrest and i just
> > committed the updated jar, so we will see how our
> > other developers go with it.
> >
> > We are not using any new features yet of course.
> > I am just saying that it works as a drop-in replacement
> > for the previous version.
> >
> > --David
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
Re: CVS Resolver supports XML Catalogs 1.1
Posted by Norman Walsh <nd...@nwalsh.com>.
/ David Crossley <cr...@apache.org> was heard to say:
| I just updated the old Apache License headers to be
| Apache License 2.0 and added some missing ones.
| It is a new requirement that all releases must be so.
Ah, thanks. Sorry about that.
| The new resolver is working nicely for me in
| my local version of Apache Forrest and i just
| committed the updated jar, so we will see how our
| other developers go with it.
|
| We are not using any new features yet of course.
| I am just saying that it works as a drop-in replacement
| for the previous version.
Good news!
Be seeing you,
norm
--
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
Re: CVS Resolver supports XML Catalogs 1.1
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
On the subject of the 2.0 license, I noticed in a recent commit of the
resolver code [1] an attribution notice was added to the bottom of the
license text. Shouldn't this be placed in a NOTICE file rather than the
source code?
Thanks.
[1]
http://cvs.apache.org/viewcvs.cgi/xml-commons/java/src/org/apache/xml/resolver/Catalog.java?r1=1.14&r2=1.15&diff_format=h
David Crossley <cr...@apache.org> wrote on 04/13/2005 11:24:39 PM:
> Norman Walsh wrote:
> > I don't know how often the Commons work is packaged up for release,
> > but I'd sure appreciate feedback from others about the stability of
> > the new code before it gets shipped off in a real release.
>
> XML Commons Resolver can be shipped separately.
> That is what we did with the 1.1 version. It can go out
> anytime that we are ready. While a bit of testing is
> happening, i will try to get the website updated so
> that we can document some of the new features and fixes.
>
> I just updated the old Apache License headers to be
> Apache License 2.0 and added some missing ones.
> It is a new requirement that all releases must be so.
>
> The new resolver is working nicely for me in
> my local version of Apache Forrest and i just
> committed the updated jar, so we will see how our
> other developers go with it.
>
> We are not using any new features yet of course.
> I am just saying that it works as a drop-in replacement
> for the previous version.
>
> --David
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: CVS Resolver supports XML Catalogs 1.1
Posted by David Crossley <cr...@apache.org>.
Norman Walsh wrote:
> I don't know how often the Commons work is packaged up for release,
> but I'd sure appreciate feedback from others about the stability of
> the new code before it gets shipped off in a real release.
XML Commons Resolver can be shipped separately.
That is what we did with the 1.1 version. It can go out
anytime that we are ready. While a bit of testing is
happening, i will try to get the website updated so
that we can document some of the new features and fixes.
I just updated the old Apache License headers to be
Apache License 2.0 and added some missing ones.
It is a new requirement that all releases must be so.
The new resolver is working nicely for me in
my local version of Apache Forrest and i just
committed the updated jar, so we will see how our
other developers go with it.
We are not using any new features yet of course.
I am just saying that it works as a drop-in replacement
for the previous version.
--David
Re: CVS Resolver supports XML Catalogs 1.1
Posted by robert burrell donkin <rd...@apache.org>.
On Wed, 2005-04-13 at 10:33 -0400, Norman Walsh wrote:
> / Norman Walsh <nd...@nwalsh.com> was heard to say:
> | The XML Catalogs spec has been revised by the OASIS Entity Resolution
> | Technical Committee. We've added two new entry types. As it turns out,
> | one of them was the test case I used for extensibility, so it won't
> | be hard to implement the new types :-)
>
> I checked in the updated code this morning. The resolver now supports
> systemIdSuffix and uriSuffix as defined in the XML Catalogs V1.1
> Committee Specification.
>
> And I added the bare beginnings of a JUnit test framework. I don't
> really understand JUnit and Ant integration so I don't think it works
> unless your CLASSPATH is setup right. I'd like to fix that,
> suggestions welcome.
there are two basic options for ant and junit integration: either use
the ant task or run the appropriate junit class from a java task. using
the ant task is easier but invocation from java sometimes allows greater
control.
there are a couple of other things which might be worth thinking about.
the xml-commons layout is a little bit unusual. most apache java
projects (and most tools) have now consolidated on a strategy that
separates components. if this strategy were adopted, which and resolver
would be organised more like:
xml-commons - which - src - java
| |- tests
- resolver - src - java
|- tests
the other is considering using maven. you would need to adopt the
standard layout and naming conventions but then maven would take care of
setting up stuff like unit test environment. the only downside would be
that i'm uncertain as to how well maven plays with forrest...
- robert