[
https://issues.jboss.org/browse/RF-11054?page=com.atlassian.jira.plugin.s...
]
Jean ANDRE commented on RF-11054:
---------------------------------
There is definitively a link with the component outputPanel. When the outputPanel is
removed, the exception may not appear. Removing the tab, by the onclick on a graphicImage
has not the same effect as using the h:commandButton with action. In the second way, it
does not trigger the NPE but the tag must be selected before to be able to delete the
tab.
Moreover, I've just try the version 4.1.0 M4, this version displays the following
stack trace instead of the NPE - We do not have a NPE but an IndexOutBounds Exception.
Setting the activeItem, was ever the way (binding, activeItem, by
ViewRoot.findComponent,...), does not have any effect.
Here is the stack trace.
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1147)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:722)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:449)
at
com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1020)
at
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:883)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1659)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at
com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1648)
Caused by: java.lang.IndexOutOfBoundsException: Index: 14, Size: 15
at java.util.ArrayList.get(ArrayList.java:347)
at
com.sun.faces.facelets.tag.jsf.ComponentSupport.finalizeForDeletion(ComponentSupport.java:136)
at
com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.doOrphanedChildCleanup(ComponentTagHandlerDelegateImpl.java:338)
at
com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:192)
at
javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at
javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at
org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
at
com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184)
at
javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at
javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:166)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
Dynamically created tabs within tabPanel causes NPE in
getActiveItem()
----------------------------------------------------------------------
Key: RF-11054
URL:
https://issues.jboss.org/browse/RF-11054
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: base functionality , component-panels-layout-themes
Affects Versions: 4.0.0.Final
Environment: RichFaces 4.1.0-SNAPSHOT r.22526
Metamer r.22526
Mojarra 2.0.4-b09
Apache Tomcat 7.0.12
Java(TM) SE Runtime Environment 1.6.0_19-b04 @ Linux
Chrome 12.0.718.0 @ Linux i686
Reporter: Ján Jamrich
Fix For: 4.Future
Attachments: exception-on-tab-switch
When set switchType on TabPanel to "server" (notice that with
"client" everything works correctly, with "ajax" tab switch not work
as well as with "null"), all dynamically created tabs causes NPE on tab switch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira