RE: why read ony ComponentEventException

2011-09-19 Thread Ken in Nashua
tapestry is worth it and I could not think of developing with anything else as extensible and flexible - cheers From: kcola...@live.com To: users@tapestry.apache.org Subject: why read ony ComponentEventException Date: Sun, 18 Sep 2011 16:39:21 -0400 Folks, I have a page feeding read

why read ony ComponentEventException

2011-09-18 Thread Ken in Nashua
Folks, I have a page feeding read/write property Home.JAVA @Property(read = true, write = true)// no getter/setter needed @Persist(session) private int itemsPerPage; to a component parameter Gallery.JAVA @Property(read = true, write = true)

Re: why read ony ComponentEventException

2011-09-18 Thread Howard Lewis Ship
${...} doesn't do what you think it does. It specifically extracts the expression and converts it to a String, and the expression is read-only. Bind it like this: itemsPerPage=itemsPerPage this binds the component parameter field directly to the containing page's property, so it's