EAR deployment fails if jars contain OSGi headers

[sebp]

I have an .ear deployment. Inside it I have lots of jars. One of these jars contains entities. My .ear deployment fails if this jar also contains OSGi manifest headers.

07:47:18,309 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

JBAS014775:    New missing/unsatisfied dependencies:

      service jboss.module.spec.service."deployment.com.test.genrefdata.demo-6.0.0-SNAPSHOT.ear.GeneticReference_Persistence.jar".main (missing) dependents: ...

I don't want to use OSGi in my .ear deployment. But I'm also using the library with the entities in other environments where the OSGi manifest headers are needed.

Can I disable OSGi on JBoss? Or at least for this deployment?

Btw: I'm using JBoss 7.1.1.

Thx.

[jaikiran]

Sebastian, 7.1.1 is a very old version. I would recommend that you upgrade to WildFly (JBoss AS has been renamed to WildFly) 8.1.0.Final which was recently released Downloads · WildFly. WildFly no longer has OSGi support (by default), so you shouldn't run into that problem.

[sebp]

Thanks for the quick answer. In our project switching to Wildfly is not an option at the moment. But I realized that I can remove the osgi extension from the configuration. Then the deployment works just fine. I hope that this does not break anything else.

[jaikiran]

Sebastian Lorenz wrote:

But I realized that I can remove the osgi extension from the configuration. Then the deployment works just fine. I hope that this does not break anything else.

Yes, that's the other option and removing it should be fine.