Closed GoogleCodeExporter closed 9 years ago
One remark:
After using an own compile script (instead of the compile button of the Google
Plugin
for Eclipse)
I got the "Guice creation errors" also when compiling to javascript and not
only in
hosted mode.
Original comment by shyb...@gmail.com
on 5 May 2009 at 9:57
tried it again today with guice 2.0 and gin r108.
everything works a expected now.
Original comment by marc.die...@gmail.com
on 3 Jun 2009 at 1:46
Original comment by bstoler+code@google.com
on 3 Jun 2009 at 3:35
Hello,
I have exactly the same problem (double configuration) and I use guice 2.0. I
also
use ubuntu 9.04, and tried compiling with GWT 1.64 and 1.7. I use eclipse and
the
google plugin to compile. I try to bind an interface D to DImpl in my module
exactly
as described above. The error I get is:
1) A binding to com.mycomp.D was already configured at
com.google.gwt.inject.rebind.LieToGuiceModule$ImplicitBindingModule.configure(Li
eToGuiceModule.java:70).
at com.mycomp.MyClientModule.configure(MyClientModule.java:14)
I really suspect a configration problem on my side as other people have
succeeded
compiling with the same settings, but I fail to see what is wrong.
Original comment by savolain...@gmail.com
on 9 Aug 2009 at 7:13
Like the previous commenter, I'm on Linux and compiling my GWT modules results
in the
same NullPointerException. Are you sure this issue has been fixed? GWT version
1.7,
Java version 1.6.0_16.
The first message in the following thread describes the problem I'm having in a
bit
more detail:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/38a173d8b
0d11359/f165bf1b88cab945?lnk=raot
Note that the author got things working because Eclipse was compiling the Gin
module
into a class file, which happened to be on the classpath of the GWT compiler.
But
surely you shouldn't need to compile client classes as normal Java before
compiling
the GWT modules?
Original comment by p.ledbr...@gmail.com
on 19 Aug 2009 at 3:33
Ooops, forgot to mention Gin version: r109
Original comment by p.ledbr...@gmail.com
on 19 Aug 2009 at 3:34
And in NetBeans 6.7.1 in order to get GIN overcome that
ClassNotFound/NullPointer
issue you also have to manually add "<project
folder>/build/web/WEB-INF/classes" path
into project classpath (i.e. among other libraries).
Original comment by Bulatju@gmail.com
on 5 Sep 2009 at 10:26
I have the same problem too. I set a breakpoint on the firstline of configure()
method and it stops twice.
Original comment by wbabac...@googlemail.com
on 26 May 2010 at 12:39
I see this as well. The first call seems fine but the second call has this as
part of the stack...
GinModuleAdapter.configure(Binder) line: 40
Elements$RecordingBinder.install(Module) line: 223
Elements.getElements(Stage, Iterable<Module>) line: 101
InjectorShell$Builder.build(Initializer, BindingProcessor, Stopwatch, Errors)
line: 135
InjectorBuilder.build() line: 102
Guice.createInjector(Stage, Iterable<Module>) line: 92
BindingsProcessor.validateModulesUsingGuice(List<Module>) line: 378
BindingsProcessor.process() line: 218
GinjectorGeneratorImpl.generate() line: 76
GinjectorGenerator.generate(TreeLogger, GeneratorContext, String) line: 47
It looks like the nested Guice infra is creating a dummy injector for
validation. Is this correct and, if so, then
can we be sure that the dummy injector created by Guice is discarded i.e. two
calls to configure() are actually
ok?
Original comment by steve.buikhuizen@gmail.com
on 2 Jun 2010 at 9:54
Yes, this should be fine. We run the validation injector (which is never saved)
and
then run the config again when we read the actual bindings.
Original comment by aragos
on 2 Jun 2010 at 8:58
Original issue reported on code.google.com by
marc.die...@gmail.com
on 5 May 2009 at 9:27