Expand my Community achievements bar.

SOLVED

Wrong bundle location in web console

Avatar

Level 1

I am working on AEM 6.4 project. I saw that my core bundles are not installing in "jcrinstall:/apps/etap/install/etap.core-1.0-SNAPSHOT.jar" but installing in "inputstream:etap.core-1.0-SNAPSHOT.jar".

So when i export my project, none of my back end logic is being exported. How to change Bundle location in web console?

I tried uninstalling in console and running autoInstallBundle from ecllipse, but it is installing in wrong location only.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

When you use the standard AEM maven archetypes, you should have also have an ui.apps project, which builds a content-package you can deploy.

Jörg

View solution in original post

5 Replies

Avatar

Employee Advisor

when you install bundles directly (not as part of a content package) via maven or directly in the OSGI webconsole, it will register directly in Felix and will not install via the repository. When you embed a bundle in a content-package and then deploy the content-package into AEM, it will result in the bundle location "jcrinstall:/...".

From a functional point of view it does not make any difference.

HTH,

Jörg

Avatar

Level 1

Hi, Thanks for the reply.

Now i have my java code in eclipse. This as I told is installed in repository. If I want my java code to be in apps/etap/install, so that I can share my project as content-package What can I do?

And the current java file in install folder is also corrupted. Please suggest how can we solve this.

Avatar

Correct answer by
Employee Advisor

When you use the standard AEM maven archetypes, you should have also have an ui.apps project, which builds a content-package you can deploy.

Jörg

Avatar

Level 1

Sorry for the mistake in my previous comment. It is not installing in repository. It is installing in "inputstream:etap.core-1.0-SNAPSHOT.jar".

Avatar

Level 10

When you deploy your Maven Archetype AEM Project- it places the bundle in the install folder when you run the command

mvn -PautoInstallPackage install

To fix any Java issue, recompile in Eclipse and redeploy.

So two thing happen when using the above command:

1 - THE OSGI bundle is placed into the AEM service container and placed into an Active State (assuming you have all correct dependencies)

2 - Its placed in the Install folder under /app