please take a look at this code and reopen the issue if you think there's something off with it.
https://fisheye.springsource.org/bro...2=2366&r1=2279
please take a look at this code and reopen the issue if you think there's something off with it.
https://fisheye.springsource.org/bro...2=2366&r1=2279
I just made a few minor changes:
https://fisheye.springsource.org/cha...ation/?cs=2367
However, we might be able to push down all locking into the underlying OrderedAwareLinkedHashSet implementation. At this point, the only relevant methods lacking a lock there are toArray().
-Mark
Mark Fisher
Spring Integration Lead
SpringSource, a division of VMware
http://www.springsource.com
http://www.springsource.org/spring-integration
http://blog.springsource.com/main/author/markf
Dan,
Have a look at the most recent changes:
https://fisheye.springsource.org/cha...ation/?cs=2368
All concurrent access safety is being managed within the OrderedAwareLinkedHashSet implementation now. Let me know what you think, and if you have time to bombard that collection with some similar tests, that would be really helpful.
Regards,
Mark
Mark Fisher
Spring Integration Lead
SpringSource, a division of VMware
http://www.springsource.com
http://www.springsource.org/spring-integration
http://blog.springsource.com/main/author/markf