The method selection mechanism in Xalan will always prefer the second
signature since signatures that begin with an ExpressionContext argument
are preferred over those that don't. Why do you need these two
functions with the same name? Do they do different things?
Gary
Shruti Ahuja wrote:
>
> > Hello
> >
> > i have made an extension function in Xpath by the name contains_words
> > .This function has 2 overloaded versions
> > public static boolean contains_words(String searchstr,String tosearch)
> > {
> > //code
> > }
> > and
> > public static boolean contains_words(ExpressionContext mycontext, String
> > searchstr,String tosearch)
> > {
> > //code
> > }
> >
> >
> > i am calling this function in my xpath expression as
> > txt:conatins_words("this is a book","book")
> > where txt is a namespace which maps to this extension class.
> > The problem is that this call always results in the second contains_words
> > being invoked .i want the first one to be invoked.
> > can someone suggest the reason for it to behave this way.
> >
> >
> > thanx
> > Shruti
