Enabling fabric disables features, osgi, admin, commands

[pratik_patel]

Hi,

I am using Fuse ESB 7.0 on Windows 7. When I launch Fuse ESB, osgi:list shows around 95 plugins deployed. I can also see the 'features', 'admin', 'fab' and many other commands.

But as soon as I initialize fabric using 'fabric --clean root', I cannot see features, admin, fab commands. osgi:list shows only 7 plugins.

   ID   State         Blueprint      Level  Name

Apache Karaf :: Shell :: Main shell (2.2.5.fuse-70-097)

Fuse Fabric :: Core Agent SSH (7.0.2.fuse-097)

Fuse Fabric :: Maven Proxy (7.0.2.fuse-097)

Fuse Fabric :: ZooKeeper ConfigAdmin Bridge (7.0.2.fuse-097)

Fuse Fabric :: JAAS (7.0.2.fuse-097)

Fuse Fabric :: Karaf Commands (7.0.2.fuse-097)

Fuse Fabric :: Provisioning Agent (7.0.2.fuse-097)

I cannot understand the behavior. Am I doing something wrong?

Thanks,

Pratik

Edited by: pratik_patel on Jan 18, 2013 5:46 PM

[jasonnh]

Hi,

I had that problem as well prior to FUSE 7.1.0.

After upgrading to 7.1.0 it seems to be fixed.

[pratik_patel]

Thanks, I can confirm this.

Regards,

Pratik

[iocanel]

Prior to 7.1.0 fabric was removing the features service provided by karaf on container managed by fabric. This was done mostly to prevent users installing features manually, since the fabric agent would remove them the next time it was triggered by a profile change.

As of 7.1.0 we added a fabric specific implementation of the features service that is read-only. This allows the use of features commands, compellers related to features and bundles that depend on the feature service.