It's probably something from the spec, but I don't know why.
On 8/17/06, Frank Russo <[EMAIL PROTECTED]> wrote:
You're right. It wasn't the validation phase. It was update model. Why is it that instead of throwing an exception, a message is created? I would only expect messages from the validation phase, so they can be shown on the screen. Is this an implementation detail or something from the spec? I guess I'll have to read the docs to get up to speed on the purpose of h:messages. Thanks for the input... Frank Russo Senior Developer FX Alliance, LLC -----Original Message----- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 16, 2006 4:25 PM To: MyFaces Discussion Subject: Re: General Lifecycle Question On 8/16/06, Frank Russo <[EMAIL PROTECTED]> wrote: > So, I made the mistake of not having an h:messages tag on my page. I > was referencing an attribute on an object in a list as part of a > datatable, that was failing. The only thing I was noticing was that > the lifecycle was skipping the invoke application phase. Once I added > the h:messages tag, I saw the issue, but what I'm wondering is that > shouldn't the lifecycle also have skipped the update model values > phase as well? I thought if process validations phase fails, then the lifecycle jumps right to render response. Sounds right to me, but was it the validation phase that was failing? It sounds like it would be the update model phase that's failing since the path to the model was wrong.
