Hi Michael About the ETA: As we are on the break of releasing a Camel 1.4 I don't think any new features will make it in. So any ETA is at the earliest in Camel 1.5.
Please fill in a JIRA request for this important improvement http://activemq.apache.org/camel/support.html And as we love contributions, the chance is higher that it will be fixed in Camel if people submit patches or vote on issues. http://activemq.apache.org/camel/contributing.html So if you fancy you could give it a go, or do some digging and comment on the JIRA ticket so we are in a better position to upgrade to the new 3.x API. Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: Michael Kahn [mailto:[EMAIL PROTECTED] Sent: 2. juli 2008 23:43 To: [email protected] Subject: Question about XMPP/Smack API/auto-reconnection Hi: I have been attempting to test the XMPP endpoint with Camel 1.3.0. I see that it uses the Smack 2.2.1 API, and is not 100% (drop-in) compatible with the smack 3.x API. The problem is that the 2.2.1 API does support the auto-reconnect feature (connect() and disconnect() methods) that the 3.x API does, and so if the XMPP connection goes down after your camelContext.start(), attempts to route will just throw an exception until you restart the process. Are there any plans to switch to Smack 3.0.x in order to support automatic reconnects? If so, what's the ETA? Thanks, Michael
