answering myself: yes, it could be...
Ron Piterman wrote:
I would tip that the problem is somewhere else -
not in the binding / calling the method -
could it be that you define an abstract property in the .jwc/.page
(which will make tapestry override your method implementation...) ?
Cheers,
Ron
Matt Raible wrote:
In Tapestry 3, I had methods in my pages like the following:
public List getUserRoles() {
List selectedRoles = new ArrayList(getUser().getRoles().size());
for (Iterator it = getUser().getRoles().iterator();
(it != null) && it.hasNext();) {
Role role = (Role) it.next();
selectedRoles.add(role.getName());
}
return selectedRoles;
}
I then called them in my .page specification using:
<component id="userRoles" type="contrib:MultiplePropertySelection">
<binding name="model" expression="availableRoles"/>
<binding name="selectedList" expression="userRoles"/>
<binding name="renderer"
expression="beans.multipleCheckboxRenderer"/>
</component>
Hower, it doesn't seem that this is possible with Tapestry 4 - even if
I use expression="ognl:userRoles". I have to add an abstract
getUserRoles() method and put the above logic in my pageBeginRender()
method.
Is this "as designed" or am I doing something wrong?
Thanks,
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
