I had a private conversation while the mailinglist was out of order and I want to bring the conclusions that were drawn back online.<br><br>To restate the problem, how does JSF handle the case when both a value attribute and body markup are provided for UIOutput components?<br>
<br>1. We need to spec the behavior so there is consistency across implementations<br>2. Ajax should not be handled as a special case (consistency across usage scenarios)<br>3. If the value attribute is used, and the value is not empty, the body markup should be ignored.<br>
<br>The following use case was put forth that relies on the unspecified behavior today:<br><br>&lt;h:outputText style=&quot;border: 1px solid blue&quot; value=&quot;#{escapedText}&quot; escape=&quot;false&quot; rendered=&quot;#{renderCondition}&quot;&gt;&lt;img src=&quot;img/exclmark.gif&quot; alt=&quot;!&quot; /&gt;&lt;/h:outputText&gt;<br>
<br>It&#39;s semantically incorrect to consider both the value and body
content. That would be an attempt to use a shorthand which I don&#39;t think should
be supported. The proper thing to do is introduce additional, nested
tags.<br><br>-Dan<br><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don&#39;t hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters.  Please don&#39;t hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>