Ok, I got pre-empted but am back. I understand the flames from Andy and I do
not mind being torched. I can handle the flames and eventually come out
contributing to the drive of this framework in a fruitful user capacity. It's
not you guys fault and I have high regard for your priest stewardship to
tapestry and tacos/dojo. I will try to clean up my posts.
I originally used Integer inside my list
private static final Integer[] tableSizeIntegerOptions = new Integer[]
{ new Integer("1"), new Integer("2"), new Integer("3"), new Integer("4"), new
Integer("5"), new Integer("10"),
new Integer("25"), new Integer("50"), new Integer("100"), new Integer("500"),
new Integer("1000"),
new Integer("2500"), new Integer("5000"), new Integer("10000"), new
Integer("25000"), new Integer("50000") };
And OGNL-2.7.1 appears to operate arithmetic on the string property seamlessly.
I will convert my property to int and see what that yeilds... but I am
wondering why a strihg property would be implicitly interpretted as static.
Ok, I will take a closer look and yeild results.
Thanks for your patience.
Best regards
Ken in nashua
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: PropertySelection binding bug
T-4.1.3 ?Date: Wed, 28 Nov 2007 17:46:43 -0500
Jesse, I regard the repsonse. But I need to update the binding on subsequent. I
cannot update a static binding. I specified a valif component property as such
<component id="tableSizeSelect" type="PropertySelection">
<binding name="model" value="tableSizeModel"/>
<binding name="onchange"
value="literal:tapestry.form.submit(this.form)"/></component> and
@Persist("session")
@InitialValue("literal:2")
public abstract String getTableSize();public abstract void setTableSize(String
tableSize); and
<span jwcid="@Insert" value="Table Size"/><select jwcid="tableSizeSelect"
value="ognl:tableSize"/> The binding still gets whacked on submit. Event
listeners also do not get called.
@EventListener(events = { "onChange" }, targets = { "tableSizeSelect" },
submitForm = "galleryForm", async = false)
public void tableChangeListener(IRequestCycle cycle)
{} Now I believe I do not have to muck with pumping properties into my home
page to get this to work. The only other route is a component cached parameter
method which fails also. Has the samples that operate these components been
checked recently? I am hoping to see this thru.Best regards Ken in
nashua________________________________From: [EMAIL PROTECTED]: [EMAIL
PROTECTED]: RE: PropertySelection binding bug T-4.1.3 ?Date: Wed, 28 Nov 2007
15:10:19 -0500The questions is why does the code believe it has no bindings?I
have thrown property bindings, page bindings and parameter bindings at this.
Nothing sticks?________________________________You keep typing, we keep giving.
Download Messenger and join the i’m Initiative now. Join
in!<http://im.live.com/messenger/im/home/?source=CRM_WL_joinnow>
Your smile counts. The more smiles you share, the more we donate. Join in!
_________________________________________________________________
You keep typing, we keep giving. Download Messenger and join the i’m Initiative
now.
http://im.live.com/messenger/im/home/?source=TAGLM
