From: Wolfgang Hoschek <whoschek@lb...> - 2005-06-22 22:03:06
I can live with the workaround, of course. I mostly dropped the note
to the list to document the source of the problem for archival and
search purposes. It may not be obvious at first sight which component
is causing the problem. Is it saxon, nux, xyz or some third-party
container classloader mess? It's saxon.
On Jun 22, 2005, at 2:49 PM, saxon-help-request@...
> I think this is too marginal a case to justify fixing. I don't
> often say
> that, but one has to draw the line somewhere. The circumvention is
> to write
> a wrapper Java class that handles the situation, and call that
> Michael Kay
>> -----Original Message-----
>> From: saxon-help-admin@...
>> [mailto:saxon-help-admin@...] On Behalf Of
>> Wolfgang Hoschek
>> Sent: 22 June 2005 20:59
>> To: saxon-help@...
>> Subject: [saxon] External function binding bug (early binding)
>> Hi Mike,
>> There is another small bug in the way saxon-8.4 searches and binds
>> Java extension functions.