sudo update-alternatives --install /usr/bin/java java $1/bin/java 200 \
--slave /usr/bin/jar jar $1/bin/jar \
--slave /usr/bin/jarsigner jarsigner $1/bin/jarsigner \
--slave /usr/bin/javac javac $1/bin/javac \
--slave /usr/bin/javadoc javadoc $1/bin/javadoc \
--slave /usr/bin/javah javah $1/bin/javah \
--slave /usr/bin/javap javap $1/bin/javap \
--slave /usr/bin/javaws javaws $1/bin/javaws

Then I just invoke the following command to select the JDK I want to use:

sudo update-alternatives --config java

I get presented with the following

There are 5 choices for the alternative java (providing /usr/bin/java).

  Selection    Path                                            Priority   Status
------------------------------------------------------------
  0            /usr/lib/jvm/ibm-java-x86_64-60/bin/java         200       auto mode
  1            /usr/lib/jvm/ibm-java-x86_64-60/bin/java         200       manual mode
  2            /usr/lib/jvm/ibm-java-x86_64-70/bin/java         200       manual mode
  3            /usr/lib/jvm/java-1.7.0-openjdk-amd64/bin/java   200       manual mode
  4            /usr/lib/jvm/jdk1.6.0_31/bin/java                200       manual mode
* 5            /usr/lib/jvm/jdk1.7.0_03/bin/java                200       manual mode

Press enter to keep the current choice[*], or type selection number:

And when you need to dynamically set JAVA_HOME to the appropriate path, use the following command:

export JAVA_HOME=$(readlink -f /usr/bin/java | sed "s:bin/java::")

Ma i prodotti Apple non migliorano il mondo: sono accessibili solo a persone dotate di capacità economica medio-alta, creano un sistema chiuso fatto di connettori non standard, di parti di ricambio non sostituibili in autonomia, di un App Store su cui è possibile pubblicare solo applicazioni che rispettano delle regole non pubbliche dettate  dalla moralità (economica) di Apple.

Le stesse persone che elogiano il fantastico mondo creato da Steve Jobs, sono quelle che si scagliano contro i metodi anti-competitivi di Microsoft, contro i protocolli chiusi e i formati proprietari. Ma una prigione, anche se ha i muri pitturati con paesaggi bellissimi, è pur sempre una prigione.

Per cui elogiamo pure Steve Jobs per il suo genio del marketing. Ma ricordiamoci anche di elogiare le persone che cercano veramente di cambiare il mondo in meglio con la tecnologia, cercando di liberare le informazioni, di renderle accessibili alle persone meno fortunate, di permettere ad ognuno di noi di esprimere la propria opinione liberamente.

<dependency>
	<groupId>net.dataforte.cassandra</groupId>
	<artifactId>cassandra-connection-pool</artifactId>
	<version>0.7.1</version>
</dependency>

I also wish to announce that I am currently working on Cassandra Armeria, an abstraction layer for Cassandra’s ever-changing Thrift API, and hope that this will provide the basis for Infinispan’s Cassandra support in the next release cycle (5.1.0).

https://github.com/tristantarrant/amanuensis

Amanuensis is a clustered IndexWriter for Infinispan which leverages JGroups’ channel multiplexing to stream index changes from slave nodes to a master node.

To use Amanuensis, add the appropriate dependency to your pom.xml:

<dependencies>
	<dependency>
		<groupId>net.dataforte.infinispan</groupId>
		<artifactId>amanuensis</artifactId>
		<version>0.0.2</version>
	</dependency>
</dependencies>
<repositories>
	<repository>
		<id>dataforte</id>
		<url>http://www.dataforte.net/listing/maven/releases</url>
		<snapshots><enabled>false</enabled></snapshots>
	</repository>
</repositories>

You also need to tell Infinispan to use Amanuensis’ JGroups channel lookup which enables muxed transport of messages.

<global>
		<transport clusterName="cluster">
			<properties>
				<property name="channelLookup" value="net.dataforte.infinispan.amanuensis.backend.jgroups.MuxChannelLookup" />
			</properties>
		</transport>
	</global>

In your code you need to initialize an instance of AmanuensisManager and obtain an InfinispanIndexWriter for each InfinispanDirectory you want to write to as follows:

import net.dataforte.infinispan.amanuensis.AmanuensisManager;
import net.dataforte.infinispan.amanuensis.IndexerException;
import net.dataforte.infinispan.amanuensis.InfinispanIndexWriter;

AmanuensisManager amanuensisManager = new AmanuensisManager(cacheManager);
amanuensisManager.setAnalyzer(analyzer);
InfinispanIndexWriter indexWriter = amanuensisManager.getIndexWriter(directory);

You then invoke methods on the InfinispanIndexWriter from any node and it will send changes to the Infinispan’s coordinator which will apply them to the directory. Index operations can also be batched together:

indexWriter.startBatch();
indexWriter.deleteDocuments(query);
indexWriter.addDocument(doc);
indexWriter.endBatch();

InfinispanIndexWriter is thread safe in that multiple threads can send batches individually.

The project’s site (together with JavaDocs) is available at: http://www.dataforte.net/software/amanuensis/index.html

I recommend upgrading to it.

Get it from my Maven repo.

New features in this release are:

• automatic host discovery with connection failover
• datasource implementation
• cleanups and bugfixes

From the silly capitalization you can already guess that it’s a CSV library. It differs from other libraries I’ve seen in that it doesn’t attempt to read the whole file in one go, but is uses an event-driven architecture so that your application can decide what to do with each row as it is parsed.

Docs are here: http://www.dataforte.net/software/cohesive/index.html