-
1. Re: Weld independence vs Guice Independece
nickarls Aug 31, 2010 5:54 AM (in response to nimo22)The normal scopes are backed by HTTP artifacts so there is a dep, yes. You can implement your own scopes/contexts.
Apps without deps to implementations (i.e only imports CDI stuff) is portable between all implementations that pass the TCK (in a perfect world).SE isn't defined in the current version of the spec, it's an extension
-
2. Re: Weld independence vs Guice Independece
nimo22 Aug 31, 2010 9:48 AM (in response to nimo22)Okay,
so javax.inject. (which handles DI) is portable the same as Guice is.
If I need the Context in DI (javax.enterprise.context.), then I can write own Scopes, which depends to the environment (for example, HTTP).thanks.
-
3. Re: Weld independence vs Guice Independece
mstruk.strukelj.parsek.net Aug 31, 2010 12:34 PM (in response to nimo22)Related to the topic ...
You can take a look at one CDI-Guice integration prototype: http://wiki.github.com/avrecko/weld-guiceconfig/
Maybe you find it useful, or have some ideas on how to improve it.
-
4. Re: Weld independence vs Guice Independece
pmuir Sep 1, 2010 10:24 AM (in response to nimo22)Take a look at our Java SE support :-)