-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.1.7-SNAPSHOT
-
Fix Version/s: 1.1.2
-
Component/s: None
-
Labels:None
-
Environment:tomahawk-sandbox-1.1.6-snapshot.jar
The stateChangedNotifier component will currently never look for a value binding for the confirmationMessage property.
I think there is something wrong in current source of StateChangedNotifier.java#getConfirmationMessage().
ValueBinding wont be evaluated because of property will always be set to default message:
private static final String DEFAULT_MESSAGE = "Are you sure?";
private String confirmationMessage = DEFAULT_MESSAGE;
public String getConfirmationMessage()
{ if (confirmationMessage != null) return confirmationMessage; ValueBinding vb = getValueBinding("confirmationMessage"); return (vb != null) ? _ComponentUtils.getStringValue(getFacesContext(), vb) : null; }Is this correct?
Greetings, bruno
- is a clone of
-
TOMAHAWK-219 stateChangedNotifier does not use ValueBinding for the confirmation message
-
- Closed
-