Hi,
i think this is the case because the {0}, {1} values are in request
scope only. Try to store the values somewhere, e.g. t:saveState with
model value bindings.
cheers,
Gerald
On 7/12/07, Michał 'Gandalf' Stawicki <[EMAIL PROTECTED]> wrote:
Disregard what i said. It's something strange with detailFormat. {1}
is empty, and {0} is alaways id: message
here's my code:
<t:outputLabel
for="password1"
value="#{m.password1}" />
<t:inputText
id="password1"
value="#{registerUser.password1}"
onkeyup="submit(this);"
valueChangeListener="#{registerUser.password1Changed}">
<f:validateLength minimum="6" />
</t:inputText>
<s:pprPanelGroup
partialTriggers="mainForm:password1,mainForm:password2"
id="pprPassword2">
<t:message
id="password2Msg"
for="password1"
showSummary="false"
showDetail="true"
forceSpan="true"
replaceIdWithLabel="true"/>
</s:pprPanelGroup>
On 12/07/07, Michał 'Gandalf' Stawicki <[EMAIL PROTECTED]> wrote:
> If I put a t:message inside s:pprPanelGroup and it get's displayed as
> partial rendering, then messages' atttributes are all ignored, and
> defaults are used. If it is displayed after full page submit
> everything works fine. Is there any solution for this behaviour?
>
> regards,
>
> --
> Michał Stawicki
>
> [EMAIL PROTECTED]
> http://stawicki.jasliska.pl
>
--
Michał Stawicki
[EMAIL PROTECTED]
http://stawicki.jasliska.pl
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
