Saxon » Saxon-CE

If I understand correctly: you didn't get a license error initially, but then got one after adding the logLevel attribtue value 'FINE' to the URL - the most likely explanation is that you were using a previous version of Saxon-CE requiring another license-file, the URL change then caused the browser to refresh the cache, switching from a cached old version of Saxon-CE (beta 0.2?) to the newer version of Saxon-CE (1.0?) - thus requiring a newer license file with a different name.

A test for this is if you revert to the previous URL without the logLevel attribute you should still see the license error message:

No Saxon-CE license found at: http://localhost/{your path}/saxonce-license-1.txt

Is this the case?

If so, this situation reflects that there are some difficulties with the browser cache - especially when updating the processor, the best approach in these cases is to explicitly clear the entire cache using whatever method your own browser provides. You will then kinow in a more timely manner that the license file is not in the expected location.

Philip Fearon wrote:

If I understand correctly: you didn't get a license error initially, but then got one after adding the logLevel attribtue value 'FINE' to the URL - the most likely explanation is that you were using a previous version of Saxon-CE requiring another license-file, the URL change then caused the browser to refresh the cache, switching from a cached old version of Saxon-CE (beta 0.2?) to the newer version of Saxon-CE (1.0?) - thus requiring a newer license file with a different name.

i've already tried to isolate this issue;

• firebug cache disable is on

• no old saxon ce in effect

• works without appending ?logLevel=FINE

I also tried with a different browser with zero cache and still get issue;

the specific error I get is;

SaxonCE.XSLT20Processor 12:07:52.860

SEVERE: LicenseException in onModuleLoad: No Saxon-CE license found at: http://saxonce-license-1.txt

http://localhost/saxon-ce-1.0/SaxonceDebug/C13D740AA47BA044EDA03E6F9AA2CB78.cache.html

Line 4049

I think something else is in play here

note I get the same behaviour if I just append a ? to the end of script url

and

ok me stupid ....

for some reason I thought this was to be appended to the script invoke, versus the actual url

I think this is probably not a bug ;)

Ok thanks, I expect there's an ambiguity in the documentation (like explicitly stating it's the URL of the host page that is being referred to and ensuring an example is always used to underline this) that led to this assumption so I'll look to correct this.