The x:messages stuff is not usable for you, right?

regards,

Martin

On 8/11/05, Matthew Pease <[EMAIL PROTECTED]> wrote:
OK, I'll do that.

In the meantime, does anyone know of a way to do this sort of
validation error reporting?  Is there a control?  I've looked at JSF &
now Myfaces.. anyone else making JSF components?

The type where at the top of the page I can show messages like:

Name is required.
Call Request must be a number between 1 & 500.
...

Thank you-
Matt

On 8/10/05, Martin Marinschek < [EMAIL PROTECTED]> wrote:
> there was the same 'problem' with the output label before, than we fixed it,
> and obviously forgot about doing it for the message as well.
>
>  can you open a jira issue?
>
>  thx,
>
>  Martin
>
>
> On 8/11/05, Matthew Pease <[EMAIL PROTECTED]> wrote:
> > Hi..
> >
> >   Using Weblogic 8.1..
> >
> >
> >   Basically, I'd like to use <x:message>  on the top of the page &
> > have the fields that I'm validating be stuffed away lower in
> > panelGrids.
> >
> > I have:
> >
> > <x:message for="">> > <h:outputLabel for="" rendered="false" value="Name"/>
> >
> > near the top.
> >
> > and
> >
> >     <h:inputText id="phoneExt" required="true"   ...
> >
> > further below buried in few <h:panelGrid>s
> >
> > I get the following exception when trying to render the page:
> >
> > javax.faces.FacesException: Could not render Message. Unable to find
> > component 'phoneExt'
> >
> >
> > This seems to be a myfaces bug, because if I remove the <x:message
> > for="" and switch on rendering of the <h:outputLabel,  the
> > outputLabel renders itself & doesn't complain about not finding a
> > matching phoneExt.      It seems that when <x:message>  tries the
> > same, it dies complaining that it can't find the matching label.
> >
> >
> >
> > Any ideas?
> >
> > Thank you-
> > Matt
> >
>
>

Reply via email to