Regularly we see TomEE users wanting to deploy their app in Tomcat. Most of the time it is because they can’t select the container (company policy, cloud…).
Until now it needed some advanced knowledge, now it is easier :).
When testing a EE application you regularly rely on EJBContainer.
One issue is its lifecycle handling. Most of implementations map it (and that’s really correct) to the test lifecycle. In summary it looks like:
@BeforeClass
public static void boot() {
container = EJBContainer.createEJBContainer();
}
@AfterClass
public static void shutdown() {
container.close();
}
Extra module of commons-jcs provides some interesting basic features to use with JCache.
This post is just a quick overview of them.
Apache JCS project now has a new “openjpa” module. This one allows to use JCache (whatever implementation it is) as OpenJPA L2 cache.
JCache is the standard API for cache libraries. One common need is to
link the cache with another data source like a database (RDBMS or
NoSQL).
Of course JCache handles both access types: reader and writer.
This post is about readers.
JCache is out since some months and we already have some implementations popping out (Hazelcast implemented the main part, Infinispan passes all TCKs, commons-jcs passes standalone TCKs – CDI implementation in progress, Spring just integrated it etc…).
This article is just here to present the basic API but some more will come with the features which can make it interesting compared to more simple APIs (like a Map).
New posts here >>> rmannibucau.metawerx.net 