Getting closer. Problem so far: there are two ID's of 81 (obviously). The first one get's its ID during the restore view (even though the view is new) phase while the view root has not been created yet. The second one has the ID obtained from the view root.
The stack of when the first 81 is assigned: 2006-04-14 13:03:16,673 INFO [STDOUT] ---------- OutputText. this: [EMAIL PROTECTED] Setting Id to = _id81. View ID: null 2006-04-14 13:03:16,673 INFO [STDOUT] java.lang.Exception: Stack trace 2006-04-14 13:03:16,674 INFO [STDOUT] at java.lang.Thread.dumpStack(Thread.java:1158) 2006-04-14 13:03:16,674 INFO [STDOUT] at javax.faces.component.html.HtmlOutputText.setId(HtmlOutputText.java:69) 2006-04-14 13:03:16,674 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:112) 2006-04-14 13:03:16,675 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:121) 2006-04-14 13:03:16,675 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:121) 2006-04-14 13:03:16,675 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:121) 2006-04-14 13:03:16,675 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:121) 2006-04-14 13:03:16,675 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:121) 2006-04-14 13:03:16,675 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:121) 2006-04-14 13:03:16,675 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:121) 2006-04-14 13:03:16,675 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:121) 2006-04-14 13:03:16,675 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:121) 2006-04-14 13:03:16,675 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.internalRestoreTreeStructure(TreeStructureManager.java:121) 2006-04-14 13:03:16,676 INFO [STDOUT] at org.apache.myfaces.application.TreeStructureManager.restoreTreeStructure(TreeStructureManager.java:99) 2006-04-14 13:03:16,676 INFO [STDOUT] at org.apache.myfaces.application.jsp.JspStateManagerImpl.restoreTreeStructure(JspStateManagerImpl.java:271) 2006-04-14 13:03:16,676 INFO [STDOUT] at org.apache.myfaces.application.jsp.JspStateManagerImpl.restoreView(JspStateManagerImpl.java:283) 2006-04-14 13:03:16,676 INFO [STDOUT] at org.jboss.seam.jsf.SeamPhaseListener$StateManagerInterceptor.restoreView(SeamPhaseListener.java:205) 2006-04-14 13:03:16,676 INFO [STDOUT] at org.apache.myfaces.application.jsp.JspViewHandlerImpl.restoreView(JspViewHandlerImpl.java:255) 2006-04-14 13:03:16,676 INFO [STDOUT] at org.jenia.faces.template.handler.ViewHandler.restoreView(ViewHandler.java:246) 2006-04-14 13:03:16,676 INFO [STDOUT] at com.sun.facelets.FaceletViewHandler.restoreView(FaceletViewHandler.java:321) 2006-04-14 13:03:16,676 INFO [STDOUT] at org.apache.myfaces.lifecycle.LifecycleImpl.restoreView(LifecycleImpl.java:141) 2006-04-14 13:03:16,676 INFO [STDOUT] at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:66) I am creating a new view though, so I am not sure how this same component gets from an old view to the new view. Is MyFaces reusing components accross views? -Andrew On 4/14/06, Andrew Robinson <[EMAIL PROTECTED]> wrote: > Well, it is not the view root, I added some println's to the view root and > got: > 12:26:33,246 INFO [STDOUT] --------------- NEW UNIQUE ID: 80 (this: > [EMAIL PROTECTED]) > 12:26:33,246 INFO [STDOUT] --------------- NEW UNIQUE ID: 81 (this: > [EMAIL PROTECTED]) > 12:26:33,247 INFO [STDOUT] --------------- NEW UNIQUE ID: 82 (this: > [EMAIL PROTECTED]) > > But I still got the error (_id81 is duplicate). So it seems the > duplicate ID is coming from somewhere else. Anyone know of an > alternate locate that tomahawk controls may be getting their IDs from? > > > > On 4/14/06, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > Unfortunately trying to reproduce it is a pain as I have many files > > involved to build this one view, and other files using the same > > template work. I'm going to try to get in the current code myself and > > see if I can debug it. I'll either send a patch or at least provide > > some insight on the problem if I can. > > > > -Andrew > > > > On 4/14/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > > > On 4/14/06, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > > > Okay, the no class error was because I accidentally copied the sandbox > > > > into my classpath. That error went away when I upgraded. > > > > > > > > However, I am still hosed! The 1.1.2 still produces duplicate IDs. I > > > > got the same exception in the same spot in component tree. > > > > > > > > Any ideas? > > > > > > Unfortunately, no. I don't suppose you could produce a small example > > > demoing the problem so we can get it front of someone who knows > > > something? I'm not an expert on duplicate id issues -- it seems like > > > I'm more of an expert on version control these days.... > > > > > >
