I've got a patch for the case you posted, such that
<h:outputText value="#{data.city}"/> is in <h:outputText
value="#{data.state}"/>
works, though
<h:outputText value="#{data.city}"/> <h:outputText value="#{data.state}"/>
will still not work, since that would 1) create lots of new components,
and 2) mess up stuff like panelgrid.
The fix should go in sometime next week, I'd like Ryan to review it first.
You can track the progress of this bug at
https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=959
Thanks for your report.
Jim
On 7/17/09 3:21 PM, webtier_at_javadesktop.org wrote:
> That's a very good point. I removed the h:outputText from my tutorial, where they really are not needed.
>
> However, if I had converted an example to Ajax, then I would have wanted to use h:outputText so I can give the component an ID. And then it would be really weird if that conversion introduced this problem. So, it still would be awfully nice to fix it.
>
> Cheers,
>
> Cay
> [Message sent by forum member 'cayhorstmann' (cayhorstmann)]
>
> http://forums.java.net/jive/thread.jspa?messageID=356354
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: webtier-help_at_glassfish.dev.java.net
>