camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-659) XMPP endpoint should should auto-reconnect if it loses connection to the xmpp server
Date Wed, 06 Aug 2008 18:19:52 GMT


Claus Ibsen commented on CAMEL-659:

Anyone up for the task of creating a patch for the upgrade to smack 3.0.4. Michael, sorry
we have changed the camel-xmpp quite a bit lately so your original patch must be redone.

We have a maven repo with the 3.0.4 jars now. 

1) Add this to pom.xml
    <!-- ServiceMix repo -->
      <name>Apache ServiceMix Repository</name>

2) Upgrade to 3.0.4 in pom.xml

Then you are set. You will get some compilation errors since the API in 3.0 is different than

> XMPP endpoint should should auto-reconnect if it loses connection to the xmpp server
> ------------------------------------------------------------------------------------
>                 Key: CAMEL-659
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-xmpp
>    Affects Versions: 1.3.0, 1.4.0
>            Reporter: Michael Kahn
>             Fix For: 1.5.0
>         Attachments: camel-xmpp-smack_3_0_4.patch
> In 1.3.0, and related classes use the smack 2.2.1 API, and have a getConnection()
method that sets up and caches the xmpp connection and chat once when the endpoint is initialized.
If the network connection to the xmpp server is subsequently lost, attempts to route throw
an exception.  This makes use of this component on remote and roaming/wireless devices difficult.
> Smack API 3.0.4+ (the only version available for "official" download right now) should
auto-reconnect the XMPPConnection once it is created, reusing the same credentials from the
current login() session, however the API is not a drop-in replacement, there are a few differences.
 It also isn't in the maven repository yet - that maxes out at 2.2.1.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message