Yea you are right I did what you suggested and the setters are called.
First thing that happens is that it calls the coercion that I have created.
Coercion<String, PopupItem> coercion3 = new Coercion<String,
PopupItem>() {
public PopupItem coerce(String input) {
return new PopupItem(new Long(2), input, input);
}
};
configuration.add(new CoercionTuple<String, PopupItem>(String.class,
PopupItem.class, coercion3));
It is obvious that this is wrong but I am not sure how to create a good
coercion. The input is something like. com.components.PopupItem@1us75. How
do I convert this into the actual PopupItem?
After this it calls the setter in the popup class and sets the PopupItem
value that was passed form the coercion. After that it calls the setter for
the PopupItem that was just passed and sets its value into what ever I have
typed into the filed. But for some reason this new value even do it is
stored can not be access from the page that is holding this component.
In the page Index I have create a list with one PopupItem and passed that
list to the component. But when the value is set it is not passed back to
the list in the Index page.
Any more ideas????
oh and thx for help please don't stop :D
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Form-elements-inside-a-component-tp4749774p4775720.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
