Go to file
Florian Schmaus 4c76f2652d Reworked OSGi support of Smack (SMACK-343)
Because of OSGi, no subproject of Smack (which is the same as a OSGi
bundle) must export a package that is already exported by another
subproject.

Therefore it was necessary to move the TCP and BOSH code into their own
packages: org.jivesoftware.smack.(tcp|bosh).

OSGi classloader restrictions also made it necessary to create a
Declarative Service for smack-extensions, smack-experimental and
smack-lagacy (i.e. smack subprojects which should be initialized), in
order to initialize them accordingly, as smack-core is, when used in a
OSGi environment, unable to load and initialize classes from other smack
bundles. OSGi's "Service Component Runtime" (SCR) will now take care of
running the initialization code of the particular Smack bundle by
activating its Declarative Service.

That is also the reason why most initialization related method now have an
additional classloader argument.

Note that due the refactoring, some ugly changes in XMPPTCPConnection
and its PacketReader and PacketWriter where necessary.
2014-05-15 16:09:37 +02:00
config Substitute MXParser with a call to XmlPullParserFactory 2014-02-20 13:48:36 +01:00
documentation Add missing HOXT entry in toc.html 2014-04-26 19:19:29 +02:00
resources Change keyringfile example to real file 2014-04-17 13:47:19 +02:00
smack-bosh Reworked OSGi support of Smack (SMACK-343) 2014-05-15 16:09:37 +02:00
smack-compression-jzlib Reworked OSGi support of Smack (SMACK-343) 2014-05-15 16:09:37 +02:00
smack-core Reworked OSGi support of Smack (SMACK-343) 2014-05-15 16:09:37 +02:00
smack-debug Make ProviderManager static 2014-05-11 09:27:41 +02:00
smack-experimental Reworked OSGi support of Smack (SMACK-343) 2014-05-15 16:09:37 +02:00
smack-extensions Reworked OSGi support of Smack (SMACK-343) 2014-05-15 16:09:37 +02:00
smack-jingle Make ProviderManager static 2014-05-11 09:27:41 +02:00
smack-legacy Reworked OSGi support of Smack (SMACK-343) 2014-05-15 16:09:37 +02:00
smack-resolver-dnsjava Reworked OSGi support of Smack (SMACK-343) 2014-05-15 16:09:37 +02:00
smack-resolver-javax Reworked OSGi support of Smack (SMACK-343) 2014-05-15 16:09:37 +02:00
smack-tcp Reworked OSGi support of Smack (SMACK-343) 2014-05-15 16:09:37 +02:00
.gitignore Migrate from Ant to Gradle (SMACK-265) 2014-02-14 18:46:33 +01:00
README.md Refactoring: All connection classes begin with XMPP now 2014-04-09 20:03:07 +02:00
build.gradle Reworked OSGi support of Smack (SMACK-343) 2014-05-15 16:09:37 +02:00
settings.gradle Prefix subprojects with 'smack-' 2014-04-28 19:44:14 +02:00

README.md

Smack

About

Smack is an Open Source, cross-platform, easy to use Java XMPP client library.

Communicate with XMPP servers to perform real-time collaboration, including instant messaging and group chat.

Key Advantages :

  • Extremely simple to use, yet powerful API. Sending a text message to a user can be accomplished in only a few lines of code:

    XMPPConnection connection = new XMPPTCPConnection("jabber.org");
    connection.connect();
    connection.login("mtucker", "password");
    Chat chat = ChatManager.getInstanceFor(connection)
        .createChat("jsmith@jivesoftware.com", new MessageListener() {
    
        public void processMessage(Chat chat, Message message) {
            System.out.println("Received message: " + message);
        }
    });
    chat.sendMessage("Howdy!");
    
  • Doesn't force you to code at the packet level, as other libraries do. Smack provides intelligent higher level constructs such as the Chat and Roster classes, which let you program more efficiently.

  • Does not require that you're familiar with the XMPP XML format, or even that you're familiar with XML.

  • Provides easy machine to machine communication. Smack lets you set any number of properties on each message, including properties that are Java objects.

  • Open Source under the Apache License, which means you can incorporate Smack into your commercial or non-commercial applications.

Smack is an Open Source XMPP (Jabber) client library for instant messaging and presence. A pure Java library, it can be embedded into your applications to create anything from a full XMPP client to simple XMPP integrations such as sending notification messages and presence-enabling devices.

Smack - an Ignite Realtime community project.

Bug Reporting

Only a few usrs have acces for for filling bugs in the tracker. New users should:

  1. Create a forums account (only e-mail is a requirement, you can skip all the other fields).
  2. Login to a forum account
  3. Press New in your toolbar and choose Discussion
  4. Choose the Smack Dev forum of Smack and add the tag 'bug_report' to your new post

Please search for your issues in the bug tracker before reporting.

Contact

The developeres hang around in #smack (freenode, IRC). Remeber that it may take some time (~hours) to get a response.

You can also reach us via the Smack Developers Forum.

Resources

Ignite Realtime

Ignite Realtime is an Open Source community composed of end-users and developers around the world who are interested in applying innovative, open-standards-based Real Time Collaboration to their businesses and organizations. We're aimed at disrupting proprietary, non-open standards-based systems and invite you to participate in what's already one of the biggest and most active Open Source communities.