Possible problem with the DoubleList when compiled

zhongxan / emite

Automatically exported from code.google.com/p/emite

0 stars 0 forks source link

Possible problem with the DoubleList when compiled #285

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

This may be a problem with our integrated version, but I don't think so. So I'm 
raising an issue here to see if anyone else has encountered or can reproduce 
this problem.

Basically the double list which is used for the user selection for group chats 
and the like works absolutely fine in gwt development mode, but doesn't work 
correctly when the app is compiled (we're using pretty compilation too for 
certain reasons - not sure if that makes a difference) and deployed to tomcat. 
The problems I've noticed so far is that it's not possible to un-highlight 
users once they are highlighted, and if there are online and offline users in 
the list it only seems possible to transfer online users to the selected list. 
Very strange!

I haven't had a chance to try and replicate this in vanilla hablar yet so can't 
say for sure if this is an artifact of our integration.

Original issue reported on code.google.com by ashward....@gmail.com on 16 Jun 2010 at 6:37

GoogleCodeExporter commented 8 years ago

Original comment by ashward....@gmail.com on 16 Jun 2010 at 6:38

Added labels: Component-Hablar

GoogleCodeExporter commented 8 years ago

Does the problem replicate on any browser?
What version of GWT are you using?

Original comment by antonio....@gmail.com on 16 Jun 2010 at 7:34

GoogleCodeExporter commented 8 years ago

I tested it on FF3.6 and IE6 and it does the same thing so I don't think it's a 
browser specific issue.

Good thought on the gwt version. We're using gwt 2.0.2 (built using the gwt 
maven plugin). I'll try updating to the latest version and test again.

Original comment by ashward....@gmail.com on 16 Jun 2010 at 7:41

GoogleCodeExporter commented 8 years ago

Just tried recompiling and redeploying using gwt2.0.3 and still the same 
problem :(

Original comment by ashward....@gmail.com on 16 Jun 2010 at 9:03

GoogleCodeExporter commented 8 years ago

This issue was closed by revision r1487.

Original comment by ashward....@gmail.com on 17 Jun 2010 at 9:49

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

So what was the problem? A bug in comparison?

Original comment by antonio....@gmail.com on 17 Jun 2010 at 9:56

GoogleCodeExporter commented 8 years ago

The problem was that on our test environment we are using openfire backed by 
ldap and it seems this causes some RosterItem names to be null. This was 
causing a problem with the compareTo method which was comparing nulls and 
saying they were always different! TreeSet uses the compareTo method to find 
objects in the set (with contains() for example) and so was never finding items 
with a null name.

Original comment by ashward....@gmail.com on 17 Jun 2010 at 10:57

GoogleCodeExporter commented 8 years ago

Thanks for the explanation :-)

Original comment by antonio....@gmail.com on 17 Jun 2010 at 11:11