Tuesday, 21 October 2014
Infinispan 7.0.0.CR2 released!
===
===
Dear community, the second release candidate of Infinispan 7 is out!
As we approach final release, the main themes of this CR were bugfixes and enhancements, many related to Partition Handling
Also included:
-
Spring Cache Provider support for Spring 4.1 (thanks Sebastian Łaskawiec)
-
Infinispan caches can now be exposed as OSGI managed services (thanks Bilgin Ibryam for the contribution!)
-
Support for replicated caches on partition handling
-
Cache.size( ) method now returns count across entire cluster instead of local
For the complete list of changes, please consult the release notes
If you have any questions, ask it on our forums, mailing lists or directly on IRC. irc://irc.freenode.org/infinispan[ ]
Tags: spring partition handling osgi release candidate
Thursday, 06 March 2014
HotRod client in OSGi
Infinispan 7.0.0.Alpha1 makes it possible to easily run the HotRod client in an OSGi based container such as Karaf. Until this point there was no easy way to find out which libraries were required for the HotRod client to run in OSGi. These libraries then had to be installed manually and dynamic imports enabled for all the libraries. Last but not least, it was not possible to use the latest HotRod feature - remote queries.
The 7.0.0.Alpha1 introduces a "features" file which not only lists all dependencies required for correct functionality of the HotRod client in OSGi, but also makes it very easy to install the whole feature into Karaf (version 2.3.3 or 3.0) in just a few steps.
HotRod client feature file for OSGi
The feature file has been deployed into JBoss Nexus repository so it’s publicly available. It looks like this:
Installing the HotRod client feature in Karaf
The HotRod feature (either a simple HotRod client or HotRod client with remote query capabilities) can be installed in Karaf in the following steps:
There’s still one limitation with respect to remote querying, though. The remote query feauture requires a JMX-based connection to Infinispan server in order to be able to register a .protobin file, which holds the description of data types being transferred between the client and server. Since a remoting-jmx protocol is required and the existing remoting-jmx client does not work correctly in OSGi (see https://issues.jboss.org/browse/ISPN-4011), it is required to register the .protobin file in another way - not from inside the OSGi container. This will be fixed in one of the next releases.
Stay connected for news about running the whole Infinispan datagrid in OSGi, not only the HotRod client. This is work in progress.
Cheers,
Martin
Tags: hotrod osgi
