|
Before casting a vote, I would like to seek clarity on one issue this
seems to raise: If the displayValueOnly attibute is set, does the underlying component change ? for example, if I have: <x:someComponent binding="#{someBean.methodReturningComponent}"/>
And I directly manipulate the underlying component with someBean.methodReturningComponent(). If I add the new displayValueOnly, will I still be able to directly manipulate the same underlying component, or will that component now be something different ? I'm thinking it WILL be different, but I would like clarity on that. Thanks, Grant. Martin Marinschek wrote: +1 from me...regards, Martin On 5/10/05, Thomas Spiegl <[EMAIL PROTECTED]> wrote:+1 using Myfaces extended components +1 add an interface similar to UserRoleAware +1 adding displayValueOnly attribute What's about matching style & styleClass attributes (displayValueOnlyStyleClass, displayValueOnlyStyle)? Should we add those attributes as well? +1 from me regards, thomas On 5/10/05, Sylvain Vieujot <[EMAIL PROTECTED]> wrote: |
- Re: Vote for new displayValueOnly attribute Grant Smith
- Re: Vote for new displayValueOnly attribute Sylvain Vieujot
- Re: Vote for new displayValueOnly attribute Martin Marinschek
- Re: Vote for new displayValueOnly attribute Sean Schofield
- Re: Vote for new displayValueOnly attribute Sylvain Vieujot
- Re: Vote for new displayValueOnly attribute Grant Smith
- Re: Vote for new displayValueOnly attribute Martin Marinschek
- RE: Vote for new displayValueOnly attribute Korhonen, Kalle
- Re: Vote for new displayValueOnly attribute Grant Smith
- RE: Vote for new displayValueOnly attribute Korhonen, Kalle
- Re: Vote for new displayValueOnly attribute Sean Schofield
