Uploaded image for project: 'Geronimo'
  1. Geronimo
  2. GERONIMO-3253

Сalculation of ${} EL expression of second level, like ${a.b} cause null value

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.0-M6
    • None
    • web
    • Security Level: public (Regular issues)
    • None
    • geronimo-tomcat6-jee5-2.0-M6-rc1

    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

      Attachments

        1. eltest.war
          6 kB
          Alexander Zynevich
        2. eltest.zip
          8 kB
          Alexander Zynevich

        Issue Links

          Activity

            People

              Unassigned Unassigned
              zynevich Alexander Zynevich
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: