On 2/14/06, Jason Vincent <[EMAIL PROTECTED]> wrote:
>
> ok... I got it to show the messages...
>
> I did what you suggested and moved the <h:messages> to the end of my
> page - THANKS!  But the method to convert my ErrorEvents into
> FacesMessages still needed to be called.  So I made it return true and
> set it as the "render" attribute for the messages tag. AHHH!
> It worked, but ewwwww. :)
>
> I could change my design so that the FacesMessages are created
> immediately when the events are added to the collecor.  That would
> eliminate the need for the render attribute.  BUT, I'll need to beg
> for forgiveness from my UI designers when I tell them that the
> <h:messages> tag MUST be at the end of the page.
>
> I guess the original intent of the FacesMessages was to be used during
> the Validation phase. Hmmm.
> Is it a sign of mis-use of the JSF framework if my getter methods in
> the render phase can produce FacesMessages?


I would say yes, that's a misuse.  If your messages represent the generic
concept of validation errors, you should strive to have those messages
created during the Process Validations phase (if it's things that validators
should normally catch), or Invoke Application phase (if its business rule
enforcement like "you cannot claim that user id because it belongs to
someone else').

HMMM.... Perhaps I could override/extend the responseComplete method
> to do my custom stuff first, and then call super.responseComplete???
> Is this a good approach or even possible or even the right method to
> override? It seems like a path to the dark side.


Yes ;-).

Thanks for the help.
> Jason


Craig


On 2/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > On 2/14/06, Jason Vincent <[EMAIL PROTECTED]> wrote:
> > >
> > > Hmm... I guess a phase listener wouldn't work for me. From what you
> > > say, it appears that the outcome of the phase is already determined
> > > before the "afterPhase" listener is triggered.
> > >
> > > Is there a another place for me to plug into the steps taken "during"
> > > a phase, that is, before the final steps in the phase are completed?
> >
> >
> > I don't see how that would really help you ... what you seem to be
> needing
> > is that the messages get generated before the <h:messages> component
> itself
> > is rendered.
> >
> > Or at least, I just need the FacesMessages to not get processed until
> > > the last step of the render phase.
> >
> >
> > Put your <h:messages> component last???
> >
> > Thanks,
> > > Jason
> >
> >
> > Craig
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to