A simple implementation based on the Java-Class LinkedHashMap can be found here:

LRUCache.java

If you need to access the cache with multiple threads, you can use the synchronized version:

LRUCache_sync.java

The difference between a webserver on the internet and a local machine is the accessibility and the need, to encrypt your sessions. This is normally done by providing a HTTPS-protocol access to your web-application.

Hubert Klein Ikkink has written a nice blog-post how this can be achieve with the jetty-maven plugin.

Click here for the blog-post

import org.slf4j.Logger;
@Inject
private Logger logger;

A little bit more complicated is the usage in a Tapestry-Service. Here an @Inject Annotation will fail, so you would have to get an instance for your logger from another source. One possibility would be to use a build-method in your Module class. But then, you would have to distribute such method for each service which should use a logger.

Tapestry helps you here and can contribute the needed Logger instance if you insert a constructor method to your service:

import org.slf4j.Logger;

private final Logger logger;

public MyServiceImpl(final Logger _logger){
     this.logger = _logger;
     this.logger.debug("Successfully initialized MyServiceImpl);
}

Your Service will now be initialized with a working instance of the Logger-class.

Java provides several build-in algorithms for symmetric-key cryptography (AES, DES …). To use those algorithms, you have to generate a secret-key and initialize a cipher for decryption and one for encryption with it.Those ciphers can now be used to crypt your data.

To simplify this task, I created a small library which provides the needed methods to decrypt and encrypt a String. There are several static methods to automatically initialize a crypter for a certain algorithm such as AES.

How to encrypt and decrypt a String:

Crypter myCrypter = Crypter.getAES_Crypter();
String encrypted = myCrypter.encrypt("my secret text");
String decrypted = myCrypter.decrypt(encrypted);

Download:

Library

Source

A big thank you goes out to the author of the used Base64-Coder: http://www.source-code.biz/

Bei unserem Projekt handelt es sich einerseits um eine Tapestry 5 Anwendung. Diese lässt sich auf jedem beliebigen Server mit installiertem Maven über den Befehl

mvn jetty:run

starten.

Auf der anderen Seite haben wir dann noch eine einfache Java-Anwendung, die eine Verbindung über einen Socket aufbaut.

Als Einführung ins Thema Maven haben wir uns das folgende Buch gekauft:
Maven: A Developer’s Notebook (Developer’s Notebooks)

Zwar behandelt es eine etwas ältere Maven Version, es ist aber gut für die Grundlagen geeignet.

It’s quite simple to use:

final CoordinateTool ct = new CoordinateTool();
final Coordinate coord = ct.getCoordinateForAddress(YOUR_ADDRESS);

Another feature is the possibility to load a route from A to B. You have the possibility to get this route as String or to save it to a File.

final CoordinateTool ct = new CoordinateTool();
final String route = ct.getRouteForAddresses(YOUR_ADDRESS, YOUR_DESTINATION);
ct.saveRouteForAddresses(YOUR_ADDRESS, YOUR_DESTINATION, FILENAME);

If you need the distance between two addresses or coordinates, you can use this “getDistanceBetween” method.

Download:

Library

Source.

Für den einfachen Einstieg habe ich dann mal nach einem Buch gesucht und folgendes gefunden:

Das Google Web Toolkit: Ajax-Applikationen mit Java

Die Bewertungen bei Amazon waren schon mal soweit ok und haben sich nun auch bestätigt. Der Autor erklärt in einem recht kleinem Rahmen die Grundlagen des Toolkits und was man damit so erreichen kann. Einziger Nachteil: es wird die Version 1.X behandelt. In der aktuellen 2.X Version sind einige Änderungen hinzugekommen, für einen Einstieg ist das Buch aber trotzdem gut geeignet.

Ein weiterer Pluspunkt ist der für ein Fachbuch doch sehr faire Preis

Amazon-Link

You can find the download on the project’s googlecode page: http://code.google.com/p/dummycreator

Seit einigen Wochen haben wir dann Redmine installiert und sind damit sehr zufrieden. Vor allem die Möglichkeit, direkt über die Webseite neue Projekte und dazugehörige SVN-Repositories anzulegen ist sehr praktisch. Wenn man nun noch ein solches Projekt als Privat markiert, erfolgt die Authentifizierung über die User-Datenbank von Redmine und somit haben nur eingetragene Entwickler des jeweiligen Projektes Zugriff.

Leider war die Installation von Redmine etwas aufwendiger, weswegen wir uns entschieden haben, eine entsprechende Dokumentation hierzu zu erstellen.

Anleitung

But there is a nice and easy possibility to build an all-in-one DVD which includes all editions (except Enterprise) and both versions (32 and 64bit)

Preparations

What you’ll need:

• Windows-PC
• Windows 7 x86 DVD
• Windows 7 x64 DVD
• Windows Automated Installation Kit (Download)

It doesn’t matter, which Windows 7 DVD you use because each contains all editions.

The first step is to download and install the Windows Automated Installation Kit.While doing this, you can copy the content of the x86 DVD to a folder on your disk.

Now you have to delete the \sources\ei.cfg file. This file defines, which edition of Windows 7 will be installed with the DVD. If it’s missing, you will see a menu while installation which allows you to choose the edition.

If this was your target, you can stop here and build the image.

Integrating the x64 versions into the x86 image

In this step, we will add the 64bit versions to our x86 image. You have to insert your x64 DVD in your drive or extract it to your disk. In the following sample, I will assume that your DVD drive is Z: and your local folder with the x86 data is e:\win7DVD.

To integrate the DVD to our local install.wim, we  have to execute the following command:

imagex /export Z:\sources\install.wim 1 e:\win7DVD\sources\install.wim "Windows 7 Home Basic x64"

This will add the Windows edition with the ID 1 to your local install.wim and rename it to “Windows 7 Home Basic x64″. This command has to be executed for each version, you want to add. Here is a list of the IDs:

1. Windows 7 Home Basic x64
2. Windows 7 Home Premium x64
3. Windows 7 Professional x64
4. Windows 7 Ultimate x64

We now have a DVD image with both 32bit and 64bit versions of Windows 7.

Adding additional language-support (optional)

For this step, you need the language-pack for Windows 7 (x86 and x64). Those can be downloaded from MSDN or Technet. If you have no account there, you’ll need to google these files

In the next step, we mount each Windows edition and include the language-pack. This has to be done 9 times (5 32bit editions, 4 64bit editions) and needs quite a long time… Just change the index-number in each pass. You need a temporary folder which will be used for the mounting process. In the example, I’ll use e:\tmp.

One more important thing:  you have to use the 32bit lb.cab for your 32bit editions (the first 5) and the 64bit lb.cab for the 64bit editions.

dism /mount-wim /wimfile:e:\win7DVD\sources\install.wim /index:1 /mountdir:e:\tmp
dism /image:e:\tmp /add-Package /PackagePath:e:\lb.cab
dism /unmount-wim /mountdir:e:\tmp /commit

Fixing the setup

We finally want to add the new language to our setup too. The needed language-packs are included on your WAIK DVD. There is only one WIM file we need to fix.

dism /mount-wim /wimfile:e:\win7DVD\sources\boot.wim /index:2 /MountDir:e:\tmp
dism /image:e:\tmp /add-package /packagepath:%WAIK_DVD_dir%WinPE_LangPacks\x86\de-de\lp.cab
dism /image:e:\tmp /add-package /packagepath:%WAIK_DVD_dir%WinPE_LangPacks\x86\de-de\winpe-setup_de-de.cab
dism /image:e:\tmp /add-package /packagepath:%WAIK_DVD_dir%WinPE_LangPacks\x86\de-de\winpe-setup-client_de-de.cab

Packing the final ISO

To finish the whole process, we have to pack the created data into an ISO file to write to a DVD.

oscdimg -lWin7AiO -m -u2 -be:\win7DVD\Boot\etfsboot.com e:\win7DVD\ Win7AiO.iso

Get the batch-script

I created a batch-script, which can easily be adapted to fit your needs. You then just have to run it from the Deployment Tools Command Prompt.

Download win7.bat