From jira-events at lists.jboss.org Mon Mar 28 05:06:38 2011
Content-Type: multipart/mixed; boundary="===============8584928755070857082=="
MIME-Version: 1.0
From: =?utf-8?q?Galder_Zamarre=C3=B1o_=28JIRA=29_=3Cjira-events_at_lists=2Ejbos?=
 =?utf-8?q?s=2Eorg=3E?=
To: infinispan-issues at lists.jboss.org
Subject: [infinispan-issues] [JBoss JIRA] Commented: (ISPN-800) Infinispan
 inside OSGI
Date: Mon, 28 Mar 2011 05:06:38 -0400
Message-ID: <1608010804.2833.1301303198206.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com>
In-Reply-To: 1429563512.5334.1290644399106.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com

--===============8584928755070857082==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


    [ https://issues.jboss.org/browse/ISPN-800?page=3Dcom.atlassian.jira.pl=
ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12592079#com=
ment-12592079 ] =


Galder Zamarre=C3=B1o commented on ISPN-800:
---------------------------------------

Luca, any news on this? Is this finished already? Or do you need to do more=
 work on it?

> Infinispan inside OSGI
> ----------------------
>
>                 Key: ISPN-800
>                 URL: https://issues.jboss.org/browse/ISPN-800
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Core API
>            Reporter: luca stancapiano
>            Assignee: Galder Zamarre=C3=B1o
>             Fix For: 5.0.0.BETA1, 5.0.0.FINAL
>
>
> We need to import infinispan inside a OSGI repository. Tests are made wit=
h Felix.
> I added the configuration to use infinispan inside a osgi repository. We =
need to ignore all listed dependencies. With this configuration we can inst=
all infinispan-core.jar inside OSGI. Its achievement will be as a base inst=
allation here: https://github.com/flashboss/infinispan
> I added the Import-Package because you are forced to put manually in Feli=
x 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 co=
re can be started in default mode without errors. If we want use the replic=
ation in OSGI, it is enough add manually the other packages (jgroups.jar et=
c 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.jbo=
ss.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/J=
BMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/riv=
er/pom.xml )
> marshalling-api 1.2.3.GA
> (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/J=
BMAR-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-11=
6 )
> 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=
=3D657754 )
> i18nlog 1.0.9
> (sent a patch in https://sourceforge.net/projects/i18nlog . It could beco=
me a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.=
15)
> log4j 1.2.16
> (that's ok...it is a osgi bundle ;))
> jcip-annotations 1.0
> (I sent a patch via email to brian(a)briangoetz.com and a post in http://=
tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.ed=
u too. They responded to me. There is a OSGI version with a different artif=
act name. I changed the dependency in the pom.xml of the parent project)
> 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 e=
ssential 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


--===============8584928755070857082==--

