Redistributing Saxon-EE without a license key

--===============6266183112355183828==
Content-Type: multipart/alternative; boundary="00000000000064530505c94c66ab"

--00000000000064530505c94c66ab
Content-Type: text/plain; charset="UTF-8"

Hi,

I have an open-source application which enables users to perform XSLT
transformations over HTTP using Saxon.

I'm wondering if it's technically and legally possible to bundle a Saxon-EE
.jar with my application. The intention behind this is that users who wish
to use EE functionality can plug in their own license file.

As far as I can see, using an EnterpriseConfiguration without supplying a
license file works fine as long as you don't use EE features, and any
attempt to do so is gracefully denied by raising an SaxonApiException.

I'm less sure about the licensing part, so any hints would be appreciated.

Thanks,
Willem

--00000000000064530505c94c66ab
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>I have an open-source ap=
plication which enables users to perform XSLT transformations over HTTP usi=
ng Saxon.</div><div><br></div><div>I&#39;m wondering if it&#39;s technicall=
y and legally possible to bundle a Saxon-EE .jar with my application. The i=
ntention behind this is that users who wish to use EE functionality can plu=
g in their own license file.</div><div><br></div><div>As far as I can see, =
using an EnterpriseConfiguration without supplying a license file works fin=
e as long as you don&#39;t use EE features, and any attempt to do so is gra=
cefully denied by raising an SaxonApiException.</div><div><br></div><div>I&=
#39;m less sure about the licensing part, so any hints would be appreciated=
.<br></div><div><br></div><div><div><div dir=3D"ltr" class=3D"gmail_signatu=
re" data-smartmail=3D"gmail_signature"><div>Thanks,</div><div>Willem<br></d=
iv></div></div></div></div>

--00000000000064530505c94c66ab--


--===============6266183112355183828==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============6266183112355183828==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
[email protected]
https://lists.sourceforge.net/lists/listinfo/saxon-help 
--===============6266183112355183828==--