Thanks Howard... i wondered if this one would get your attention and glad I can
move onward.
maybe i am getting old in my age but I got 5 years of hard C, 10 years of C++,
12 years of JAVA and a boat load of front end to back end...
conceptual expression parsing and de-referencing caught me up a bit I guess...
and I have thought recently (as I have in the past with tap3 and tap4)... why
does tapestry have to be so hard... but I think it's just me
maybe I am asking too much for these semantics should be flagged too... and
articulated for the developer
anyway... thanks... in the end 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/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)
@Parameter(required = true, cache = true, defaultPrefix = "50")
private int itemsPerPage;
@BeginRender
public void beginRender()
{
//itemsPerPage = 50;
//tableColumns = 3;
}
org.apache.tapestry5.runtime.ComponentEventExceptionFailure
writing parameter 'value' of component
Home:gallerywidget.itemsperpageselect: Failure writing parameter
'itemsPerPage' of component Home:gallerywidget: Binding
org.apache.tapestry5.internal.services.AttributeExpansionBinding@3e963f38
is read-only.
here are some sources... to possbly indicate the issue but I cannot spot why.
Any ideas ? I would think that the annotations provided are sufficient? Also if
I try to set a value to this parameter within the component I receive the same
thing...
HOME.TML
...
<t:form t:id="galleryForm" t:name="galleryForm" clientValidation="true">
<t:errors/>
<t:Gallery t:id="GalleryWidget"
collection="${collection}"
itemsPerPage="${itemsPerPage}"
tableColumns="${tableColumns}"
cursor="${cursor}"
/>
</t:form>
</t:layout>
