-
1. Re: @PostCosntruct not been called
mbarkley Dec 9, 2013 9:43 AM (in response to jose.alejandro)1 of 1 people found this helpfulHey Jose,
So just to confirm: you have a class annotated with @EntryPoint, in a package *.client.local.*, with a method annotated with @PostConstruct, and you have an ErraiApp.properties in your src/main/resource directory.
Have you verified that the entrypoint class is being instantiated? If not, can you try putting print statement in the beans constructor and seeing if the constructor is invoked?
-
2. Re: @PostCosntruct not been called
jose.alejandro Dec 9, 2013 12:54 PM (in response to mbarkley)Ok, so I was trying too many things at the same time because injecting the RootPanel alone and adding a dummy label works, the @PostConstruct gets called. The thing is that I'm trying the Presenter First approach for mvp where you have to write a presenter only using interfaces of the views and model. So, I have an interface on top of my @Templated class which would be my view implementation.
When I injected the view interface in my presenter I was hoping for errai to do some magic and pick up my @Templated implementation, which didn't work of course, and that experiment was the problem. I'll try to write a provider to make it work. The weird thing is that if I uncomment the interface injection it stops working but there is not erros in the console.
-
3. Re: @PostConstruct not been called
jose.alejandro Dec 9, 2013 5:59 PM (in response to mbarkley)Now it works! I didn't had to write a provider, actually the interface thing with the @Tamplated as implementation works very well. The problem was just that I was trying to inject my model from outside the client directory of the gwt module so... layer 8?
And my tests are working with jukito! you guys have made a great work, thank you for the help. Probably I will be back very soon asking more questions.
-
4. Re: @PostConstruct not been called
marius.gerwinn Dec 11, 2013 6:10 AM (in response to jose.alejandro)The problem was that I had an injection point to a class outside the client directory of the gwt module, everything is working now.
We running into the same problem from time to time. Especially when refactoring the codebase. The IOC generators does not produce a sufficient log for this problem.
Meanwhile the maven compiler (logLevel=TRACE) shows some warning for not reachable class.
Some more specific logging that points to the specific error would be a major improvement.