I, for one, would be interested in the converter source code.
To help see what's going on, I'd add *a ton* of logging statements to
your code and turn debugging up to FINEST level and trace what happens
when it works vs when it doesn't.
I'm talking about log.trace() at the beginning and end of every method
and in if/else/for/while/etc statements, log.info() to dump the
contents of variables before and after setting them and before
returning a value from a method, etc.
I find this helps me find the source of any problem, generally. The
MyFaces libraries have pretty good logging as well, so even if the
problem is in MyFaces and not your code, you would probably be able to
"see" it.
Wayne
On 11/3/05, Ennio Tosi <[EMAIL PROTECTED]> wrote:
> Hi, I developed a custom converter to highlight certain terms in a string
> that is displayed with an <h:outputText> tag.
>
> Here's a sample code to illustrate how it works:
>
> <h:outputText value="#{myBean.description}">
> <q:stringMatcher match="#{myBean.queryString}" />
> </h:outputText>
>
>
> myBean.queryString property is populated by an inputText in the same page.
>
> So I would like to highlight matching words depending on what the user is
> searching...
>
> The first time I access the page everything works well, but as soon as I
> submit the page, nothing gets highlighted.
> I'm sure myBean.queryString is not null, because in the same page I'm
> displaying it...
>
> If it could be interesting for someone I could post the converter source
> code.
>
> Thanks,
> Ennio
>
>
