I'm seeing this same issue with MyFaces 1.2.0 and Facelets 1.1.13. I tried
the exclusion selection below and that doesn't solve anything. I've had a
discussion with the Jetty folks about commons-el in Jetty 6.1.5 and they've
proven it's not present.

http://www.nabble.com/Is-it-possible-to-exclude-commons-el-as-a-dependency-with-the-maven-jetty-plugin--tf4348944.html#a12407203

The code below is in a Facelets page and seems to be causing an issue. If I
create an empty errors list and put it in my request even when there are no
errors, things work fine.

Everything works fine on Tomcat 6, this seems to be a Jetty 6.1.5 (Maven
Plugin) + MyFaces 1.2.0 issue.

Any ideas how to fix?

Thanks,

Matt

<%-- Error Messages --%>
<c:if test="${not empty errors}">
    <div class="error" id="errorMessages">
        <c:forEach var="error" items="${errors}">
             <c:url value= "
                alt="<fmt:message key="icon.warning"/>" class="icon" />
            <c:out value="${error}" escapeXml="false"/><br />
        </c:forEach>
    </div>
    <c:remove var="errors" scope="session"/>
</c:if>

<%-- Success Messages --%>
<c:if test="${not empty messages}">
    <div class="message" id="successMessages">
        <c:forEach var="msg" items="${messages}">
             <c:url value= "
                alt="<fmt:message key="icon.information"/>" class="icon" />
            <c:out value="${msg}" escapeXml="false"/><br />
        </c:forEach>
    </div>
    <c:remove var="messages" scope="session"/>
</c:if>



Bruno Aranda wrote:
> 
> Ok, found the problem. The issue is with tomahawk, that depends on
> commons-el. Be sure that you don't have this dependency (commons-el)
> in the classpath. If using maven, do this for tomahawk and the
> sandbox:
> 
> <dependency>
>             <groupId>org.apache.myfaces.tomahawk</groupId>
>             <artifactId>tomahawk</artifactId>
>             <scope>compile</scope>
>             <exclusions>
>                 <exclusion>
>                     <groupId>commons-el</groupId>
>                     <artifactId>commons-el</artifactId>
>                 </exclusion>
>             </exclusions>
>         </dependency>
> 
> Hope that helps,
> 
> Bruno
> 
> On 05/07/07, Bruno Aranda <[EMAIL PROTECTED]> wrote:
>> I cannot reproduce this in the current12/test-webapp, so I guess it is
>> a configuration issue whith the EL dependencies,
>>
>> Bruno
>>
>> On 05/07/07, Bruno Aranda <[EMAIL PROTECTED]> wrote:
>> > though it seems to be a problem with jetty having a dependency on
>> > commons-el 1.0 ?
>> >
>> > Bruno
>> >
>> > On 05/07/07, Bruno Aranda <[EMAIL PROTECTED]> wrote:
>> > > I can confirm this issue. Could you add it to JIRA please?
>> > >
>> > > Cheers,
>> > >
>> > > Bruno
>> > >
>> > > On 28/06/07, noah <[EMAIL PROTECTED]> wrote:
>> > > > With the 1.2.0-SNAPSHOT for today
>> > > >
>> > > > <%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h" %>
>> > > > <%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f" %>
>> > > > <html>
>> > > >         <head>
>> > > >             <title>Null Test</title>
>> > > >         </head>
>> > > >         <body>
>> > > >         <f:view>
>> > > >             <h:outputText value="#{nullValue}" />
>> > > >         </f:view>
>> > > >         </body>
>> > > > </html>
>> > > >
>> > > > causes the exception shown below. 1.1.5 didn't have problem with
>> null
>> > > > expressions where there is only a base and the 1.2 RI doesn't
>> either.
>> > > > This is on Jetty.
>> > > >
>> > > > javax.el.PropertyNotFoundException: ELResolver cannot handle a null
>> > > > base Object with identifier 'nullValue'
>> > > >         at
>> com.sun.el.lang.ELSupport.throwUnhandled(ELSupport.java:52)
>> > > >         at
>> com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:75)
>> > > >         at
>> com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:195)
>> > > >         at
>> javax.faces.component.UIOutput.getValue(UIOutput.java:68)
>> > > >         at
>> org.apache.myfaces.shared_impl.renderkit.RendererUtils.getStringValue(RendererUtils.java:241)
>> > > >         at
>> org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.renderOutput(HtmlTextRendererBase.java:71)
>> > > >         at
>> org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.encodeEnd(HtmlTextRendererBase.java:58)
>> > > >         at
>> javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:539)
>> > > >         at
>> javax.faces.component.UIComponent.encodeAll(UIComponent.java:250)
>> > > >         at
>> javax.faces.component.UIComponent.encodeAll(UIComponent.java:247)
>> > > >         at
>> org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:308)
>> > > >         at
>> com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:533)
>> > > >         at
>> org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
>> > > >         at
>> org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132)
>> > > >         at
>> javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
>> > > >         at
>> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>> > > >         at
>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)
>> > > >         at
>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>> > > >         at
>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>> > > >         at
>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
>> > > >         at
>> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
>> > > >         at
>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
>> > > >         at
>> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
>> > > >         at
>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
>> > > >         at org.mortbay.jetty.Server.handle(Server.java:295)
>> > > >         at
>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
>> > > >         at
>> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827)
>> > > >         at
>> org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511)
>> > > >         at
>> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210)
>> > > >         at
>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379)
>> > > >         at
>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361)
>> > > >         at
>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
>> > > >
>> > >
>> >
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/null-EL-expression---%22ELResolver-cannot-handle-a-null-base-Object-with-identifier-%27nullValue%27%22-tf3996691.html#a12663989
Sent from the MyFaces - Users mailing list archive at Nabble.com.

Reply via email to