[oXygen-user] using custom parser in saxon 9 transformation scenario

[Peter Rushforth]

Hi,

I believe I've set the extension classes correctly.  An odd thing is that when I
try to run the same thing from the command line, when I *don't* use the -u
option I get the same message regarding content not allowed in prolog.

Where I look at the saxon command line documentation, I see that the -u
option is used to tell saxon that the files are "urls", unless they begin with
http: or file:, in which case they are taken as urls as is.

But I don't see anywhere in oxygen I can set the -u parameter.

Thanks for your help.

Cheers,
Peter

On Mon, Apr 21, 2008 at 11:34 AM, Sorin Ristache <> wrote:
> Hello,
>
> First you should make sure that your custom URI resolver is configured
> correctly in the Editor perspective before trying it in the Debugger
> perspective. The custom URI resolver and all the Java classes referenced
> from the custom URI resolver including the custom XML parser must be set as
> XSLT extensions for your transformation. You set an XSLT extension in the
> dialog opened by the Extensions button of the scenario edit dialog:
>
> http://www.oxygenxml.com/doc/ug-standalone/xslt-xquery-extensions.html
>
> You have to set the full name of the Saxon 9 URI resolver class in the Saxon
> 9 Advanced settings available from menu Options -> Preferences -> XML ->
> XSLT/FO/XQuery -> XSLT -> Saxon -> Saxon 9 -> Advanced -- URI Resolver class
> name. If you type "uri" in the search field of the Preferences dialog you
> can locate this setting quickly.
>
> Does the URI resolver work in a transformation applied with a transformation
> scenario in the Editor perspective?
>
>
> Regards,
> Sorin
>
>
>
>
> Peter Rushforth wrote:
> > Hi,
> >
> > I'm new to oxygen, but I have written a custom uri resolver which
> > references a custom parser, for saxon 9.
> >
> > The parser reads a binary format file, and returns xml events to
> > saxon.  It seems to work well
> > interactively; now I would like to use it in the oxygen xslt debugging
> > environment.
> >
> > I have configured a transformation scenario with the appropriate classes
> on the
> > class path including both the resolver and the parser and classes upon
> > which they depend.
> >
> > However when I invoke the transformation, I get "Content is not
> > allowed in prolog", which looks
> > to me like the parser isn't getting first crack at the binary data.
> >
> > Does anyone have a suggestion to help with this?
> >
> > Cheers,
> > Peter
> >
> _______________________________________________
> oXygen-user mailing list
> 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>