I was very excited to find 'enabledOnUserRole' attribute on all tomahawk input fields, b/c they do exactly what I need in my app - disable fields based on user role. Unfortunately, using 'enabledOnUserRole' has a side effect that makes it useless to me. Unless I am missing something...
The page displays correctly, but when the page is submitted, since some input fields are disabled, the browser doesn't send their values to the server. Not only does this fire all of the change listeners attached to the disabled fields, but more importantly, the model is updated with nulls where there used to be values. Is this the expected behavior? Is there a way around this? It seems that having 'enabledOnUserRole' is not that useful if it's going to overwrite all of your model data with nulls... -- View this message in context: http://www.nabble.com/Problem-with-enabledOnUserRole-t1763951.html#a4800751 Sent from the MyFaces - Users forum at Nabble.com.
