2011-05-09 27 views
3

当从EL调用JSF Bean时,我有一个关于方法签名的问题。在JSF 2.0中调用方法的方法签名?

在下面的例子中,我有3个方法调用,在的outputText value属性,并在该命令按钮的actionListener & & action属性。

<p:dataTable id="gridRPBDetails" 
    var="rpbDetail" 
    value="#{tInputBean.detailList}" 
    selection="#{tInputBean.selectedDetails}"> 

    .... 

    <p:column selectionMode="multiple" /> 
    <p:column> 
     <h:outputText value="#{tInputBean.isNewRecord(rpbDetail) ? 'New' : tInputBean.isEditRecord(rpbDetail) ? 'Edited' : '-'}"/> 
    </p:column> 
    <p:column> 
     <p:commandButton 
      process="@this" 
      actionListener="#{tInputBean.activateDetail(rpbDetail)}" 
      action="#{tInputBean.querySubAnggaranListImpl(rpbDetail.map['subBudget.budget'])}" 
      update="DetailDialogForm" 
      oncomplete="detailDialog.show();" 
      image="ui-icon ui-icon-search"/> 
    </p:column> 

    .... 

一个很奇怪的是,无论是actionListener="#{tInputBean.activateDetail(rpbDetail)}"action="#{tInputBean.querySubAnggaranListImpl(rpbDetail.map['subBudget.budget'])}"可以有一个自定义类型作为参数(在这种情况下,这是一个my.package.Dto型):

public void activateDetail(Dto activeDetail) { 
    .... 
} 
public void querySubAnggaranListImpl(Dto budget) { 
    DebugUtil.start("querySubAnggaranListImpl"); 
    .... 
    DebugUtil.end("querySubAnggaranListImpl"); 
} 

其中isNewRecord方法需要一个java.lang.Object中:

public boolean isNewRecord(Dto record) { // this does NOT work 
    .... 
} 

这是生成的跟踪S:

ERROR BusinessExceptionHandler - javax.el.ELException: /TInput.xhtml @156,130 value="#{tInputBean.isNewRecord(rpbDetail) ? 'New' : tInputBean.isEditRecord(rpbDetail) ? 'Edited' : '-'}": java.lang.NoSuchMethodException: id.co.sofcograha.cashbank.webapp.paymentplan.TInputBean.isNewRecord(java.lang.Object) 
javax.el.ELException: /TInput.xhtml @156,130 value="#{tInputBean.isNewRecord(rpbDetail) ? 'New' : tInputBean.isEditRecord(rpbDetail) ? 'Edited' : '-'}": java.lang.NoSuchMethodException: id.co.sofcograha.cashbank.webapp.paymentplan.TInputBean.isNewRecord(java.lang.Object) 
     at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:114) 
     at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:193) 
     at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:181) 
     at javax.faces.component.UIOutput.getValue(UIOutput.java:169) 
     at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:205) 
     at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:355) 
     at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:164) 
     at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:883) 
     at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1659) 
     at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1655) 
     at org.primefaces.component.datatable.DataTableRenderer.encodeRegularCell(DataTableRenderer.java:571) 
     at org.primefaces.component.datatable.DataTableRenderer.encodeRow(DataTableRenderer.java:531) 
     at org.primefaces.component.datatable.DataTableRenderer.encodeTbody(DataTableRenderer.java:472) 
     at org.primefaces.component.datatable.DataTableRenderer.encodeRegularTable(DataTableRenderer.java:201) 
     at org.primefaces.component.datatable.DataTableRenderer.encodeMarkup(DataTableRenderer.java:180) 
     at org.primefaces.component.datatable.DataTableRenderer.encodeEnd(DataTableRenderer.java:85) 
     at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:883) 
     at org.primefaces.renderkit.CoreRenderer.renderChild(CoreRenderer.java:59) 
     at org.primefaces.renderkit.CoreRenderer.renderChildren(CoreRenderer.java:43) 
     at org.primefaces.component.panel.PanelRenderer.encodeContent(PanelRenderer.java:229) 
     at org.primefaces.component.panel.PanelRenderer.encodeMarkup(PanelRenderer.java:152) 
     at org.primefaces.component.panel.PanelRenderer.encodeEnd(PanelRenderer.java:75) 
     at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:883) 
     at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1659) 
     at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) 
     at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:853) 
     at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1652) 
     at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1655) 
     at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1655) 
     at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1655) 
     at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1655) 
     at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:399) 
     at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131) 
     at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) 
     at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) 
     at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) 
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) 
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) 
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) 
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240) 
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) 
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) 
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) 
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541) 
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) 
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:383) 
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:243) 
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:188) 
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:166) 
     at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:288) 
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
     at java.lang.Thread.run(Thread.java:662) 
Caused by: java.lang.NoSuchMethodException: id.co.sofcograha.cashbank.webapp.paymentplan.TInputBean.isNewRecord(java.lang.Object) 
     at java.lang.Class.getMethod(Class.java:1605) 
     at javax.el.BeanELResolver.invoke(BeanELResolver.java:405) 
     at javax.el.CompositeELResolver.invoke(CompositeELResolver.java:161) 
     at org.apache.el.parser.AstValue.getValue(AstValue.java:159) 
     at org.apache.el.parser.AstChoice.getValue(AstChoice.java:45) 
     at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:189) 
     at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) 
     ... 52 more 
DEBUG DebugUtil - ************ END printing stack trace ************ 

但是,如果我加入这个方法,一切工作顺利:

public boolean isNewRecord(Object o) { // this DOES work 
    return isNewRecord((Dto) o); 
} 

的基本问题是: 为什么该方法从JSF调用有时可以接受定制类型,有时不是?


顺便说一句,即时通讯使用的是Tomcat 7,而这些是我的依赖关系:

<dependency> 
    <groupId>org.primefaces</groupId> 
    <artifactId>primefaces</artifactId> 
    <version>2.2.1</version> 
</dependency> 
<dependency> 
    <groupId>com.sun.faces</groupId> 
    <artifactId>jsf-api</artifactId> 
    <version>2.0.4-b09</version> 
    <scope>compile</scope> 
</dependency> 
<dependency> 
    <groupId>com.sun.faces</groupId> 
    <artifactId>jsf-impl</artifactId> 
    <version>2.0.4-b09</version> 
    <scope>compile</scope> 
</dependency> 

谢谢!

回答

1

这是EL实现特有的。从我在一次演讲中听到的内容来看,规范并不完全清楚这种情况,因此实现者必须做出决定。

但Tomcat的实现应该按照您的预期工作。尝试将您的tomcat升级到最新版本,并确保您没有在您的WEB-INF/lib

+0

确实升级tomcat解决了问题。谢谢 ! – bertie 2011-07-05 07:08:06