Home >> All >> org >> jabber

•	org.jabber.jabberbeans.* (30)

Package Samples:

• org.jabber.jabberbeans

Classes:

• RosterBean: RosterBean is a bean to gain and utilize the roster information in jabber. A 'Roster' is a list of users, a type of subscription list or address book, if you will. By using a roster, you can get the status of other users (online/offline, etc), subscribe and unsubscribe users, as well as change your own status. This bean hooks into an IQBean, it will not work until it is given a ConnectionBean to handle. RosterBean to ConnectionBean is a many to one relation - one ConnectionBean can have many RosterBeans, but if software wants to use more than a singular server connection, there is need for multiple ...
• Message: This is the data type that holds the data of a message. from the jabber documentation page here we get the message format (sorry, not in DTD format): The following metadata subject text thread id and the following content types main text of message + *
• PresenceBuilder: This class is an abstraction of presence packets - both incoming and outgoing. Incoming presence packets are notifications on a resource - they are sent by the remote client's server when that client has a status change. Outgoing presence packets are of two types. You send out your presence by sending a packet to the server with your new status. The second type is a subscribe request, where you request a remote user add you to their presence notifications.
• Presence: This class is an abstraction of presence packets - both incoming and outgoing. Incoming presence packets are notifications on a resource - they are sent by the remote client's server when that client has a status change. Outgoing presence packets are of two types. You send out your presence by sending a packet to the server with your new status. The second type is a subscribe request, where you request a remote user add you to their presence notifications.
• IQBean: IQBean is a bean used to utilize the 'iq' functionality of the jabber protocol. IQ is used for setting and reading values, including user information (for logging on). IQBean, like most of the other beans in jabberbeans, relies on ConnectionBean to provide the actual network socket to the server. IQBean will not operate until a connection is set.
• ConnectionAdapter: Convenience implementation of ConnectionListener. This is provided so that the ConnectionListener interface can be upgraded, without breaking backwards compatibility - extend ConnectionAdapter and you will gain do-nothing implementations of ConnectionListener's new events.
• PacketBuilder: A PacketBuilder is the base class for the builder of all the different Builder classes for Packet objects. Packet-derived objects require builders since they are immutable.
• PacketAdapter: PacketAdapter is a convenience class - it provides do-nothing implementations of the PacketListener class, so that clients will work with an upgraded jabberbeans with new packet events.
• User: User is the generic 'user' class. It holds all the unique information for identifying a user. It also provides resources to compare user objects and to get a URI quickly (toString)
• ConnectionBean: ConnectionBean is the main bean for jabberbeans. A ConnectionBean models the connection to the server, and all other beans rely on the ConnectionBean for server communication.
• IdentifierCounter: This counter is used to add a unique identifier to outgoing messages, so that the message can be linked to an error message should one be reported by the server.
• MessengerBean: MessengerBean is used to send and receive messages over a Connection. Connections are established by the ConnectionBean and required to use the MessengerBean.
• ConnectionListener: ConnectionListener is a listener interface, which you can implement and register to handle connection status change events, such as 'disconnected'.
• Packet: a packet is a single unit of information to be sent (or received) from the server. The two types of packets currently 'known' are IQ and Message.
• ContentPacket: a packet is a single unit of information to be sent (or received) from the server. The two types of packets currently 'known' are IQ and Message.
• IQPacketListener: This is an interface that extends an IQListener, so that it will filter out messages that don't concern the object. This is an adapter.
• RosterListener: RosterListener is an interface you can implement in a client to get any roster changes as notifications to your code.
• RosterAdapter: RosterAdapter is an abstract class you can extend to get any roster changes as notifications to your code.
• UserURI: UserURI is a subclass of user which allows for one resource to be specified. This makes it a complete URI.
• PacketListener: PacketListener is the interface the client implements to receive notification on incoming packets.
• EConnectionState: Enumeration for Connection Types
• PresenceBean

Home | Contact Us | Privacy Policy | Terms of Service