You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Alexander Zynevich (JIRA)" <ji...@apache.org> on 2007/06/21 19:09:33 UTC
[jira] Updated: (GERONIMO-3253) Сalculation of ${} EL expression of seconf level, like ${a.b} cause null value
[ https://issues.apache.org/jira/browse/GERONIMO-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Zynevich updated GERONIMO-3253:
-----------------------------------------
Description:
I have simple JSP snip:
\*<h:outputText id="cll1" value="#{customerDetailsBean}" />\*<br/>
\*<h:outputText id="cll2" value="#{customerDetailsBean.customer}" />\*<br/>
\*${customerDetailsBean}\*<br/>
\*${customerDetailsBean.customer}\*<br/>
it renders to:
\*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
\*com.mycomp.data.customer.Customer@149e361\*
\*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
\*\*
How it may be? I would expect:
\*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
\*com.mycomp.data.customer.Customer@149e361\*
\*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
\*com.mycomp.data.customer.Customer@149e361\*
The only special about my code is that I use Spring 2 and have
<variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver>
but this customerDetailsBean is defined in faces-config.xml and in session scope:
<managed-bean>
<description>Backing bean for customer_details.jsp</description>
<managed-bean-name>customerDetailsBean</managed-bean-name>
<managed-bean-class>com.mycomp.viewbeans.cust.CustomerDetailsBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>customerManager</property-name>
<value>#{customerManager}</value>
</managed-property>
<managed-property>
<property-name>specialsManager</property-name>
<value>#{specialsManager}</value>
</managed-property>
</managed-bean>
again bug in Tomcat EL engine, like https://issues.apache.org/jira/browse/MYFACES-1656 ?
actually I found this bug because <c:when test='${customerDetailsBean.customer != null}'> is not fired :(
was:
I have simple JSP snip:
\*<h:outputText id="cll1" value="#{customerDetailsBean}" />\*<br/>
\*<h:outputText id="cll2" value="#{customerDetailsBean.customer}" />\*<br/>
\*${customerDetailsBean}\*<br/>
\*${customerDetailsBean.customer}\*<br/>
it renders to:
\*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
\*com.mycomp.data.customer.Customer@149e361\*
\*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
\*\*
How it may be? I would expect:
\*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
\*com.mycomp.data.customer.Customer@149e361\*
\*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
\*com.mycomp.data.customer.Customer@149e361\*
The only special about my code is that I use Spring 2 and have
<variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver>
but this customerDetailsBean is defined in faces-config.xml and in session scope:
<managed-bean>
<description>Backing bean for customer_details.jsp</description>
<managed-bean-name>customerDetailsBean</managed-bean-name>
<managed-bean-class>com.mycomp.viewbeans.cust.CustomerDetailsBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>customerManager</property-name>
<value>#{customerManager}</value>
</managed-property>
<managed-property>
<property-name>specialsManager</property-name>
<value>#{specialsManager}</value>
</managed-property>
</managed-bean>
again bug in Tomcat EL engine, like https://issues.apache.org/jira/browse/MYFACES-1656 ?
Summary: Сalculation of ${} EL expression of seconf level, like ${a.b} cause null value (was: Bug in calculation of ${} EL expression)
> Сalculation of ${} EL expression of seconf level, like ${a.b} cause null value
> ------------------------------------------------------------------------------
>
> Key: GERONIMO-3253
> URL: https://issues.apache.org/jira/browse/GERONIMO-3253
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M6
> Environment: geronimo-tomcat6-jee5-2.0-M6-rc1
> Reporter: Alexander Zynevich
>
> I have simple JSP snip:
> \*<h:outputText id="cll1" value="#{customerDetailsBean}" />\*<br/>
> \*<h:outputText id="cll2" value="#{customerDetailsBean.customer}" />\*<br/>
> \*${customerDetailsBean}\*<br/>
> \*${customerDetailsBean.customer}\*<br/>
> it renders to:
> \*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
> \*com.mycomp.data.customer.Customer@149e361\*
> \*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
> \*\*
> How it may be? I would expect:
> \*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
> \*com.mycomp.data.customer.Customer@149e361\*
> \*com.mycomp.viewbeans.cust.CustomerDetailsBean@15c50e9\*
> \*com.mycomp.data.customer.Customer@149e361\*
> The only special about my code is that I use Spring 2 and have
> <variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver>
> but this customerDetailsBean is defined in faces-config.xml and in session scope:
> <managed-bean>
> <description>Backing bean for customer_details.jsp</description>
> <managed-bean-name>customerDetailsBean</managed-bean-name>
> <managed-bean-class>com.mycomp.viewbeans.cust.CustomerDetailsBean</managed-bean-class>
> <managed-bean-scope>session</managed-bean-scope>
> <managed-property>
> <property-name>customerManager</property-name>
> <value>#{customerManager}</value>
> </managed-property>
> <managed-property>
> <property-name>specialsManager</property-name>
> <value>#{specialsManager}</value>
> </managed-property>
> </managed-bean>
> again bug in Tomcat EL engine, like https://issues.apache.org/jira/browse/MYFACES-1656 ?
> actually I found this bug because <c:when test='${customerDetailsBean.customer != null}'> is not fired :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.