Using EBean 7 and 12 in one application

[tbee]

Is it possible to use EBean 7 and 12 in one application? Or are we on a dead end?

We are in the process of migrating a rather large multimodule application to EBean 12 (then Java 11, then EBean 13). In order not to have to do a big bang migration, it would be preferable that the migration could be done in steps. Since Ebean 12 uses a completely different package, it seems this could be possible:

• Replace the maven dependency of one maven module/artifact with EBean 12,
• switch the compile time enhancement in the pom to EBean 12,
• and of course let the repository that accesses the data use 'DB' instead of 'Ebean'.

Compilewise this works, but at startup EBean 7 finds the EBean 12 classes and complains about them not being enhanced. Can this be configured?

14:49:50,821 ERROR [com.avaje.ebeaninternal.server.deploy.BeanDescriptorManager] (ServerService Thread Pool -- 112) Error in deployment: java.lang.IllegalStateException: Bean class com.nedap.healthcare.administration.properties.Property is not enhanced?
        at com.avaje.ebeaninternal.server.deploy.BeanDescriptorManager.setEntityBeanClass(BeanDescriptorManager.java:1462)
        at com.avaje.ebeaninternal.server.deploy.BeanDescriptorManager.createByteCode(BeanDescriptorManager.java:1207)
        at com.avaje.ebeaninternal.server.deploy.BeanDescriptorManager.readDeployAssociations(BeanDescriptorManager.java:1124)
        at com.avaje.ebeaninternal.server.deploy.BeanDescriptorManager.readEntityDeploymentAssociations(BeanDescriptorManager.java:606)
        at com.avaje.ebeaninternal.server.deploy.BeanDescriptorManager.deploy(BeanDescriptorManager.java:317)
        at com.avaje.ebeaninternal.server.core.InternalConfiguration.<init>(InternalConfiguration.java:134)
        at com.avaje.ebeaninternal.server.core.DefaultContainer.createServer(DefaultContainer.java:121)
        at com.avaje.ebeaninternal.server.core.DefaultContainer.createServer(DefaultContainer.java:74)
        at com.avaje.ebeaninternal.server.core.DefaultContainer.createServer(DefaultContainer.java:41)
        at com.avaje.ebean.EbeanServerFactory.create(EbeanServerFactory.java:55)
        at com.avaje.ebean.Ebean$ServerManager.getWithCreate(Ebean.java:210)
        at com.avaje.ebean.Ebean$ServerManager.<init>(Ebean.java:168)
        at com.avaje.ebean.Ebean$ServerManager.<init>(Ebean.java:133)
        at com.avaje.ebean.Ebean.<clinit>(Ebean.java:127)

[rbygrave]

Compilewise this works, but at startup EBean 7 finds the EBean 12 classes and complaints about them not being enhanced. Can this be configured?

Yes it can. Use ServerConfig.addClass() to explicitly register the entity classes with that version of Ebean.