OK I found this in my FRAMEWORK. Its the FrameworkPrincipal class. Eclipse is marking er.attachment.model.ERAttachment as

The import er.attachment cannot be

resolved

This was no issue with Fluffy Bunny!

package com.as;

import er.attachment.model.ERAttachment;
import er.corebusinesslogic.ERCoreBusinessLogic;
import er.extensions.ERXFrameworkPrincipal;

public class ASBriefsFrameworkPrincipal extends ERXFrameworkPrincipal {

    protected static ASBriefsFrameworkPrincipal sharedInstance;

    public final static Class[] REQUIRES = new Class[] {
            ERAttachment.class, ERCoreBusinessLogic.class
            };

    static {
setUpFrameworkPrincipalClass(ASBriefsFrameworkPrincipal.class);
    }

    public static ASBriefsFrameworkPrincipal sharedInstance() {
        if (sharedInstance == null) {
            sharedInstance = sharedInstance(ASBriefsFrameworkPrincipal.class);
        }
        return sharedInstance;
    }

    @Override
    public void finishInitialization() {
        log.debug("ASBriefsFrameworkPrincipal loaded");
    }
}

On 1/29/26 12:42 AM, Theodore Petrosky via Webobjects-dev wrote:


I thought ERAttachment was included in ERCoreBusinessLogic. What am I missing?

I have a dependency:

        <dependency>
            <groupId>wonder.businesslogic</groupId>
<artifactId>ERCoreBusinessLogic</artifactId>
            <version>${wonder.version}</version>
        </dependency>


and the error:

Jan 29 05:35:00 ASBriefsD2W[64169] ERROR er.extensions.appserver.ERXApplication  - ASBriefsD2W failed to start. IllegalArgumentException: There is no model named 'ERAttachment' in this model group.   at er.extensions.migration.ERXMigrator._buildDependenciesForModelsNamed(ERXMigrator.java:274)   at er.extensions.migration.ERXMigrator.migrateToLatest(ERXMigrator.java:185)   at er.extensions.appserver.ERXApplication.finishInitialization(ERXApplication.java:1311)   at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
  ... skipped 10 stack elements
Jan 29 05:35:00 ASBriefsD2W[64169] WARN  NSLog  - A fatal exception occurred: There is no model named 'ERAttachment' in this model group. [2026-1-29 5:35:0 UTC] <main> java.lang.IllegalArgumentException: There is no model named 'ERAttachment' in this model group.     at er.extensions.migration.ERXMigrator._buildDependenciesForModelsNamed(ERXMigrator.java:274)     at er.extensions.migration.ERXMigrator.migrateToLatest(ERXMigrator.java:185)     at er.extensions.appserver.ERXApplication.finishInitialization(ERXApplication.java:1311)     at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
    at java.base/java.lang.reflect.Method.invoke(Method.java:580)
    at com.webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java:122)     at com.webobjects.foundation.NSNotificationCenter$_Entry.invokeMethod(NSNotificationCenter.java:588)     at com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:532)     at com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:546)
    at com.webobjects.appserver.WOApplication.run(WOApplication.java:1229)
    at er.extensions.appserver.ERXApplication.run(ERXApplication.java:1431)
    at com.webobjects.appserver.WOApplication.main(WOApplication.java:548)
    at er.extensions.appserver.ERXApplication.main(ERXApplication.java:888)
    at com.as.application.app.Application.main(Application.java:19)

APPLICATION SHUTDOWN SEQUENCE COMPLETE
  • dependency issue Theodore Petrosky via Webobjects-dev
    • Re: dependency issue Theodore Petrosky via Webobjects-dev

Reply via email to