More fixes for resolver: xml.catalog.verbosity & catalog parsing

[Earl Hood]

Since it appears that development of the resolver code is
stagnant due to response from my previous message containing
patches, I'm not sure if it still worth the effort to
submit others.

However, for a project I'm working on, I've made a couple
of other modifications that may be of interest to others:

(1) Bug-fix to honor xml.catalog.verbosity system property.
    I noticed that if one does not use CatalogManager.properties,
    this system property is never checked.

(2) Proper setting of systemID of InputSource of SAX parsing
    when parsing XML catalog files.  W/o this fix, if a catalog
    file has references to external entities using relative SYSTEM
    identifiers, they are resolved relative to the current working
    directory versus the location of the catalog file being parsed.

    In my case, I was dealing with catalog files that included
    <!DOCTYPE catalog SYSTEM "..."> declarations using relative paths
    to catalog.dtd.  Things would bomb out during parsing since the
    SAX parser could not find the file specified due to invalid base
    URI context.

If there is interest, I can post patches.

--ewh

[Ushakov, Sergey N]

Hi Earl,

I personally would welcome your patches if you make them publicly available
in Bugzilla or similar place. Perhaps some time later they will be
incorporated into the main stream...

I have come across and reported one of the issues you address (regarding
verbosity), but was somewhat shy to intrude without community feedback...
But your message is a sort of first feedback I get :)  So IMHO you did the
right job :)

Regards,
Sergey


----- Original Message -----
From: "Earl Hood" <earl@...>
To: <commons-dev@...>
Sent: Saturday, June 14, 2008 6:48 AM
Subject: More fixes for resolver: xml.catalog.verbosity & catalog parsing

> Since it appears that development of the resolver code is
> stagnant due to response from my previous message containing
> patches, I'm not sure if it still worth the effort to
> submit others.
>
> However, for a project I'm working on, I've made a couple
> of other modifications that may be of interest to others:
>
> (1) Bug-fix to honor xml.catalog.verbosity system property.
>    I noticed that if one does not use CatalogManager.properties,
>    this system property is never checked.
>
> (2) Proper setting of systemID of InputSource of SAX parsing
>    when parsing XML catalog files.  W/o this fix, if a catalog
>    file has references to external entities using relative SYSTEM
>    identifiers, they are resolved relative to the current working
>    directory versus the location of the catalog file being parsed.
>
>    In my case, I was dealing with catalog files that included
>    <!DOCTYPE catalog SYSTEM "..."> declarations using relative paths
>    to catalog.dtd.  Things would bomb out during parsing since the
>    SAX parser could not find the file specified due to invalid base
>    URI context.
>
> If there is interest, I can post patches.
>
> --ewh

[Jacob Kjome]

I believe Norm Walsh, the primary resolver maintainer, has moved on to a separate
xmlresolver codebase [1].  Unless someone steps up to drive development of the
project, I think it's dead on the vine.  Even xmlresolver at java.net doesn't have
a proper release yet.  I'm guessing Norm is a pretty busy guy.


[1] https://xmlresolver.dev.java.net/


Jake


USHAKOV, Sergey wrote:

> Hi Earl,
>
> I personally would welcome your patches if you make them publicly
> available in Bugzilla or similar place. Perhaps some time later they
> will be incorporated into the main stream...
>
> I have come across and reported one of the issues you address (regarding
> verbosity), but was somewhat shy to intrude without community
> feedback... But your message is a sort of first feedback I get :)  So
> IMHO you did the right job :)
>
> Regards,
> Sergey
>
>
> ----- Original Message ----- From: "Earl Hood" <earl@...>
> To: <commons-dev@...>
> Sent: Saturday, June 14, 2008 6:48 AM
> Subject: More fixes for resolver: xml.catalog.verbosity & catalog parsing
>
>
>> Since it appears that development of the resolver code is
>> stagnant due to response from my previous message containing
>> patches, I'm not sure if it still worth the effort to
>> submit others.
>>
>> However, for a project I'm working on, I've made a couple
>> of other modifications that may be of interest to others:
>>
>> (1) Bug-fix to honor xml.catalog.verbosity system property.
>>    I noticed that if one does not use CatalogManager.properties,
>>    this system property is never checked.
>>
>> (2) Proper setting of systemID of InputSource of SAX parsing
>>    when parsing XML catalog files.  W/o this fix, if a catalog
>>    file has references to external entities using relative SYSTEM
>>    identifiers, they are resolved relative to the current working
>>    directory versus the location of the catalog file being parsed.
>>
>>    In my case, I was dealing with catalog files that included
>>    <!DOCTYPE catalog SYSTEM "..."> declarations using relative paths
>>    to catalog.dtd.  Things would bomb out during parsing since the
>>    SAX parser could not find the file specified due to invalid base
>>    URI context.
>>
>> If there is interest, I can post patches.
>>
>> --ewh
>
>
>
>