URIResolver used by Oxygen for Saxon

[bdonoghoe]

I use Oxygen to develop XSLT stylesheets that will be run from the command line using the Saxon 9 PE jar.

If have a stylesheet that loads a number of RDF resources as unparsed-text entities. The resources are retrieved by the stylesheet when it is run from within Oxygen but not when run from the command line with the Saxon jar. The reason I believes this is happening is that default URIResolver provided by Saxon does not handle the HTTP 301 "Moved Permanently" return code.

In Curl terms, Oxgygen appears to operate with the --location option ( If the server reports that the requested page has moved to a different location (indicated with a Location: header and a 3XX response code), this option will make curl redo the request on the new place).

Does Oxygen use an open source URIResolver class that could be configured for use with Saxon?

[adrian]

Hi,

The reason the resource with HTTP 301 code is accessible in Oxygen is a modification in the way the HTTP client handles this code. Oxygen catches the 'redirect' and 'moved' HTTP codes and attempts to resolve them transparently to the new destination. This has nothing to do with the URIResolver.
This is handled this way by Oxygen because it needs to resolve this situation for multiple components, not just Saxon.

Regards,
Adrian

[bdonoghoe]

Thanks for the prompt reply.

I am going to use a different approach to the problem I am trying to solve.