Package org.jivesoftware.smack.roster

Class AbstractRosterListener

java.lang.Object
org.jivesoftware.smack.roster.AbstractRosterListener
All Implemented Interfaces:
RosterListener
public abstract class AbstractRosterListener extends Object implements RosterListener
Provides empty implementations for RosterListener.
Since:
4.2

  • Constructor Details

  • Method Details

    • entriesAdded

      public void entriesAdded(Collection<Jid> addresses)
      Description copied from interface: RosterListener
      Called when roster entries are added.
      Specified by:
      entriesAdded in interface RosterListener
      Parameters:
      addresses - the XMPP addresses of the contacts that have been added to the roster.

    • entriesUpdated

      public void entriesUpdated(Collection<Jid> addresses)
      Description copied from interface: RosterListener
      Called when a roster entries are updated.
      Specified by:
      entriesUpdated in interface RosterListener
      Parameters:
      addresses - the XMPP addresses of the contacts whose entries have been updated.

    • entriesDeleted

      public void entriesDeleted(Collection<Jid> addresses)
      Description copied from interface: RosterListener
      Called when a roster entries are removed.
      Specified by:
      entriesDeleted in interface RosterListener
      Parameters:
      addresses - the XMPP addresses of the contacts that have been removed from the roster.

    • presenceChanged

      public void presenceChanged(Presence presence)
      Description copied from interface: RosterListener
      Called when the presence of a roster entry is changed. Care should be taken when using the presence data delivered as part of this event. Specifically, when a user account is online with multiple resources, the UI should account for that. For example, say a user is online with their desktop computer and mobile phone. If the user logs out of the IM client on their mobile phone, the user should not be shown in the roster (contact list) as offline since they're still available as another resource.

      To get the current "best presence" for a user after the presence update, query the roster: 

          String user = presence.getFrom();
    Presence bestPresence = roster.getPresence(user);
      That will return the presence value for the user with the highest priority and availability. Note that this listener is triggered for presence (mode) changes only (e.g presence of types available and unavailable. Subscription-related presence packets will not cause this method to be called.
      Specified by:
      presenceChanged in interface RosterListener
      Parameters:
      presence - the presence that changed.
      See Also: