JSF中的错误不清楚

我正在使用Tomahawk进行演示文件上传。没关系，但在我的代码触发错误的一部分中，上次的代码运行正常。这是一个日志文件：

StandardWrapperValve[FacesServlet]：PWC1406:Servlet FacesServlet的Servlet.service引发异常com.sun.el.parser.ParseException:遇到。在第2行第37列。他期待着：。。。java:2309 at com.sun.el.parser.ELParser.ELParser.jj_consume_tokenELParser.java:2191 at com.sun.el.parser.ELParser.DotSuffixELParser.java:1094 at com.sun.el.parser.ELParser.valuesubfixelparser.java:1071 at com.sun.el.parser.ELParser.ELParser.ValueELParser.ValueELParser.java:1016 atjava:986在com.sun.el.parser.ELParser.ELParser.MultiplicationELParser.java:750在com.sun.el.parser.ELParser.MathELParser.java:670在com.sun.el.parser.ELParser.CompareELParser.java:482在com.sun.el.parser.ELParser.ELParser.EqualityELParser.java:376在com.sun.el.parser.ELParser.ELParser.AndELParser.java:320在com.sunjava:264在com.sun.el.parser.ELParser.ChoiceELParser.java:222在com.sun.el.parser.ELParser.ExpressionELParser.java:214在com.sun.el.parser.ELParser.delparser.DeferredExpressionELParser.java:152在com.sun.el.parser.ELParser.CompositeExpressionELParser.java:80在java:177在com.sun.el.lang.ExpressionBuilder.java:229在com.sun.el.lang.ExpressionBuilder.java:229在com.sun.el.lang.ExpressionBuilder.createValueExpressionBuilder.java:273在com.sun.el.ExpressionFactoryImpl.createValueExpressionFactoryImpl.java:98在com.sun.jsftemplating.component.ComponentUtil.resolveValueComponentUtil.java:608在com.sun.jsftemplating.layout.descriptors.handler.handler.handler.handler.getInputValueHandler.java:197在com.sun.jsftemplating.layout.descriptors.handler.HandlerContextImpl.getInputValueHandlerContextImpl.java:142在com.sun.jsftemplating.handlers.UtilHandlers.writeUtilHandlers.java:160位于sun.reflect.GeneratedMethodAccessor148.invokeUnknown源位于sun.reflect.DelegatingMethodAccessorImpl.invokedLegatingMethodAccessorImpl.java:43位于java.lang.reflect.Method.invokeMethod.java:601位于com.sun.jsftemplating.layout.descriptors.handler.handler.invokeHandler.java:442在com.sun.jsftemplating.layout.descriptors.LayoutElementBase.LayoutElementBase.java:420在com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlerSlayYoutElementbase.java:394在java:321在com.sun.jsftemplating.layout.descriptor.LayoutElementBase.encodeLayoutElementBase.java:321在com.sun.jsftemplating.LayoutDefinition.encodeLayoutDefinition.java:250在com.sun.jsftemplating.render.Templaterender.TemplateRenderer.encodeEndTemplateRenderer.java:139在javax.faces.component.UIComponentBase.encodeEndUIComponentBase.java:875在java:99位于com.sun.webui.jsf.renderkit.html.TableColumnRenderer.encodeChildrenTableColumnRenderer.java:188位于javax.faces.component.UIComponentBase.encodeChildrenUIComponentBase.java:845位于com.sun.webui.jsf.util.RenderingUtilities.RenderControlmentTrenderingUties.java:91位于com.sun.webui.jsf.renderkit.html.TableRowGroupRenderer.encodeChildrenTableRowGroupRenderer.java:199位于javax.faces.component.UIComponentBase.encodeChildrenUIComponentBase.java:845位于com.sun.webui.jsf.util.RenderingUtilities.renderComponentTrenderingUtilities.java:91位于com.sun.webui.jsf.renderkit.html.TableRenderer.encodeChildrenTableRenderer.java:168位于javax.faces.component.UIComponentBase.encodeChildrenUIComponentBase.java:845位于com.sun.jsftemplating.layout.descriptors.LayoutElementBase.encodeChildLayoutElementBase.java:551位于com.sun.jsftemplating.layout.descriptors.LayoutElementBase.encodeChildLayoutElementBase.java:555在com.sun.jsftemplating.layout.descriptors.LayoutElementBase.encodeChildLayoutElementBase.java:555在com.sun.jsftemplating.layout.descriptors.LayoutElementBase.encodeChildLayoutElementBase.java:555在com.sun.jsftemplating.layout.descriptors.LayoutElementBase.encodeChildLayoutElementBase.java:555在com.sun.jsftemplating.layout.descriptors.LayoutComponent.encodeLayoutComponent.java:243在com.sun.jsftemplating.layoutDescriptors.LayoutElementBase.encodeLayoutElementBase.java:348在com.sun.jsftemplating.layout.descriptors.LayoutDefinition.encodeLayoutDefinition.java:246在com.sun.jsftemplating.LayoutViewHandler.renderViewLayoutViewHandler.java:683在com.sun.faces.lifecycle.RenderResponsePhase.executeRenderResponsePhase.java:121在com.sun.faces.lifecycle.Phase.doPhasePhase.java:101在java:139位于javax.faces.webapp.FacesServlet.serviceFacesServlet.java:594位于org.apache.catalina.core.StandardWrapper.serviceStandardWrapper.java:1542位于org.apache.catalina.core.ApplicationFilterChain.internalDoFilterApplicationFilterChain.java:343位于org.apache.catalina.core.ApplicationFilterChain.doFilte java:233位于org.apache.catalina.core.ApplicationFilterChain.internalDoFilterApplicationFilterChain.java:256位于org.apache.catalina.core.ApplicationFilterChain.java:256位于org.apache.catalina.core.StandardWrapperValve.invokeStandardWrapperValve.java:279在org.apache.catalina.core.StandardContextValve.invokeStandardContextValve.java:175在org.apache.catalina.core.StandardPipeline.doInvokeStandardPipeline.java:655在org.apache.catalina.core.StandardHostValve.invokeStandardHostValve.java:161在org.apache.catalina.connector.CoyoteAdapter.doServiceCoyoteAdapter.java:331在org.apache.catalina.connector.CoyoteAdapter.CoyoteAdapter.java:231在com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallContainerMapper.java:317在com.sun.enterprise.v3.services.impl.ContainerMapper.serviceContainerMapper.java:195在com.sun.grizzly.http.ProcessorTask.invokeAdApertProcessorTask.java:849在com.sun.grizzly.http.ProcessorTask.ProcessorTask.java:746在com.sun.grizzly.http.ProcessorTask.ProcessorTask.java:1045在java:228在com.sun.grizzly.DefaultProtocolChain.ExecutedProtocolFilterDefaultProtocolChain.ExecutedProtocolFilterDefaultProtocolChain.java:137在com.sun.grizzly.DefaultProtocolChain.ExecutedProtocolChain.java:104在com.sun.grizzly.DefaultProtocolChain.ExecutedProtocolChain.java:90在java:79在com.sun.grizzly.ProtocolChainContextTask.doCallProtocolChainContextTask.java:54在com.sun.grizzly.SelectionKeyContextTask.callSelectionKeyContextTask.java:59在com.sun.grizzly.ContextTask.runContextTask.java:71在com.sun.grizzly.util.AbstractThreadPool$Worker.doWorkAbstractThreadPool.java:532在com.sun.grizzly.util.AbstractThreadPool$Worker.runAbstractThreadPool.java:513在java.lang.Thread.runThread.java:722

---

验证您是否在WEB-INF/lib中包含了库el-api-2.2.jar和el-impl-2.2.jar

---

关于这一点，

至少，您可以提供一个带有代码的实际页面链接，并指定您的配置发布给您带来问题的JSF代码。社区不会猜到你现在有什么问题。