Re: Saxon serialization methods require Saxon-PE to be

Fair point, Ibll withdraw this question from here and send it to the correct
forum.

Thanks

Ian





From: Michael Kay mike@xxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: 01 June 2018 09:29
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Saxon serialization methods require Saxon-PE to be enabled



As Liam says, it would be better to raise this on a Saxon list (or since
you're a paying customer, you're perfectly entitled to email us directly).



My first guess with this is that you are instantiating Saxon using "new
Processor(false)" rather than "new Processor(true)". But without seeing any
code, that's a shot in the dark, and there are many other possible
explanations.



Michael Kay

Saxonica





On 1 Jun 2018, at 00:57, ian.proudfoot@xxxxxxxxxxx
<mailto:ian.proudfoot@xxxxxxxxxxx>  <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx
<mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> > wrote:



Ibm using a licenced copy of Saxon-PE embedded in a Java application. One of
the stylesheets makes use of xsl:result-document  with
method="saxon:base64Binary". While developing the stylesheets using Oxygen
Editor this works perfectly. However when running my JAR file from the command
line I get an unexpected message:



Error on line 94 of designmap.xsl:

  Saxon serialization methods require Saxon-PE to be enabled



Looking at the Saxon documentation leads me to the Saxon Configuration File,
but so far my attempts have been spectacularly ineffective!



Ibm relatively new to Java development, so it can take me some time to get
my head around the Saxon Java API documentation, but itbs getting easier
every day!

Thanks for any guidance



Ian



iTP-X

 <mailto:ian.proudfoot@xxxxxxxxxxx> ian.proudfoot@xxxxxxxxxxx



Bembridge

Isle of Wight

United Kingdom



 <http://www.mulberrytech.com/xsl/xsl-list> XSL-List info and archive

EasyUnsubscribe (by email)



XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>

EasyUnsubscribe <-list/604558>  (by email <> )