> If that doesn't work, I recommend using the "spawn" command in Swat to
> start your application. This will stop the application's start-up
> sequence early enough for you to use commands like "gentree" and
> "vistree" to analyze the object tree of your geode. Using those two
> commands you can check that all of the objects are attached to the
> object tree.
>
In addition to Nathan's advice, you could also use the "cup <classname>"
command to see what classes you have to deal with, and then use "methods
<@number class to inspect>" to see what messages that you've written are
available for you to use as break points. This works as far down the tree as
you need, down to meta.
>From the output, however, it looks to me like you may have either a.)
forgotten a class (although I don't see how since it compiled <g>) or b.)
you're doing a little custom subclassing and there's something wrong with
your subclass and it's not building out properly at run time, hence, when it
tries to build and fails, you're getting that message. <--pure guess, of
course, since I have no idea what your code is trying to do or whether you
have modified a class.
Lee