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? -Andrew On 4/14/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > On 4/14/06, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > I'm getting the following exception with the current 1.1.2 nighly: > > > > java.lang.NoClassDefFoundError: > > org/apache/myfaces/application/ComponentNotFoundException > > Sounds like you are using an old version of sandbox. > This file was moving from myfaces-core to sandbox a couple weeks ago > (maybe more) by myself. > > You really want to be using either the 1.1.2 proposed releases or > later for all of your myfaces jars. This will eliminate dependency > problems like this -- sandbox had dependences on core until earlier > today -- and you'll no longer have to keep core and tomahawk versions > in sync. > > I'm currently retesting my facelets applications with the proposed > MyFaces 1.1.2 release from yesterday (on nightlies) and with an SVN > snapshot of Tomahawk/sandbox from a couple of hours ago. > > If it's not possible to upgrade sandbox/tomahawk, manually copy the > file (either from the old SVN attic or from the new location as part > of the sandbox AjaxDecodePhaseListener) and add it to your classpath. > The class isn't used by anything else, so that should be safe. You > can manually create your own version too -- it's a trivial subclass of > FacesException. > > If you go to the "quick fix" route, make sure you're not using any of > the other sandbox components that depend on core. See this issue for > a list. > > http://issues.apache.org/jira/browse/TOMAHAWK-220 >
