Re: External function binding bug (early binding)

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.

Wolfgang.


On Jun 22, 2005, at 2:49 PM, saxon-help-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx  
wrote:

> 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  
> instead.
>
> Michael Kay
> http://www.saxonica.com/
>
>
> > -----Original Message-----
> > From: saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> > [mailto:saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx] On 
> > Behalf Of
> > Wolfgang Hoschek
> > Sent: 22 June 2005 20:59
> > To: saxon-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> > 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.



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click