[
https://issues.apache.org/activemq/browse/CAMEL-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
freetwix updated CAMEL-659:
---------------------------
Attachment: camel-xmpp-smack_3_0_4.patch
Hey, this is a working port of camel-xmpp to smack 3.0.4. I didn't get the
maven repo stuff to work (as mentioned on the smack forum - see comments in the
pom.xml) - need to download it manual and tweak the local maven repo.
i added a todo for the nickname stuff. think it would be nice to add the
nickname to the room uri (like [EMAIL PROTECTED]/dude) and parse it when
consuming the room.
the code works with openfire 3.5.1/2. i will submit new changes as patches
here, too, and hereby grant all rights of the patch code to ASF.
hope the patch will help and are appreciating comments and more suggestions,
greets
freetwix
ps: tried to be javaesk though on the ruby path these days ...
> XMPP endpoint should should auto-reconnect if it loses connection to the xmpp
> server
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-659
> URL: https://issues.apache.org/activemq/browse/CAMEL-659
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-xmpp
> Affects Versions: 1.3.0
> Reporter: Michael Kahn
> Attachments: camel-xmpp-smack_3_0_4.patch
>
>
> In 1.3.0, XmppEndpoint.java 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.
