Working with the Portal Error Stack in PL/SQL

Question

Hi,
In brief, this is a question about the persistence of errors on the stack, as they appear to disappear without warning. Any help would be appreciated, if you'd like background, read on.
I'm writing PL/SQL web applications and as ever one of the required tasks is user validation.
I have a form on a page which submits directly to a stored procedure. If the validation within the proc is ok, the value(s) get inserted into a DB table and the user gets directed to another Portal page. If there is a user input error then the code reloads the original page (via redirect) with the necessary errors displayed.
I used to use the Session storage to hold any error messages and then check to see if any errors existed at the point of page redirection, and this worked fine.
Now that I figure that I should do the job properly and use Portals' error stack, everything falls over!
It would seem that between moving from one page to another any values held in the stack are lost, yet I know they are definitely getting put there in the first place as I can view them, as long as I don't redirect the Portal page.
Any ideas??
Thanks in advance.
Dan

Answer 1

1.) Create a hidden item on your page.
2.) In your Page Rendering PL/SQL Process add logic which assigns 'EDIT' or 'NO_EDIT' to the hidden item.
3.) Create a "Message" HTML region which conditionally displays based of the value of your hidden item being 'NO_EDIT'.
4.) Make your edit field conditionally Read Only based on the value of your hidden item being 'NO_EDIT'.
There may be an easier way but I got this to work
Mike