[
https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s...
]
luca stancapiano updated ISPN-800:
----------------------------------
Description:
We need to import infinispan inside a OSGI repository. Tests are made with Felix.
I added the configuration to use infinispan inside a osgi repository. We need to ignore
all listed dependencies. With this configuration we can install infinispan-core.jar inside
OSGI. Its achievement will be as a base installation here:
https://github.com/flashboss/infinispan
I added the Import-Package because you are forced to put manually in Felix all
dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen
infinispan core working by default without all those libraries, so I think the same
achievement should be replicated in OSGI.
Inside the Import-Package tag I excluded those libraries so Infinispan core can be started
in default mode without errors. If we want use the replication in OSGI, it is enough add
manually the other packages (jgroups.jar etc etc)
Actually the core bundle can be installed. But to be used it needs theese projects be
installed as osgi bundles:
jboss transaction api 1.0.1.GA
(It is not yet a OSGI bundle. Waiting for a response to:
https://jira.jboss.org/browse/JBEE-67 )
jgroups 2.10.1.GA
(fixed in jgroups 2.12)
river 1.2.3.GA
(opened an issue for marshalling 1.4.0 in
https://jira.jboss.org/browse/JBMAR-118 and
https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml )
marshalling-api 1.2.3.GA
(opened an issue for marshalling 1.4.0 in
https://jira.jboss.org/browse/JBMAR-118 and
https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml )
jboss common core 2.2.14.GA
(fixing in 2.2.18-SNAPSHOT. See
https://jira.jboss.org/browse/JBCOMMON-116 )
jboss logging spi 2.0.5.GA
(added a jira issue in
https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in
the 2.2.0.CR2 version)
rhq plugin annotations 1.4.0.B01
(opened a feature request in
https://bugzilla.redhat.com/show_bug.cgi?id=657754 )
i18nlog 1.0.9
(sent a patch in
https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle
in the 1.0.10 version. Waiting for a response. Fixed in 1.14)
log4j 1.2.16
(that's ok...it is a osgi bundle ;))
We should make sure proper 'Import-Package' property is specified in the
MANIFEST.MF so that:
1- it fails to load obviously when there's any missing bundles that are essential in
using the very core functionality of Infinispan.
2 - it does not fail due to the dependency that is not really essential.
was:
We need to import infinispan inside a OSGI repository. Tests are made with Felix.
I added the configuration to use infinispan inside a osgi repository. We need to ignore
all listed dependencies. With this configuration we can install infinispan-core.jar inside
OSGI. Its achievement will be as a base installation here:
https://github.com/flashboss/infinispan
I added the Import-Package because you are forced to put manually in Felix all
dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen
infinispan core working by default without all those libraries, so I think the same
achievement should be replicated in OSGI.
Inside the Import-Package tag I excluded those libraries so Infinispan core can be started
in default mode without errors. If we want use the replication in OSGI, it is enough add
manually the other packages (jgroups.jar etc etc)
Actually the core bundle can be installed. But to be used it needs theese projects be
installed as osgi bundles:
jboss transaction api 1.0.1.GA
(It is not yet a OSGI bundle. Waiting for a response to:
https://jira.jboss.org/browse/JBEE-67 )
jgroups 2.10.1.GA
(fixed in jgroups 2.12)
river 1.2.3.GA
(opened an issue for marshalling 1.4.0 in
https://jira.jboss.org/browse/JBMAR-118 and
https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml )
marshalling-api 1.2.3.GA
(opened an issue for marshalling 1.4.0 in
https://jira.jboss.org/browse/JBMAR-118 and
https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml )
jboss common core 2.2.14.GA
(fixing in 2.2.18-SNAPSHOT. See
https://jira.jboss.org/browse/JBCOMMON-116 )
jboss logging spi 2.0.5.GA
(added a jira issue in
https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in
the 2.2.0.CR2 version)
rhq plugin annotations 1.4.0.B01
(opened a feature request in
https://bugzilla.redhat.com/show_bug.cgi?id=657754 )
i18nlog 1.0.9
(sent a patch in
https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle
in the 1.0.10 version. Waiting for a response)
log4j 1.2.16
(that's ok...it is a osgi bundle ;))
We should make sure proper 'Import-Package' property is specified in the
MANIFEST.MF so that:
1- it fails to load obviously when there's any missing bundles that are essential in
using the very core functionality of Infinispan.
2 - it does not fail due to the dependency that is not really essential.
i18nlo with the OSGI patch was released in the 1.14 version
Infinispan inside OSGI
----------------------
Key: ISPN-800
URL:
https://issues.jboss.org/browse/ISPN-800
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.2.0.CR1
Reporter: luca stancapiano
Assignee: Manik Surtani
Fix For: 5.0.0.ALPHA1, 5.0.0.Final
We need to import infinispan inside a OSGI repository. Tests are made with Felix.
I added the configuration to use infinispan inside a osgi repository. We need to ignore
all listed dependencies. With this configuration we can install infinispan-core.jar inside
OSGI. Its achievement will be as a base installation here:
https://github.com/flashboss/infinispan
I added the Import-Package because you are forced to put manually in Felix all
dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen
infinispan core working by default without all those libraries, so I think the same
achievement should be replicated in OSGI.
Inside the Import-Package tag I excluded those libraries so Infinispan core can be
started in default mode without errors. If we want use the replication in OSGI, it is
enough add manually the other packages (jgroups.jar etc etc)
Actually the core bundle can be installed. But to be used it needs theese projects be
installed as osgi bundles:
jboss transaction api 1.0.1.GA
(It is not yet a OSGI bundle. Waiting for a response to:
https://jira.jboss.org/browse/JBEE-67 )
jgroups 2.10.1.GA
(fixed in jgroups 2.12)
river 1.2.3.GA
(opened an issue for marshalling 1.4.0 in
https://jira.jboss.org/browse/JBMAR-118 and
https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml )
marshalling-api 1.2.3.GA
(opened an issue for marshalling 1.4.0 in
https://jira.jboss.org/browse/JBMAR-118 and
https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml )
jboss common core 2.2.14.GA
(fixing in 2.2.18-SNAPSHOT. See
https://jira.jboss.org/browse/JBCOMMON-116 )
jboss logging spi 2.0.5.GA
(added a jira issue in
https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed
in the 2.2.0.CR2 version)
rhq plugin annotations 1.4.0.B01
(opened a feature request in
https://bugzilla.redhat.com/show_bug.cgi?id=657754 )
i18nlog 1.0.9
(sent a patch in
https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle
in the 1.0.10 version. Waiting for a response. Fixed in 1.14)
log4j 1.2.16
(that's ok...it is a osgi bundle ;))
We should make sure proper 'Import-Package' property is specified in the
MANIFEST.MF so that:
1- it fails to load obviously when there's any missing bundles that are essential in
using the very core functionality of Infinispan.
2 - it does not fail due to the dependency that is not really essential.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira