You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@indexgeo.com.au> on 2003/09/12 05:57:33 UTC
apparent resolver troubles
Juan Jose Pablos wrote:
Subject: Re: cvs commit: xml-forrest/src/resources/schema catalog.xcat
>
> I think that this change fix that error
>
> please can anyone cvs update -r FORREST_05_RC and test it?
This is not the source of the error that was described in the
other thread. The entity resolver has a special bootstrap resolver
that uses a local in-built copy of the catalog DTD. So it should
never need to go wandering on the net to get it. To prove this again,
i just disconnected from the network and the build works fine for me
(without this recent change below).
When i built that resolver.jar and committed it to cvs ages ago,
i built it with JDK-1.4 ... so could that be the problem, should
it be built with JDK-1.3 ?
Another possibility is that there is an old copy of resolver.jar
on the systems of the people who are having trouble. The old
resolver certainly did need to go on the net to get the catalog DTD.
This is what i have on my system ...
build.sh clean
find . -name 'resolver*.jar' -exec ls -l {} \;
...75064 Jul 20 18:31 ./lib/core/resolver-20030708.jar
...75064 Jul 8 17:50 ./tools/ant/lib/resolver.jar
That second one is copied there by the build from the lib/core/
Does the .jar on your system have the same file size as me (75064).
--David
> > cheche 2003/09/11 07:40:20
> >
> > Modified: src/resources/schema catalog.xcat
> > Log:
> > Avoid forrest to validate to oasis site. It fails for users with proxy.
> >
> > Revision Changes Path
> > 1.23 +1 -2 xml-forrest/src/resources/schema/catalog.xcat
> >
> > Index: catalog.xcat
> > ===================================================================
> > RCS file: /home/cvs/xml-forrest/src/resources/schema/catalog.xcat,v
> > retrieving revision 1.22
> > retrieving revision 1.23
> > diff -u -r1.22 -r1.23
> > --- catalog.xcat 8 Sep 2003 06:18:11 -0000 1.22
> > +++ catalog.xcat 11 Sep 2003 14:40:20 -0000 1.23
> > @@ -2,8 +2,7 @@
> > <!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
> > "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
> > <!-- OASIS XML Catalog for Forrest -->
> > -<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
> > - prefer="public">
> > +<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
> >
> > <!-- Document Type Definitions (current) -->
> > <public publicId="-//APACHE//DTD Documentation V1.2//EN"
Re: apparent resolver troubles
Posted by Juan Jose Pablos <ch...@che-che.com>.
David Crossley wrote:
>I thought that attribute was actually the inverse, so how do you explain
>>that removing that attribute stop the http conections?
>
>
> Mmm, that is interesting and i have also been trying to explain it
> to myself. We should investigate further. If anyone wants to follow
> up then http://xml.apache.org/commons/
>
> Anyway our Forrest distribution seems to work fine now.
>
> --David
>
I can wait for you explanation some day... :-)
Re: apparent resolver troubles
Posted by David Crossley <cr...@indexgeo.com.au>.
Juan Jose Pablos wrote:
> David Crossley wrote:
> >
> > Yes, we always want to use the local catalog to resolve entities
> > based on their public identifiers, in preference to trundling out
> > on the network, or even on the local filesystem.
>
> I thought that attribute was actually the inverse, so how do you explain
> that removing that attribute stop the http conections?
Mmm, that is interesting and i have also been trying to explain it
to myself. We should investigate further. If anyone wants to follow
up then http://xml.apache.org/commons/
Anyway our Forrest distribution seems to work fine now.
--David
Re: apparent resolver troubles
Posted by Juan Jose Pablos <ch...@che-che.com>.
David Crossley wrote:
>
> Yes, we always want to use the local catalog to resolve entities
> based on their public identifiers, in preference to trundling out
> on the network, or even on the local filesystem.
>
I thought that attribute was actually the inverse, so how do you explain
that removing that attribute stop the http conections?
Thanks for the info!
Cheche
Re: apparent resolver troubles
Posted by David Crossley <cr...@indexgeo.com.au>.
Juan Jose Pablos wrote:
<snip/>
> So is this needed?:
>
> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
> prefer="public">
Yes, we always want to use the local catalog to resolve entities
based on their public identifiers, in preference to trundling out
on the network, or even on the local filesystem.
--David
Re: apparent resolver troubles
Posted by Juan Jose Pablos <ch...@che-che.com>.
Jeff Turner wrote:
>
> When David committed his fix, he did not remove the FORREST_05_RC tag
> from tools/ant/lib/resolver.jar, so your test against the FORREST_05_RC
> tag probably had both new and old resolver.jars in the classpath. I've
> fixed that now. I can switch off networking and successfully build
> projects, so I'm happy this bug is fixed.
Thank you Jeff!!
So is this needed?:
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
prefer="public">
This has been added by mistake:
RCS file: /home/cvspublic/xml-forrest/build.xml,v
----------------------------
revision 1.73
date: 2003/09/11 19:37:25; author: cheche; state: Exp; lines: +8 -0
Convert all EOLs to the pair CRLF on fresh-site files except gif & png.
PR: FOR-31
Let me know that works fine for you Jeff,
Later,
Cheche
Re: apparent resolver troubles
Posted by David Crossley <cr...@indexgeo.com.au>.
Jeff Turner wrote:
<snip/>
> When David committed his fix, he did not remove the FORREST_05_RC tag
> from tools/ant/lib/resolver.jar, so your test against the FORREST_05_RC
> tag probably had both new and old resolver.jars in the classpath. I've
> fixed that now. I can switch off networking and successfully build
> projects, so I'm happy this bug is fixed.
Drat, sorry. I am getting better at using tags, i did move
the tag forward on the other files.
Thankfully opensource is looking over my shoulder.
--David
Re: apparent resolver troubles
Posted by Jeff Turner <je...@apache.org>.
On Fri, Sep 12, 2003 at 12:15:27PM +0200, Juan Jose Pablos wrote:
> David,
>
> Hold on here, we need more testing on this issue.
>
> David Crossley wrote:
> >Juan Jose Pablos wrote:
> >Subject: Re: cvs commit: xml-forrest/src/resources/schema catalog.xcat
> >
> >>I think that this change fix that error
> >>
> >>please can anyone cvs update -r FORREST_05_RC and test it?
> >
> >
> >This is not the source of the error that was described in the
> >other thread. The entity resolver has a special bootstrap resolver
> >that uses a local in-built copy of the catalog DTD. So it should
> >never need to go wandering on the net to get it. To prove this again,
> >i just disconnected from the network and the build works fine for me
> >(without this recent change below).
> >
>
> After your modifications of today I am able to see a request to
> www.oasis-open.org.
When David committed his fix, he did not remove the FORREST_05_RC tag
from tools/ant/lib/resolver.jar, so your test against the FORREST_05_RC
tag probably had both new and old resolver.jars in the classpath. I've
fixed that now. I can switch off networking and successfully build
projects, so I'm happy this bug is fixed.
--Jeff
Re: apparent resolver troubles
Posted by Juan Jose Pablos <ch...@che-che.com>.
David,
Hold on here, we need more testing on this issue.
David Crossley wrote:
> Juan Jose Pablos wrote:
> Subject: Re: cvs commit: xml-forrest/src/resources/schema catalog.xcat
>
>>I think that this change fix that error
>>
>>please can anyone cvs update -r FORREST_05_RC and test it?
>
>
> This is not the source of the error that was described in the
> other thread. The entity resolver has a special bootstrap resolver
> that uses a local in-built copy of the catalog DTD. So it should
> never need to go wandering on the net to get it. To prove this again,
> i just disconnected from the network and the build works fine for me
> (without this recent change below).
>
After your modifications of today I am able to see a request to
www.oasis-open.org.
FYI, what I did was not a ramdon change, before I change the change:
I used tcpdump to verify if there is any http reqeust, and I saw first a
domain request:
11:59:11.272301 192.168.1.5.32774 > 192.168.1.2.53: 48027+ A?
www.oasis-open.org. (36) (DF)
11:59:11.277677 192.168.1.2.53 > 192.168.1.5.32774: 48027 1/4/4 A
209.202.168.105 (206)
www.oasis-open.org. 2240 IN A 209.202.168.105
and after that a connection to port 80
11:59:11.290424 192.168.1.5.32809 > 209.202.168.105.80: S
3478140636:3478140636(0) win 5840 <mss 1460,sackOK,timestamp 275544
0,nop,wscale 0> (DF)
> When i built that resolver.jar and committed it to cvs ages ago,
> i built it with JDK-1.4 ... so could that be the problem, should
> it be built with JDK-1.3 ?
>
> Another possibility is that there is an old copy of resolver.jar
> on the systems of the people who are having trouble. The old
> resolver certainly did need to go on the net to get the catalog DTD.
> This is what i have on my system ...
> build.sh clean
> find . -name 'resolver*.jar' -exec ls -l {} \;
> ...75064 Jul 20 18:31 ./lib/core/resolver-20030708.jar
> ...75064 Jul 8 17:50 ./tools/ant/lib/resolver.jar
> That second one is copied there by the build from the lib/core/
> Does the .jar on your system have the same file size as me (75064).
> --David
Re: apparent resolver troubles
Posted by David Crossley <cr...@indexgeo.com.au>.
We had four separate discussion threads on this topic.
The resolution is at:
http://marc.theaimsgroup.com/?l=forrest-dev&m=106335282600332
--David