As you might have guessed we use cglib to wrap domain classes and proyx
them... This approach lets you "inject" localizing into existing systems..
So you do this:
@Translatable
public class Hotel {
private Long id;
private String name;
@Translate
private String description;
[...getter & setter...]
}
Translator translator = new Translator( Locale.GERMAN );
Hotel translatedHotel = translator.translate( hotel );
translatedHotel.getDescription(); // return description in german
translatedHotel.setDescription( "die Beschreibung" ); // persist german
description
And with a little code you can wrap this into your session and voila you
have localizing onthe fly:) Im working on this part as we speak..:)
Nino Saturnino Martinez Vazquez Wael wrote:
Hi
If you have trouble localizing your backend components, domain classes
etc... Look no futher:)
http://code.google.com/p/jpa-translator/ (licensed under apache)
Disclaimer, im one of the authors:) But it fits really great into
wicket and it's plugable too...
--
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
