While working on a new JEE based project at the customer premise, I had to design and implement one of the most important parts of a product architecture – cache. Cache is defined as “a component that improves performance by transparently storing data such that future requests for that data can be served faster.” [Wikipedia]. There are several kinds of cache, and when you think of it, caching can be integrated in different layers of a product with different kind of cache: web browser cache, web Proxy cache, business-logic (applicative) cache, data access cache, DB cache etc. In this series I'll explore three different kinds of cache, which I integrated into this new product: web proxy cache, business cache, and data access cache. In this first part I'll concentrate on the web proxy cache.

Have been wondering how to build your application that have both Java and Scala sources with Maven?

Here you can find a tutorial from http://mackaz.de:

Build a mixed Scala 2.8/Java application and Eclipse Settings for this project

UPDATE: edited to make my meaning clearer (I hope).

Disclaimer: This post is about my opinion, not formal definitions.

In today's introduction to the Scala course. Adi asked what is functional programming. Here is Wikipedia's definition:

In computer science, functional programming is a programming paradigm that treats computation as the evaluation of mathematical functions and avoids state and mutable data

 http://code.joejag.com/2009/new-language-features-in-java-7/