Re: Dynamic Working with Tapestry...

2006-11-29 Thread Skorpien126
Ron you do a great Job here!!! Now I understand a little bit more how the delegate works. It could be compared with "ExceptionHandler" which catchs "Exceptions" thrown by the included subcomponents. (unimportant how deep the hierachy is). But Now I have another Prob. I have multible Textareas in

Re: Dynamic Working with Tapestry...

2006-11-26 Thread Ron Piterman
Tapestry uses for validation the ValidationDelegate - I would recomment you stick to it, it will make your life much easier, and it is one of tapestry's most powerfull features: You can use validators on each of your fields, and that doesn't mean they have to be preconfigured - you can use a d

Re: Dynamic Working with Tapestry...

2006-11-26 Thread Skorpien126
Thats not exactly the situation... here a descreption depending on your code snippet. (includes Validation and further function) (includes Validation and further function) the Problem is that I don´t know how to check the Validation of each

Re: Dynamic Working with Tapestry...

2006-11-24 Thread Ron Piterman
If I get this right, there is some kind of iteration over objects inside the form component. When the form is submitted, the iteration will be performed again, this one updating the values. then you add an "action" binding to the submit, and persist the whole list of obejcts which were updated:

Re: Dynamic Working with Tapestry...

2006-11-24 Thread Skorpien126
I´m not sure I´ve I understand you in the right way. Updating one Component is not the problem, I stillt tried taht and it works.. I want that my ContainerElement includes the "@Form" and in the Form tag the dynamic Number of Components is included. So the ConatinerElement have to take care of bi

Re: Dynamic Working with Tapestry...

2006-11-24 Thread Ron Piterman
There are some approaches to that problem, one approach would be to use the parameter binding for that: The component gets a paraemter from its container, and is responsible to update the parameter. Say you have a property on your page/container component: public Data getData() {...} public