Migration path from JBOSS AS (Wildfly / jbosgi) to FUSE

[andrew_scully]

Hi all,

OSGI support was provided in JBOSS AS 7. For AS 8 (Wildfly), that support was moved to a separate sub-project (JBOSS OSGI). It now appears that this project has been killed.

The line being given out is that OSGI support for JBOSS is now supported purely via FUSE...

https://community.jboss.org/thread/237989

https://community.jboss.org/thread/238007

https://issues.jboss.org/browse/JBOSGI-762

...but it is not clear what the migration path is for this, so I'm looking for general advice.

The impression I'm getting is that FUSE appears to be an ESB rather than a fully-fledged application server. Therefore, to support OSGI is JBOSS, we would need to drop FUSE into Wildfly.

Am I on the correct lines here? Is this something that anybody else has done?

Any pointers appreciated muchly.

Cheers, Andy.

[davsclaus]

JBoss Fuse is labeled as an ESB, but in fact its based on Apache Karaf as the OSGi container. So you can run and deploy anything you want - just that its OSGi compliant.

Just use the minimal distribution of JBoss Fuse, to not include stuff you do not need installed out of the box. Otherwise you can customize what JBoss Fuse should included out of the box, in the etc configuration files.

Notice that Apache Karaf is by default using Apache Felix as the OSGi framework, and supporting Spring-DM 1.x and Apache Aries Blueprint as spring and blueprint.

[andrew_scully]

Thanks for the reply, Claus.

So FUSE is an OSGI runtime with extended functionality. If we wanted to migrate, we would need to drop any "bits" of Wildfly we are using into the deploy directory (as bundles).

[davsclaus]

Yeah if you are using any of the Wildfly bits in your applications.

Some bits like JPA / Hibernate / Servlet / WS (using Apache CXF) et all is also available from JBoss Fuse / Apache Karaf. But things like EJB's is not.