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 back to the dynamic component issues discussed at length on the list? It seems that none of the suggested work arounds really work in your situation where Tapestry has been integrated into work flow? Tapestry has a bias towards the stateless app, which is where this becomes difficult, because form Type A instance b is related to *but not the same as* form type A instance a i.e. has additional properties that enable it to be able to pick up errors created in another instance. You could say they are not really of the same type, because of this, but even as you propose to create Ba instead of Aa, the question is how? Why isn't persisting this data to a db which B would pick up a solution here? Adam
On 24/04/06, gaz jones <[EMAIL PROTECTED]> wrote: > > hi, > > i currently have a situation where i need to display the errors that exist > on a prepopulated form _before_ the form is submitted. > > basically there are a group of applications that all share the same form > components - one of the applications allows users to fill in a form > online. > if the user gets stuck and have problems getting their data to pass > validation then they call a helpline, which is answered by people using > another application that uses the same common form components to show the > form to the call centre operator. > when the call centre operator looks at the form, they want to be able to > view all of the validation errors immediately when the form first loads > up. > > we have a custom validation engine which parses the object model and puts > any errors into properties on the object model objects, then we have > hacked > tapestry a little bit by creating a class which parses the object model > and > moves these messages from the om into tapestry's fieldtracking. this all > occurs in the rewind phase normally - and works fine. > > to achieve the effect we want, i have tried validating the object model in > the render phase (works fine), but then the class that copies the values > into the fieldtracking fails on render because the fieldtracking is all > null > - this only seems to get set up during the rewind phase of a form. so im a > bit stuck... its like i need a rewind to occur where i can do validation > on > the page im moving _to_ rather than the page im on... and then display the > existing errors when i get there... *sob* > > i am basically wondering if anyone has had a similar requirement in the > past > and has been able to achieve this effect? it seems like a simple > requirement > - perhaps i am missing something obvious O_o > > any help appreciated, cheers > gaz > >
