[ 
https://issues.apache.org/jira/browse/GERONIMO-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Zynevich updated GERONIMO-3253:
-----------------------------------------

    Attachment: eltest.war

I add a simplest test application (no Spring, no JEBs, just faces-config.xml, 
web.xml, 2 classes and 2 jsps).
The print.jsp has:
    <f:view>
    <h:form id="myform" >
    <b>Using sharp-el</b>: <br/>
    \*<h:outputText id="cll1" value="#{customerDetailsBean}" />\*<br/>
    \*<h:outputText id="cll2" value="#{customerDetailsBean.customer}" />\*<br/>
    <b>Using dollar-el</b>: <br/>
    \*${customerDetailsBean}\*<br/>
    \*${customerDetailsBean.customer}\*<br/>
    <b>Classical "servlet" style</b>: <br/>
    \*<% if (session.getAttribute("customerDetailsBean") != null) {%><%= 
session.getAttribute("customerDetailsBean") %><% } %>\*<br/>
    \*<% if (session.getAttribute("customerDetailsBean") != null) {%><%= 
((eltest.CustomerDetailsBean)session.getAttribute("customerDetailsBean")).getCustomer()
 %><% } %>\*<br/>
    </h:form>
    </f:view>

WHICH renders:
    *Using sharp-el:* 
    \*CustomerDetailsBean: { customer: Customer {frstName: Alex , lastName: 
Zynevich, id: 1979}}\*
    \*Customer {frstName: Alex , lastName: Zynevich, id: 1979}\*
    *Using dollar-el:* 
    \*CustomerDetailsBean: { customer: Customer {frstName: Alex , lastName: 
Zynevich, id: 1979}}\*
    \*\*
    *Classical "servlet" style:* 
    \*CustomerDetailsBean: { customer: Customer {frstName: Alex , lastName: 
Zynevich, id: 1979}}\*
    \*Customer {frstName: Alex , lastName: Zynevich, id: 1979}\*

i think it is not Geronimo's problem -- looks like MyFaces' one.

> Сalculation of ${} EL expression of second 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) 
>          Components: web
>    Affects Versions: 2.0-M6
>         Environment: geronimo-tomcat6-jee5-2.0-M6-rc1
>            Reporter: Alexander Zynevich
>         Attachments: eltest.war
>
>
> 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:
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> \*\*
> How it may be? I would expect:
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> 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.

Reply via email to