Got it. I had guessed panelgroup would fill that role, but I didn't want to influence the answer ;)

I don't see this as a gap if panelgroup implements clientbehaviorholder, but for convenience, and consistency, I'd argue we should add this to h:outputtext.

If performance is a concern (say, because of inline text being wrapped into output text components on view construction), then the jsf impl should be free to use a lightweight impl-specific component instead.

What are your performance concerns, if I have not inferred correctly?

Lincoln Baxter III
http://ocpsoft.com
http://scrumshark.com
Keep it simple.

On Jan 12, 2010 10:21 AM, "Matthias Wessendorf" <matzew@apache.org> wrote:

On Tue, Jan 12, 2010 at 4:02 PM, Andy Schwartz <andy.schwartz@oracle.com> wrote: > Hey Lincoln - > >...

I think that using h:panelGrid is not perfect, but it is better than
abusing <label>.

-Matthias

> > Andy > >> >> The next question is: Do we need such a mechanism? That's, for the most >> part, t...

-- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slidesh...