On 7/21/06, Dhananjay Prasanna <[EMAIL PROTECTED]> wrote:
We tried a hack to solve a similar issue by having a PhaseListener in
the beforeRender phase that walks the component tree and modifies it (in
our case resetting css styles) on offending components (referenced in
the FacesMessages collection).
It's a bit of an ugly hack and doesn't always work: especially in cases
where there component tree has not been built completely in the before
phase or you have components that behave unexpectedly.
But it's a quick fix if it works for you...
The OVF works similarly, but instead of doing it with a phase
listener, it's done with a custom component that's put at the bottom
of the page. By that point, the component tree should be built.
There's a generic ComponentTreeWalker class for building your own
components in OVF if you want to use that as a starting point. All
you need to do is subclass it and define the behavior for the phases
and components you want to do something with.
