Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

AEM 6.5.6 org.apache.felix.framework not export all dependencies from its manifest

Avatar

Level 3

Hello,

I am working on a new instance AEM 6.5.6 and org.apache.felix.framework bundle not export all dependencies defined on its manifest. 

For example, libraries javax.rmi or CORBA.

I have another instance AEM 6.5.6,which was upgraded, and export were correctly. 

Any suggestions?

 

AEM New, references not exported:

abcr1_0-1603438719487.png

 

On AEM 6.5 upgraded, exported correctly:

abcr1_1-1603438751548.png

 

Thanks!

 

 

 

5 Replies

Avatar

Community Advisor

Is this new instance connected to any VPN or Security restrictions?

Do you see any error / warnings ?

Avatar

Level 3

Hello, new instance does not have connection with any VPN or Security restrictions. All bundles active, but some api does not exported correctly as on upgraded instance.

I have a local instance too and I have same error too. Thanks!

Avatar

Community Advisor

Hi @abcr1 

May I know which Java version is installed in your system? If you are running on Java 11 check the below link.

https://docs.oracle.com/en/java/javase/11/migrate/index.html#JSMIG-GUID-C25E2B1D-6C24-4403-8540-CFEA...

AG

Avatar

Level 3
Hi, I have Java 8. Thanks all for your comments, finally I have modified my bundle, export dependencies in a new library. But It is interesting how libraries have different behavior on an upgrade instance or new instance, when java version and SO are identicals. Thanks !!

Avatar

Employee

Hi @abcr1 , I am also facing same issue

jeromeleslyv_0-1714991215060.png

Can you tell me little bit more how did you resolved this?
All these packages are exporting from org.apache.felix.framework but still its not resolved