-
```
I (and probably some others) commonly invoke a generator by creating an
interface like:
{{{
interface BeanInfo{
Object getValue(String prop);
void setValue(String prop, Object value);
}
}…
-
```
This should work:
class Foo {
@Inject Foo(@Nullable @Named("unbound") String s, @Nullable Unimplemented
unimpl);
interface Unimplemented {}
}
null should be passed for both constructor para…
-
```
This should work:
class Foo {
@Inject Foo(@Nullable @Named("unbound") String s, @Nullable Unimplemented
unimpl);
interface Unimplemented {}
}
null should be passed for both constructor para…
-
```
This should work:
class Foo {
@Inject Foo(@Nullable @Named("unbound") String s, @Nullable Unimplemented
unimpl);
interface Unimplemented {}
}
null should be passed for both constructor para…
-
```
What steps will reproduce the problem?
1. Create a presenter that extends PresenterWidget that has multiple method or
field injected properties
2. Make sure autobind is true
3. Configure GIN a…
-
```
It should be a fairly straight-forward project to implement Guice AOP in
Gin. We can write subclasses of intercepted types and wrap matched methods
in our pre/post-processing. The interesting part…
-
```
It should be a fairly straight-forward project to implement Guice AOP in
Gin. We can write subclasses of intercepted types and wrap matched methods
in our pre/post-processing. The interesting part…
-
```
Add support for toInstance() injections.
Proposed Solution: Add lite runtime emulation in the package
com.google.inject.client.impl, implementing the Ginjector interface to
store the instances be…
-
```
I (and probably some others) commonly invoke a generator by creating an
interface like:
{{{
interface BeanInfo{
Object getValue(String prop);
void setValue(String prop, Object value);
}
}…
-
```
GWT 2.1 will provide a bunch of new classes that would greatly benefit from DI.
Having a GinModule that you can install() or reference in your
@GinModules/Ginjector would save us all defining th…