I cleared the cache and cookie as you said. I got pretty much the same error, just the node id slightly different. Any idea?
ERROR [http-8080-Processor24] - Node with id 0:1. Failed to parse 0:1 java.lang.IllegalArgumentException: Node with id 0:1. Failed to parse 0:1 From: "Boeckli, Dominique" <[EMAIL PROTECTED]> Date: Wed Jan 25 11:19:05 CST 2006 To: [EMAIL PROTECTED] Subject: RE: tree2 clientSideToggle question need more help Remove the cached files including the cookies from your browser when changed to clientsidetoggle -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 25. Januar 2006 17:44 To: Boeckli, Dominique; users Subject: tree2 clientSideToggle question need more help The other reason I want to use tree2 clientSideToggle is when expand the tree, or click on the tree, the whole page does not refresh. For the server-side toggle, each click on the tree will generate a request which cause the web page to refresh. That's freaky. But when I use clientSideToggle, and modify the tree backing bean data, I got that ERROR [http-8080-Processor24] - Node with id 0:0. Failed to parse 0:0. I think because the tree data was stored in cookie of the browser, while changing the data of the tree causes the inconsistency with the cookie. But I don't know how to solve that problem. Anyone can help me? From: "Boeckli, Dominique" <[EMAIL PROTECTED]> Date: Wed Jan 25 02:41:06 CST 2006 To: MyFaces Discussion <[email protected]> Subject: RE: tree2 clientSideToggle question it can be faster! if the tree is huge the memory usage on the browser side is huge. In your case try to remove all cached files in your browser. kind regards Dominique From: Yixing Ma [mailto:[EMAIL PROTECTED] Sent: Dienstag, 24. Januar 2006 20:00 To: [email protected] Subject: tree2 clientSideToggle question Hi, I have a quick question about tree2 component. I set the clientSideToggle="true" After I changed the data of the tree in a method, and reload the tree I got a ERROR [http-8080-Processor24] - Node with id 0:0. Failed to parse 0:0 java.lang.IllegalArgumentException: Node with id 0:0. Failed to parse 0:0 at org.apache.myfaces.custom.tree2.TreeModel.getNodeById(TreeModel.java:153) at org.apache.myfaces.custom.tree2.TreeModel.setNodeId(TreeModel.java:71) at org.apache.myfaces.custom.tree2.UITreeData.setNodeId(UITreeData.java:290) at org.apache.myfaces.custom.tree2.HtmlTree.setNodeId(HtmlTree.java:80) at org.apache.myfaces.custom.tree2.HtmlTreeRenderer.decode(HtmlTreeRenderer.java:104) at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:305) at org.apache.myfaces.custom.tree2.UITreeData.processDecodes(UITreeData.java:139) at org.apache.myfaces.custom.tree2.HtmlTree.processDecodes(HtmlTree.java:91) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:407) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:407) at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:151) at org.apache.myfaces.lifecycle.LifecycleImpl.applyRequestValues(LifecycleImpl.java:177) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:87) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:109) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.myfaces.component.html.util.ExtensionsFilter.doFilter(ExtensionsFilter.java:112) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) How can I slove this problem? If I set clientSideToggle="false", no problem. But I really want to use clientSideToggle="true", coz it's way faster.
