Re: How to avoid contribution to TypeCoercer in my case.

2009-11-10 Thread sandeepraj singh
Hi Inge The solution you provide works fine. But to a lesser mortal like me, the description of ITERATION in LoopFormState is a bit difficult /** * Only enough state to iterate over the source values is stored. When the Form is submitted, the Loop will re-acquire its source and iterate over i

Re: How to avoid contribution to TypeCoercer in my case.

2009-11-09 Thread Inge Solvoll
I struggled a lot with loops in forms, I still do to tell you the truth. See this page in jumpstart, it helped me a lot. If you use formstate="ITERATION", it won't ask you for a coercer. Formstate and loops is one of the harder concepts of T5 in my opinion, it doesn't seem logical to me so I don't

Re: How to avoid contribution to TypeCoercer in my case.

2009-11-09 Thread sandeepraj singh
Hi Niclas, Sorry for a delayed response. The solution you suggest is not working. My Original Code is like below ... myDataObject.myOtherContent As per your suggestion i changed it to ... myDataObject.myOtherContent also tried with values of Volatile = "true" etc It still asks for co-er

Re: How to avoid contribution to TypeCoercer in my case.

2009-10-30 Thread Niclas.Meier
Hi sandeep, The effekt that occurs is, that tapestry tries to provide a loop context/state for the enclosing form. You need this if you have any fields in your loop. If you don¹t want/need to provide a context you may mark the loop as voliatile. This looks like: ... Otherwise you'll have to