This is related to a new feature in Abator. If you specify a rootClass, then Abator will try to load that class and look for existing properties that would conflict with properties it would normally generate. If there is an existing property in the rootClass that matches one of the new properties, then Abator will not generate the property (deferring to the property in the rootClass).
As you've seen, if Abator cannot load the root class, then no harm done - just a warning message. There is a new property "rootClasspath" for the JavaModelGenerator that you can use to specify a classpath if you want to take advantage of this feature. Jeff Butler On Wed, Mar 26, 2008 at 1:17 PM, Ryan Shelley <[EMAIL PROTECTED]> wrote: > I've noticed this as well, but it doesn't seem to affect anything in my > generated files. > > -Ryan > > > On Wed, Mar 26, 2008 at 11:08 AM, kbighorse <[EMAIL PROTECTED]> wrote: > > > > > Appears harmless, but got the warning "Root class <class> cannot be > > loaded, > > checking for member overrides is disabled for this class". Set > > rootClass > > <property> in <javaModelGenerator> in abatorConfig.xml. Checked all my > > classes and all extend rootClass as expected. rootClass does have an > > instance variable, but it doesn't conflict with any generated properties > > that I can find. Did anything happen/not happen that I should be aware > > of? > > > > Kimball > > -- > > View this message in context: > > http://www.nabble.com/Abator-1.1.0%3A-Root-class-cannot-be-loaded-tp16309782p16309782.html > > Sent from the iBATIS - User - Java mailing list archive at > > Nabble.com<http://nabble.com/> > > . > > > > >
