try changing string[] to CollectionString and see if this changes
anything, tapestry is probably able to coerce these values, isn't it?
Cheers,
Ron
Dan Adams wrote:
Someone here has an application where he's getting the following
exception:
Caused by:
This also sounds like an old bug that hit people only when caching was
disabled. It's been fixed starting with 4.1.1.
On 1/10/07, Ron Piterman [EMAIL PROTECTED] wrote:
try changing string[] to CollectionString and see if this changes
anything, tapestry is probably able to coerce these values,
