We are using MyFaces 1.1.5-SNAPSHOT (an 11/23 cut I think) with
Facelets. In a page we have the following code that works just fine:
<h:commandButton id="editFilter"
action="${filtersBean.prepareEditScreen}" value="Edit Filter">
<t:updateActionListener property="#{filtersBean.currentFilterId}"
value="#{reportingBean.reportSelections.filter}" />
</h:commandButton>
In the above code "filtersBean" and "reportingBean" are managed-bean's
both in session scope. "filtersBean.currentFilterId" is a property of
type java.lang.Integer as is "reportingBean.reportSelections.filter".
Again, that works as expected.
Later in the same page we have this code that does not work:
<h:commandButton id="createUserSetting"
action="${userSettingsBean.createUserSetting}" value="Create Setting">
<t:updateActionListener property="#{userSettingsBean.qType}"
value="#{reportingBean.qType}" />
</h:commandButton>
The "qType" property on both reportingBean and userSettingsBean are
Strings. Again, reportingBean is in session scope, but
userSettingsBean is a managed-bean in request scope. We get the
following exception:
SEVERE: Error Rendering View[/reporting.xhtml]
javax.faces.el.PropertyNotFoundException: /reporting.xhtml @304,85
value="#{reportingBean.qType}": Bean:
com.mktinsights.cee.web.reporting.ReportingBean, property: qType
at
com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:58)
at javax.faces.component.UIParameter.getValue(UIParameter.java:68)
at
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.addChildParameters(HtmlLinkRendererBase.java:294)
at
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart(HtmlLinkRendererBase.java:222)
at
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderCommandLinkStart(HtmlLinkRendererBase.java:157)
at
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.encodeBegin(HtmlLinkRendererBase.java:87)
at
javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:307)
Changing the scope of userSettingsBean to session does not seem to
have any effect. It appears I have two instances of a very similar
pattern and one works while the other doesn't. Any idea why?
Thanks,
Greg
