[英]Richfaces <a4j:ajax> and <rich:popupPanel> “conflict”
[英]JSF 2 + Richfaces 4.2.3 - <a4j:ajax> will not complete if <rich:pickList> is in the <h:form>
我在a4j:ajax標簽里面遇到麻煩啊:當有一個rich:pickList或者一個rich:ordersList時,表單形式相同。 會發生什么是ajax請求沒有完成,並且我的支持bean中的監聽器方法沒有被觸發。 引發了onbegin事件,但是oncomplete不是。 這真的很奇怪。
如果我將組件更改為rich:select或其他類似組件,則ajax可以正常工作。
這是我的代碼的一部分。
<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:s="http://jboss.org/schema/seam/taglib"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:a="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich"
xmlns:a4j="http://richfaces.org/a4j"
template="layout/template.xhtml">
<ui:define name="body">
<h:form id="perfil" styleClass="edit">
<rich:panel>
<a4j:outputPanel id="outputPanel">
<s:decorate id="nomeField" template="layout/edit.xhtml">
<ui:define name="label">Nome</ui:define>
<h:inputText id="nome" size="100" maxlength="100"
value="#{perfilHome.instance.nome}">
<a4j:ajax event="blur" onbegin="alert('begin');"
oncomplete="alert('complete');" bypassUpdates="true" render="outputPanel"
listener="#{perfilHome.test()}" />
</h:inputText>
</s:decorate>
</a4j:outputPanel>
<s:decorate id="descricaoField" template="layout/edit.xhtml">
<ui:define name="label">Descrição</ui:define>
<h:inputTextarea id="descricao" required="true" cols="100" rows="4" value="#{perfilHome.instance.descricao}" />
</s:decorate>
<s:decorate id="permissoesField" template="layout/edit.xhtml">
<rich:pickList required="true" styleClass="picklist" style="border: none; background: transparent;"
collectionType="java.util.ArrayList" immediate="false"
id="permissaoPickList"
value="#{perfilHome.instance.permissoes}"
listWidth="165px" listHeight="100px" orderable="true">
<f:selectItems id="permissoesItens" value="#{perfilHome.listarPermissoes()}" var="permissao"
itemValue="#{permissao}" itemLabel="#{permissao.nome}" />
<s:convertEntity />
</rich:pickList>
</s:decorate> </rich:panel>
<div class="actionButtons">
<h:commandButton id="save" value="Salvar"
action="#{perfilHome.persist}" disabled="#{!perfilHome.wired}"
rendered="#{!perfilHome.managed}">
<s:conversationId />
</h:commandButton>
<h:commandButton id="update" value="Salvar"
action="#{perfilHome.update}" rendered="#{perfilHome.managed}">
<s:conversationId />
</h:commandButton>
<h:commandButton id="delete" value="Deletar"
action="#{perfilHome.remove}" immediate="true"
rendered="#{perfilHome.managed}" /> </div>
</h:form>
<s:button id="cancelEdit" value="Cancelar" propagation="end"
view="/Perfil.xhtml" rendered="#{perfilHome.managed}" />
<s:button id="cancelAdd" value="Cancelar" propagation="end"
view="/#{empty perfilFrom ? 'PerfilList' : perfilFrom}.xhtml"
rendered="#{!perfilHome.managed}" />
</ui:define>
</ui:composition>
正如我所說,我只是用pickList和orderingList觀察到了這種行為。 有沒有人有這樣的問題?
我的第二個問題是,如果我在表單中放入兩個s:按鈕,那么ajax也不會被觸發。 對此有解釋嗎?
我正在使用JSF 2.1.14 + RichFaces 4.2.3 + Seam 2.3.0
謝謝
更新於2013年1月14日。 觀察到我之前沒有注意到的堆棧跟蹤。 我認為觀點狀態正在消失。 再次使用許多組件進行測試,只注意到pickList和orderingList的問題。
Exception during request processing:
Caused by java.lang.NullPointerException with message: ""
com.sun.faces.context.PartialViewContextImpl.createPartialResponseWriter(PartialViewContextImpl.java:441)
com.sun.faces.context.PartialViewContextImpl.access$300(PartialViewContextImpl.java:71)
com.sun.faces.context.PartialViewContextImpl$DelayedInitPartialResponseWriter.getWrapped(PartialViewContextImpl.java:582)
javax.faces.context.PartialResponseWriter.startDocument(PartialResponseWriter.java:115)
com.sun.faces.context.AjaxExceptionHandlerImpl.handlePartialResponseError(AjaxExceptionHandlerImpl.java:199)
com.sun.faces.context.AjaxExceptionHandlerImpl.handle(AjaxExceptionHandlerImpl.java:123)
com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119)
com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116)
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397)
org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50)
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
java.lang.Thread.run(Thread.java:722)
你的<rich:pickList/>
很可能是轉換失敗,導致整個表單提交窒息而且原因很明顯:你沒有在列表中定義轉換器而你正在嘗試將復雜類型更新為支持豆。 除非你的value
綁定是常規的java類型而不是pojo,否則你必須在<f:selectItems/>
上實現和定義一個JSF轉換器。 嘗試通過在視圖中放置<h:messages/>
來確認這一點,以顯示驗證/轉換錯誤
這也是為什么建議將JSF組件分成較小的形式而不是現在的巨大形式的一個很好的理由; 使用較小的表單更容易調試
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.