You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Martino Piccinato (JIRA)" <de...@tapestry.apache.org> on 2007/08/09 02:16:59 UTC
[jira] Created: (TAPESTRY-1699) Dialog component crashing on its
most simple use (hidden parameter default value)
Dialog component crashing on its most simple use (hidden parameter default value)
---------------------------------------------------------------------------------
Key: TAPESTRY-1699
URL: https://issues.apache.org/jira/browse/TAPESTRY-1699
Project: Tapestry
Issue Type: Bug
Affects Versions: 4.1.2
Reporter: Martino Piccinato
Well this is a replacement for TAPESTRY-1682 that was opened due to my total misunderstanding of binding mechanism on default-value for parameters (sorry for that).
In fact the problem that lead me to that is that Dialog component as it is, used in its simplest form (opening and closing a dialog popup) will fail without overriding default binding for hidden parameter as calling hide()/show() methods will try to write on a invariant binding (the default "true" constant). I think this is a bug as default behaviour for a component should be to work as expected and default values shouldn't get in the way.
My proposal is then to remove defaul binding from parameter so to have it unbounded by default
<parameter name="hidden"/>
and add "direct" initialization of the parameter by default
public void finishLoad() {
super.finishLoad();
if (!isParameterBound("hidden")) {
setHidden(true);
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org