If I recall correctly there is a bug or RFE open to improve the
reporting for such cases so it's much clearer what's happening.
Perhaps one aspect of the larger fix could be to detect if the system ID
does not map to our local copy but the public ID suggests that it
should. In such cases the system ID and public ID are inconsistent and
GlassFish could probably detect that.
- Tim
Bill Shannon wrote:
> Tim Quinn wrote:
>> There is one case in which remote access to DTDs or schemas can
>> occur. (I doubt it's happening here because the admin GUI app is the
>> one of interest, but just for completeness...)
>>
>> We map the identifying information in the DTD or schema to local
>> copies of the relevant files. We have had cases in which a user has
>> manually created a descriptor and misspelled some of the that
>> information - I remember specifically an incorrect DTD system ID.
>> When GlassFish fails to find it locally (because of the misspelling)
>> it tries to use the public ID from the DTD which normally refers to
>> the Sun site. If the user spelled that part correctly then the
>> remote retrieval succeeds and things work - although slowly.
>
> Can we turn that off? In the scenario you describe, it's just hiding
> another bug.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>