Well, warp-persist became Guice-Persist... and it is part of 3.0:
com.google.inject.extensions
guice-persist
3.0-rc3
com.google.inject.extensions
guice-servlet
3.0-rc3
cheers
Cristiano
On 10/03/11 12:01, Witold Czaplewski wrote:
IMO warp-persist is dead and Guice 3.0 should be final soon
IMO warp-persist is dead and Guice 3.0 should be final soon (rc3 is out now):
http://code.google.com/p/google-guice/downloads/list
Witold
Am Thu, 10 Mar 2011 15:31:19 +0100
schrieb Bas Gooren :
> Which is basically warp-persist, but integrated into guice. But as far
> as I know, it will be onl
Which is basically warp-persist, but integrated into guice. But as far
as I know, it will be only be integrated as of guice 3.0;
Bas
Op 10-3-2011 15:29, nino martinez wael schreef:
I'd go for guice persist if thats an option..
2011/3/10 Bas Gooren
Have a look at databinder or warp-persist f
I'd go for guice persist if thats an option..
2011/3/10 Bas Gooren
> Have a look at databinder or warp-persist for a better implementation.
>
> Should you go with your own implementation, do not forget to clear the
> ThreadLocal at the end of the request to prevent:
> a) leaking
> b) re-using an
Have a look at databinder or warp-persist for a better implementation.
Should you go with your own implementation, do not forget to clear the
ThreadLocal at the end of the request to prevent:
a) leaking
b) re-using an EntityManager from a previous request (most if not all
application servers u
Hi guys, is this an option to store the JPA entity manager for a wicket
webapp:
public class DBUtil {
private static EntityManagerFactory entityManagerFactory = Persistence
.createEntityManagerFactory("db");
private static ThreadLocal emHolder = new
ThreadLocal() {
p
