-
1. Re: Why does disabled/rendered break A4j:commandLink
ilya40umov Jan 5, 2011 12:49 AM (in response to jovincen)You need to extend a life time of your bean. It should live at least until user works with the same page.
Try a4j:keepAlive tag. Or make your bean page(JSF 2.0 already supports this) or session scoped.
-
2. Re: Why does disabled/rendered break A4j:commandLink
jovincen Jan 5, 2011 8:48 AM (in response to ilya40umov)eep.. is that the only way to do it?
I'd prefer to kill off the server beans...
-
3. Re: Why does disabled/rendered break A4j:commandLink
ilya40umov Jan 5, 2011 9:00 AM (in response to jovincen)1) I guess you can save only this flag into session. You shoud define it separetly in sessionScope with some name #{someFlag} and then use managed-property to inject in into bean
<managed-property><property-name>updateDeviceBean</property-name><value>#{updateDeviceBean}</value></managed-property><managed-property>
<property-name>someFlag</property-name>
<value>#{someFlag}</value>
</managed-property>
2) I guess you can always find a workaround and try to use Filter/PhaseListener in order to set this option before JSF will reread it from your request scoped bean. But it looks like a bad way out for me.