Matt,
You must be using jdk1.4 because for jdk1.5 and up, jasper does not require commons-el.
If in fact you are using jdk1.4 and therefore jsp-2.0, then you are actually using
jasper 5.5.15 from apache. I don't know whether those versions of myfaces etc are
supposed to work with jsp2.0, but if they are, then you might try and verify that
you get the same error when running under tomcat 5.5.15.
regards
Jan
mraible wrote:
> Actually, I spoke too soon - removing commons-el causes a
> NoClassDefFoundError. However, the following seems to work fine on Tomcat
> 6.0.14 (with MyFaces 1.2.0, Tomahawk 1.1.6 and Facelets 1.13):
>
> <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>
>
> Using maven-jetty-plugin 6.1.5, I get:
>
> Caused by: javax.faces.el.EvaluationException: ELResolver cannot handle a
> null base Object with identifier 'errors'
>
> Any ideas?
>
> Thanks,
>
> Matt
>
>
>
> mraible wrote:
>> I'm trying to solve the following issue and it appears that the
>> maven-jetty-plugin's dependency on commons-el is causing the problem.
>>
>>
http://tinyurl.com/2vq9rf>>
>> Is there any way to exclude it in my plugin's configuration? I'm using
>> version 6.1.5.
>>
>> Thanks,
>>
>> Matt
>>
>
--
Jan Bartel, Webtide LLC | janb@webtide.com |
http://www.webtide.com-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>
http://get.splunk.com/_______________________________________________
Jetty-support mailing list
Jetty-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support
