If you use the "for" attribute in the message component, you should
also leave out forceId.
It is not needed anymore when using for, this stuff is done
automatically by jsf for you.
You can find the examples under "Ajax Form Components" on the sandbox
examples page.
regards,
Gerald
On 2/21/06, Simon Steiner <[EMAIL PROTECTED]> wrote:
> > Werner, names are a little confusing, but I think Simon talks about
> > inputTextAjax component (validating user input on server side through
> > ajax), and not our inputSuggest comp.
> >
> > @Simon, I have submitted a patch a week ago where the above has
> > changed a little bit.
> >
> > Now, I would suggest to use t:message with the little extension like this:
> >
> > <t:message forceSpan="true" styleClass="errorMessage" for="text1">
> >
> > The inputAjax may look like this:
> >
> > <s:inputTextAjax value="#{inputAjaxBean.text1}" id="text1"
> > validator="#{inputAjaxBean.validateText1}"
> > errorStyle="..."/>
> >
> > This should work in both browsers, like it is shown in the current
> > sandbox example page.
> Where is this?
>
> > Please have also a look at it.
> >
> > Problems solved?
> Nope, switched to server side, tried t:message with/ without
> forceSpan="true" and s:message. Same exception.
>
>
>
--
Gerald Muellan
Schelleingasse 2/11
1040 Vienna, Austria
0043 699 11772506
[EMAIL PROTECTED]
