It would be convenient to have "Group" support to the RosterBean. That is, build a list of unique group names as the roster is loaded (and changed).
It may be even more useful for it to contains a mapping from group to a list/enumeration of the RosterItems in that group.
This would probably be part of a full-featured roster-presence bean. See http://www.geocrawler.com/lists/3/SourceForge/3959/0/5102771/
for more on that.
Logged In: YES
user_id=9752
*nod* thats the plan - I want to separate out 'low level
functionality' from things like a Presence/Roster manager -
mainly because people might not agree on what the
Presence/Roster manager does, and I don't want people
changing low-level classes to get different behavior for
their GUI app.