--
You received this message because you are subscribed to the Google Groups "google-guice" group.
To post to this group, send email to google...@googlegroups.com.
To unsubscribe from this group, send email to google-guice...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
Hi team;
1 .Does Guice-persist have support for hibernate? it used to be there in warp-persist.
2. How can i get guice-persist with maven? do i have to compile it from the code? Can i use guice-persist with Guice 2.0?
--
Danji;
Does it mean the support for Hibernate api has been dropped? I didnt want to use the EntityManager api but native hibernate.
Dhanji.
--You received this message because you are subscribed to the Google Groups "google-guice" group.
To post to this group, send email to google...@googlegroups.com.
To unsubscribe from this group, send email to google-guice...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
Hi all,
I'm new to guice and guice-persist. I just got guice-persist
integrated into a war based project sitting on top of Tomcat 6. Seems
to work brilliantly. On my laptop, Tomcat starts up in 2 seconds which
includes starting hibernate and connecting to the database.
A couple notes so far:
http://code.google.com/p/google-guice/wiki/JPA
JpaModule should be JpaPersistModule
I'd really like to be able to instantiate my own EntityManager
implementation (I add a few handy methods to mine). Haven't figured
how to do that quite yet. What I do right now is @Singleton a bean
that wraps a @Inject EntityManager. Works well enough, but it would be
nice to be able to do this more cleanly.
I really wish there was more lifecycle support in guice (specifically
@PostConstruct/@PreDestroy) for my beans. I know James S did some work
with guiceyfruit, but it seems like it is a dead project. I'm looking
next into seeing how hard it will be to just put weld into the mix.
>> Yea, one issue here is the Guice team has not been able to agree on the
>> ideal solution for lifecycle (this debate has been ongoing since 2007). So
>> as an alternative, Bob created the TypeListener system that enables things
>> like guiceyfruit without directly implementing them.
>
> Yea, unfortunately guiceyfruit is no longer really developed and it
> isn't compatible with latest guice (the @PreDestroy stuff throws an
> illegalstateexception when gf tries to use some internal guice api's).
I apologise in advance for what I'm about to say, as clearly advocating one project in another's mailing list is bad form but....
Spring does pretty much what you need. Just use annotation scanning, and you're all set. Resteasy and co all hook into Spring and aren't invasive at all, and you also don't have to use custom frameworks maintained by a random guice enthusiasm who might or might not get bored with trying to make it play nice without polluting the pristine NIH 'core'. Additionally, Spring doesn't suffer from the elitism/purity mindset that guice does.
Guice is ideal for projects where you need DI and just DI (I use it for a lot of enterprise projects that don't require exposing as web services, have no web views, and have few third party dependencies). If you want to play nice with any other Java framework, it's a bad bet due to the mentality of 'google shall not pollute its code with open source/standards based filth'.
Sorry Bob, don't be mad at me!
Dunno what kind of machine you have,
but on my simple laptop (almost 1y old plain MacBP) the last JBoss6_m5 takes ~15sec to boot.
Considering you have all of JavaEE6 stuff up & ready (Weld, JPA2, JSF2, Rest, ...)
I would say that's not too bad.
I do admit we did not do our best for early JBoss5, but we did fix a bunch of stuff for JBoss6.
And hopefully we'll get that running even faster for GA release.
-Ales
p.s.: I lead the JBoss Microcontainer project ;-)