New issue 340 by jiunara...@gmail.com: RoomChatManager get initializes
twice even though the module says "Singleton"
http://code.google.com/p/emite/issues/detail?id=340
What steps will reproduce the problem?
1. Injecting to a class constructor
2. Injecting to a method
3.
What is the expected output? What do you see instead?
Expected as a Singleton RoomChatManager. RoomChatManager get initiated
twice which results to two times handling of invitation
What version of the product are you using? On what operating system?
emite0.6. Fedora13
Please provide any additional information below.
How I tackle the problem is providing annotation @Singleton in
RoomChatManager class, eventhough it is specified as Singleton in
MucModule. May be this is for the time being solution.
Any reply will be helpful.
Comment #2 on issue 340 by danigb: RoomChatManager get initializes twice
even though the module says "Singleton"
http://code.google.com/p/emite/issues/detail?id=340
Are you using the same injector? If so, we should add the @Singleton
annotation to the class itself.
But when the module says "in(Singleton.class)", if I am not wrong it means
that the injector would give singleton, which didn't.
And danigb is trying to say that singleton happens only for different
injector.
Correct me if I am wrong?
Comment #4 on issue 340 by ashward....@gmail.com: RoomChatManager get
initializes twice even though the module says "Singleton"
http://code.google.com/p/emite/issues/detail?id=340
Could this be something to do with the Suco compatibility layer?
I have a feeling (although may be wrong) that this could cause duplicate
singleton objects as it instantiates its own ginjector. Make sure that
you're not including the EmiteSuco GWT module (unless you're using it, of
course!).