Its a view of a register, but the first time the page is rendered tha page is a confirmation page (nothing is save in database), and this apge have a save button ( consulta.id == null), when the user save the register the same page is rendered and the conversation is ended... now i have a NEW button (consulta.id != null) that point to a blank form and so on...
The problem is that i my logic to show thats buttons is in the rendered attribute...
On 9/28/06, Mario Ivankovits <
[EMAIL PROTECTED]> wrote:
Hi Angelo!
> i think that's the problem , but i cannot make a solution... i think
> that t:saveState is conflict with Seam... and when the button is
> rendered the conversation is End, so when i press the button the
> consulta dont exist...
Yes, I think there should be no need for saveState with seam.
Do you mean, the conversation has been ended when the page is first
rendered, or will it be ended "on button press"?
In the second case, the conversation should end AFTER the action method, no?
Well, I don't know much about seam here. At least its how we did it in
our conversationTag.
But maybe you'll have better support in seam's forum.
Still, did you check the problem Matthias pointed out? - The space after
the action name ... that way no navigation takes place and JSF simply
reloads the page.
Ciao,
Mario
