Adam,
Peristing the errir information could work - but we decided (and I suspect
this is the cause of the issue) to add it to the tapestry mechanisms.
Our problem boils down to we need to set page level errors the first time a
form is rendered. Which does not seem to be possible.
Thanks
Ben
On
Or maybe a fast in memory cache such as Prevayler - www.*prevayler*.org/
Or have I misunderstood?
Adam
On 25/04/06, adasal <[EMAIL PROTECTED]> wrote:
>
> hi gaz,
> this is an interesting problem. Because your project has moved from form
> centric to workflow centric this sort of thing turns up.
>
hi gaz,
this is an interesting problem. Because your project has moved from form
centric to workflow centric this sort of thing turns up.
I don't know the solution, but is it really Tapestry that should be
providing it, e.g. in terms of getting around its internal workings?
Doesn't this all come ba
