Thanks.  Is this '"disabledOnClientSide" a JSF standard attribute (JSF
1.0? 1.1?) ?
or it is a myfaces extension?

I can't find any documentation about that.

Thanks for any help.

On 10/29/06, Gerald Müllan <[EMAIL PROTECTED]> wrote:
Hi,

this is because the value is not posted back to server and it is
ignored by the browser when submiting the form.

But you can use t:inputText in combination with the attribute
"disabledOnClientSide" which should be set to true.

This makes sure that the value will be pushed to the form.

regards,

Gerald

On 10/29/06, ken carlino <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have page using inputText in myfaces. It works okay. But when I try
> to mark the username field to either 'readonly' or 'disabled' equals
> to 'true'.
>
> Like this:
>    <h:inputText value="#{userForm.user.username}" id="username"
> required="true" styleClass="text large" readonly="true">
>        <v:commonsValidator type="required" arg="#{text['user.username']}"/>
>    </h:inputText>
>
> the input field of the page in browser is not-changeable (as
> expected).  But when i try to do a submit my form, I get this
> error message 'This username (null) or e-mail address (null) already
> exists. Please try a different username.'
>
>
> Can you please tell why the username becomes 'null' when I try to
> submit? If i remove the 'readonly='true'' the submit works (i.e. the
> username is not null).
>
>
> Thank you for any help.
>


--
http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Reply via email to