camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "freetwix (JIRA)" <>
Subject [jira] Commented: (CAMEL-659) XMPP endpoint should should auto-reconnect if it loses connection to the xmpp server
Date Sat, 12 Jul 2008 14:16:01 GMT


freetwix commented on CAMEL-659:

hey claus,

the '_amq' is just an extension to the username providing a unique nickname of the amq user
in the muc. a nickname in a muc needs to be unique, else an exception will be raised.
you found the point what i meant by 'think it would be nice to add the nickname to the room
uri (like and parse it when consuming the room.'.
it would be ok to just use the username, too - it was just in my current project that the
same username already entered the muc and i really needed another nick for the camel user.
i just recommend the smack sources for documentation, and sorry, the '_amq' feature wasn't
really documented at all.


> 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