[jsr-314-open] Resolution? (Wrapping Text with a tag)

[Dan Allen]

+1

On Wed, Jul 8, 2009 at 6:44 PM, Jim Driscoll <Jim.Driscoll at sun.com> wrote:

> In making the changes to the RI, I also discovered that h:inputText had the
> same behavior as h:outputText.  Since the code was shared, and the behavior
> was if anything even more nonsensical in the inputText case, I changed the
> behavior for both.
>
> I'm closing the RI bug that this is associated with, and opening a spec
> issue:
> https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=585
>
> Please comment if you have any concerns.  (We still have a day to fiddle
> with it before it goes live.)
>
> Jim
>
>
> On 7/8/09 11:59 AM, Jim Driscoll wrote:
>
>> As I stated in an earlier email, I'd like this wrapped up by today. This
>> isn't an arbitrary date: I'd like to make the RI changes today, so they
>> go out in our second Beta release - if we're going to change something
>> like this, it's best that it be in a Beta, not snuck into an FCS (or
>> even an RC), so we can actually get feedback before committing to the
>> behavior.
>>
>> We seem to have a (very) rough consensus that Andy's proposed solution,
>> not rendering children of outputText, is acceptable. So, I'll proceed on
>> implementing that solution today.
>>
>> If you have serious concerns about this direction, now would be the last
>> best chance to voice them.
>>
>> Jim
>>
>>
>> On 7/8/09 9:55 AM, Jim Driscoll wrote:
>>
>>>
>>>
>>> On 7/7/09 5:52 PM, Lincoln Baxter, III wrote:
>>>
>>>> I'm ok with #1 -- "does not render childre"n. I'm also for providing a
>>>> "backwards compatability switch" -- but it needs to be documented
>>>> clearly in the component PDL docs so that people are aware of it --
>>>> that'll cause unhappy customers.
>>>>
>>>
>>> The switch I had in mind was an implementation-specific switch - we have
>>> a few of those already in Mojarra. Since the behavior wasn't previously
>>> defined in the spec, it doesn't really make sense to document a switch
>>> to change back to previous behavior in the PDL, since the PDL is part of
>>> the spec, and there was no "previous behavior" in the spec.
>>>
>>> But I share your concern and frustration about getting folks to
>>> understand how to fix it if their existing apps break. Release notes are
>>> the usual place where we put such documentation.
>>>
>>>  This is good in my eyes because it makes a piece of JSF more
>>>> intuitive, with the *OPTION* to do something counterintuitive yet
>>>> possibly necessary for a number of reasons - if we continue to make
>>>> improvements of this sort, then JSF will continue to improve.
>>>>
>>>> --Lincoln
>>>>
>>>>  1. Spec that h:outputText is a leaf component: children are not
>>>>>> rendered.
>>>>>>
>>>>>


-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jsr-314-open-mirror/attachments/20090708/a5bf1cc9/attachment.html