thanks simon,
the label-parameter looked like a solution.
but it cannot resolve my resource-bundles.
if i set label="#{label.username}" the message start with ": ..."
when label="Username" it looks fine.
so it´s not the solution i´ve looked for.
i can´t believe that such a behavior is wanted from myfaces.
Simon Kitching wrote:
>
> While testing something else, I took a moment to check how Sun's Mojarra
> handles required-messages. It also inserts the clientId (ie *with* the
> form/subview prefix). Therefore myfaces 1.2.x and mojarra currently work
> the same. I think it unlikely that MyFaces would accept a patch to
> change its default behaviour to something different from Mojarra, although
> (a) you could try; the decision is not mine to make, and
> (b) you could create and offer a patch to make the behaviour configurable
>
> Re the "label" attribute I mentioned below: it looks like JSF also added
> this optional attribute to customise the {0} parameter, eg
> <h:input id="someProgrammerId" label="someUserLabel" required="true"../>
> will generate whatever generic "required" message is configured, but
> with {0} set to "someUserLabel". This feature still requires setting
> this on each component though.
>
> Regards,
> Simon
>
--
View this message in context:
http://www.nabble.com/h%3Amessages-validation-messages-without-formid---tp20010322p20147227.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
