Re: custom outputText

2007-08-29 Thread Mike Kienenberger
Yes, I think you're on the right track. You don't need to create a custom OutputText component; you just need to create a custom OutputText renderer. If you're using facelets, you can probably do this by using a generic attribute, so you really only need to create a new renderer. If you're

Re: custom outputText

2007-08-29 Thread Mike Kienenberger
One other idea: Consider outputting the highlighted string in a span, and having a highlightedStyleClass (and/or highlightedStyle) attribute that you'd add to the span. That should allow a great deal of flexibility to what can be done with this component. On 8/29/07, Mike Kienenberger [EMAIL

Re: custom outputText

2007-08-29 Thread Mike Kienenberger
Since the most likely place for an error to occur is dealing with creating and populating the attribute on the component, I'd recommend writing the renderer first, and hardcoding the value for the matchingValue at first. For example, in your custom renderer, public String