[jira] [Resolved] (CAMEL-4384) camel-jms - Request/Reply - Allow null messages to be send back as replies when using ObjectMessage type

[ https://issues.apache.org/jira/browse/CAMEL-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4384. Resolution: Cannot Reproduce Works fine already. I have added unit tests as well. > camel-jms - Re

[jira] [Created] (CAMEL-4384) camel-jms - Request/Reply - Allow null messages to be send back as replies when using ObjectMessage type

camel-jms - Request/Reply - Allow null messages to be send back as replies when using ObjectMessage type Key: CAMEL-4384 URL: https://issues.apache.org/jira/b

[jira] [Resolved] (CAMEL-3354) Allow bean component to return null which will be accepted as a new Message with an empty body

[ https://issues.apache.org/jira/browse/CAMEL-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3354. Resolution: Duplicate Fix Version/s: (was: 3.0.0) 2.9.0 This is a dup

[jira] [Assigned] (CAMEL-3354) Allow bean component to return null which will be accepted as a new Message with an empty body

[ https://issues.apache.org/jira/browse/CAMEL-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-3354: -- Assignee: Claus Ibsen > Allow bean component to return null which will be accepted as a new Mes

[jira] [Commented] (CAMEL-4209) Upgrade camel-guice to use guice 3.0

[ https://issues.apache.org/jira/browse/CAMEL-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091608#comment-13091608 ] Tim Chen commented on CAMEL-4209: - Hey Willem any update on this one? Maybe the dependency

[jira] [Resolved] (CAMEL-4264) The routeContext stack of DefaultUnitOfWork should be thread safe

[ https://issues.apache.org/jira/browse/CAMEL-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-4264. - Resolution: Fixed > The routeContext stack of DefaultUnitOfWork should be thread safe > -

[jira] [Updated] (CAMEL-4264) The routeContext stack of DefaultUnitOfWork should be thread safe

[ https://issues.apache.org/jira/browse/CAMEL-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-4264: Fix Version/s: 2.8.1 > The routeContext stack of DefaultUnitOfWork should be thread safe >

[jira] [Reopened] (CAMEL-4264) The routeContext stack of DefaultUnitOfWork should be thread safe

[ https://issues.apache.org/jira/browse/CAMEL-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reopened CAMEL-4264: - > The routeContext stack of DefaultUnitOfWork should be thread safe > ---

[jira] [Commented] (CAMEL-4264) The routeContext stack of DefaultUnitOfWork should be thread safe

[ https://issues.apache.org/jira/browse/CAMEL-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091512#comment-13091512 ] Willem Jiang commented on CAMEL-4264: - Merged the patch into camel 2.8.x branch. > T

Re: [DISCUSS] - Apache Camel 2.8.1 release

+1 Sent from a mobile device Am 25.08.2011 20:26 schrieb "Jon Anstey" : > Sounds good to me. > > +1 > > On Thu, Aug 25, 2011 at 5:28 AM, Claus Ibsen wrote: > >> Hi >> >> Its been 1 month since Camel 2.8.0 was released. >> And we have a 2.8 branch where we have merged bug fixes. >> >> I suggest th

Re: XML validation against encoding=UTF-8

Hello Santosh! Please use the user@ mailing list for this kind of questions. Could you please provide your XSD and sample XML files to make it easier for us to check this?! Best, Christian Sent from a mobile device Am 25.08.2011 16:59 schrieb "skompelly" : > > Hi, > > I have two Questions regar

[jira] [Created] (CAMEL-4383) StreamResequencer logs unhandled Exceptions at DEBUG level

StreamResequencer logs unhandled Exceptions at DEBUG level -- Key: CAMEL-4383 URL: https://issues.apache.org/jira/browse/CAMEL-4383 Project: Camel Issue Type: Bug Components:

[jira] [Commented] (CAMEL-4327) Resequencer should include option to never deliver out-of-sequence messages

[ https://issues.apache.org/jira/browse/CAMEL-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091197#comment-13091197 ] David Tombs commented on CAMEL-4327: I agree, that's a good idea. > Resequencer shoul

Re: [DISCUSS] - Apache Camel 2.8.1 release

Sounds good to me. +1 On Thu, Aug 25, 2011 at 5:28 AM, Claus Ibsen wrote: > Hi > > Its been 1 month since Camel 2.8.0 was released. > And we have a 2.8 branch where we have merged bug fixes. > > I suggest that we consider doing a 2.8.1 release in the near term, for > example in about 1 - 2 week

[jira] [Commented] (CAMEL-4264) The routeContext stack of DefaultUnitOfWork should be thread safe

[ https://issues.apache.org/jira/browse/CAMEL-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091195#comment-13091195 ] David Tombs commented on CAMEL-4264: This issue is biting my organization hard in a cr

Re: [DISCUSS] - Apache Camel 2.8.1 release

Very interested in getting both camel 2.8.x and amq 5.6 in SMX, so yes +1. On Aug 25, 2011, at 5:59 AM, Hadrian Zbarcea wrote: > +1 > > > On 08/25/2011 03:58 AM, Claus Ibsen wrote: >> Hi >> >> Its been 1 month since Camel 2.8.0 was released. >> And we have a 2.8 branch where we have merged bug

[jira] [Resolved] (CAMEL-4382) add support to set the cipher used for SFTP

[ https://issues.apache.org/jira/browse/CAMEL-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey resolved CAMEL-4382. Resolution: Fixed Fix Version/s: 2.9.0 > add support to set the cipher used for SFTP

[jira] [Commented] (CAMEL-4382) add support to set the cipher used for SFTP

[ https://issues.apache.org/jira/browse/CAMEL-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091148#comment-13091148 ] Jonathan Anstey commented on CAMEL-4382: Based on user query here http://camel.46

[jira] [Commented] (CAMEL-4382) add support to set the cipher used for SFTP

[ https://issues.apache.org/jira/browse/CAMEL-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091145#comment-13091145 ] Jonathan Anstey commented on CAMEL-4382: janstey@duffman:/x1/asf/camel/trunk/compo

[jira] [Created] (CAMEL-4382) add support to set the cipher used for SFTP

add support to set the cipher used for SFTP --- Key: CAMEL-4382 URL: https://issues.apache.org/jira/browse/CAMEL-4382 Project: Camel Issue Type: Improvement Affects Versions: 2.8.0 Repo

Jenkins build is back to normal : Camel » Camel :: JUEL #1310

See

Jenkins build is back to normal : Camel » Camel :: Restlet #1310

See

Jenkins build is back to normal : Camel » Camel :: SAXON #1310

See

Jenkins build is back to normal : Camel » Camel :: JMS #1310

See

Jenkins build is back to normal : Camel » Camel :: Spring Web Services #1310

See

Re: Camel 2.8.0 in fuse service mix

Hi ServiceMix 4.4 will use Camel 2.8.0 or 2.8.1. Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "skompelly" To: Subject: Camel 2.8.0 in fuse service mix Date: Thu, Aug 25, 2011 5:03 pm Hi As i

Camel 2.8.0 in fuse service mix

Hi As i know recently Camel 2.8.0 has been released. I am in need of using Fuse Service Mix with camel 2.8.0 version. I dont want to install the 2.8.0 bundles on top of existing service mix. Which release/version of service mix does it support camel 2.8.0 version? When that service mix relea

Re: Build failed in Jenkins: Camel » Camel :: Restlet #1309

Already fixed the build problems. I am currently running a new build. Sorry for the build failure. Christian Am 25.08.2011 16:40, schrieb Apache Jenkins Server: See -- [INFO] ---

XML validation against encoding=UTF-8

Hi, I have two Questions regarding encoding. 1) In router, consuming xml message with encoding=Cp1252 and validating this against xsd schema which has encoding as UTF-8 using camel *validator * component. The validator component is not validating the encoding=UTF-8, its accepting Cp1252, its not

Build failed in Jenkins: Camel » Camel :: JUEL #1309

See -- [INFO] [INFO] Building Camel :: JUEL [INFO]task-segment: [clean, install] [INFO] -

Build failed in Jenkins: Camel » Camel :: JMS #1309

See -- [INFO] [INFO] Building Camel :: JMS [INFO]task-segment: [clean, install] [INFO] ---

Build failed in Jenkins: Camel » Camel :: Spring Web Services #1309

See -- [INFO] [INFO] Building Camel :: Spring Web Services [INFO]task-segment: [clean, install] [INFO] -

Build failed in Jenkins: Camel » Camel :: SAXON #1309

See -- [INFO] [INFO] Building Camel :: SAXON [INFO]task-segment: [clean, install] [INFO] ---

Build failed in Jenkins: Camel » Camel :: Restlet #1309

See -- [INFO] [INFO] Building Camel :: Restlet [INFO]task-segment: [clean, install] [INFO] ---

[jira] [Work started] (CAMEL-4376) Deprecate DefaultEndpoint constructors that create partially constructed endpoints

[ https://issues.apache.org/jira/browse/CAMEL-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4376 started by Hadrian Zbarcea. > Deprecate DefaultEndpoint constructors that create partially constructed > endpoints >

[jira] [Commented] (CAMEL-4376) Deprecate DefaultEndpoint constructors that create partially constructed endpoints

[ https://issues.apache.org/jira/browse/CAMEL-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091030#comment-13091030 ] Hadrian Zbarcea commented on CAMEL-4376: Yes, shouldn't change in 2.8.1. The issu

[jira] [Updated] (CAMEL-4376) Deprecate DefaultEndpoint constructors that create partially constructed endpoints

[ https://issues.apache.org/jira/browse/CAMEL-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated CAMEL-4376: --- Fix Version/s: (was: 2.8.1) > Deprecate DefaultEndpoint constructors that create partiall

[jira] [Commented] (CAMEL-4381) Simplify ServiceSupport and introduce ServiceWithStatus interface to remove tangle between util and support

[ https://issues.apache.org/jira/browse/CAMEL-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091023#comment-13091023 ] Christian Schneider commented on CAMEL-4381: LifeCycleAwareService sounds good

[jira] [Commented] (CAMEL-4381) Simplify ServiceSupport and introduce ServiceWithStatus interface to remove tangle between util and support

[ https://issues.apache.org/jira/browse/CAMEL-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091016#comment-13091016 ] Claus Ibsen commented on CAMEL-4381: Maybe name it StatefulService as it is capable of

[jira] [Updated] (CAMEL-4381) Simplify ServiceSupport and introduce ServiceWithStatus interface to remove tangle between util and support

[ https://issues.apache.org/jira/browse/CAMEL-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated CAMEL-4381: --- Summary: Simplify ServiceSupport and introduce ServiceWithStatus interface to remove

[jira] [Created] (CAMEL-4381) Simplyfy ServiceSupport and introduce ServiceWithStatus interface to remove tangle between util and support

Simplyfy ServiceSupport and introduce ServiceWithStatus interface to remove tangle between util and support --- Key: CAMEL-4381 URL: https://issues.apache.org/

[jira] [Updated] (CAMEL-4379) upgrade to jetty 7.4.5.v20110725

[ https://issues.apache.org/jira/browse/CAMEL-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey updated CAMEL-4379: --- Fix Version/s: 2.8.1 > upgrade to jetty 7.4.5.v20110725 > >

[jira] [Created] (CAMEL-4380) FactoryFinder should support to find the class with a filter to get a right version of class

FactoryFinder should support to find the class with a filter to get a right version of class Key: CAMEL-4380 URL: https://issues.apache.org/jira/browse/CAMEL-4380

[jira] [Commented] (CAMEL-4379) upgrade to jetty 7.4.5.v20110725

[ https://issues.apache.org/jira/browse/CAMEL-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090966#comment-13090966 ] Jonathan Anstey commented on CAMEL-4379: Merged this to 2.8 branch in revision 116

[jira] [Commented] (CAMEL-4379) upgrade to jetty 7.4.5.v20110725

[ https://issues.apache.org/jira/browse/CAMEL-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090960#comment-13090960 ] Freeman Fang commented on CAMEL-4379: - Hi Jon, Would you please also backport this fi

Re: [DISCUSS] - Apache Camel 2.8.1 release

+1 On 08/25/2011 03:58 AM, Claus Ibsen wrote: Hi Its been 1 month since Camel 2.8.0 was released. And we have a 2.8 branch where we have merged bug fixes. I suggest that we consider doing a 2.8.1 release in the near term, for example in about 1 - 2 weeks. Apache ActiveMQ 5.6.0 is upgrading t

[jira] [Resolved] (CAMEL-4379) upgrade to jetty 7.4.5.v20110725

[ https://issues.apache.org/jira/browse/CAMEL-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey resolved CAMEL-4379. Resolution: Fixed janstey@duffman:/x1/asf/camel/trunk/parent$ svn ci -m "CAMEL-4379 - upgra

[jira] [Commented] (CAMEL-4379) upgrade to jetty 7.4.5.v20110725

[ https://issues.apache.org/jira/browse/CAMEL-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090957#comment-13090957 ] Jonathan Anstey commented on CAMEL-4379: FYI ServiceMix was recently updated to th

[jira] [Created] (CAMEL-4379) upgrade to jetty 7.4.5.v20110725

upgrade to jetty 7.4.5.v20110725 Key: CAMEL-4379 URL: https://issues.apache.org/jira/browse/CAMEL-4379 Project: Camel Issue Type: Task Reporter: Jonathan Anstey Assignee: Jonathan Anst

Re: Scope of org.apache.camel.spi

Hi Willem, as long as camel keeps compatible with most user code out there I see no big problems in having the refactoring earlier. Currently I already moved the management API to spi.management. As we discussed it is not so well placed there. So I propose to do the change like described bel

[jira] [Work started] (CAMEL-4378) camel-zookeper - Add osgi unit tests

[ https://issues.apache.org/jira/browse/CAMEL-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4378 started by Freeman Fang. > camel-zookeper - Add osgi unit tests > > > Key: CAMEL-4378 >

[jira] [Resolved] (CAMEL-4377) camel-zookeper - Add features.xml

[ https://issues.apache.org/jira/browse/CAMEL-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-4377. - Resolution: Fixed commit fix http://svn.apache.org/viewvc?rev=1161465&view=rev > camel-zookeper

Re: Scope of org.apache.camel.spi

Maybe we can consider to move to Camel 3.0 after Camel 2.9.0 is released, and leave this kind of package refactor to Camel 3.0. On 8/25/11 4:17 PM, Claus Ibsen wrote: On Thu, Aug 25, 2011 at 9:40 AM, Christian Schneider wrote: I have another proposal that could work better and is quite near

Re: [DISCUSS] - Apache Camel 2.8.1 release

On 8/25/11 4:12 PM, Claus Ibsen wrote: On Thu, Aug 25, 2011 at 10:05 AM, Jean-Baptiste Onofré wrote: Hi Claus, +1, I guess that we could merge some fixes in this release (for instance, the xstream 1.4.1 update, etc).WDYT ? I would actually discourage against bigger dependency updates such

Re: Scope of org.apache.camel.spi

On Thu, Aug 25, 2011 at 10:17 AM, Claus Ibsen wrote: > On Thu, Aug 25, 2011 at 9:40 AM, Christian Schneider > wrote: >> I have another proposal that could work better and is quite near to what we >> have. >> >> org.apache.camel.management.api We could consider placing the new ManagedXXX annotati

Re: Scope of org.apache.camel.spi

On Wed, Aug 24, 2011 at 7:55 PM, Christian Schneider wrote: > Actually JDk and spring are two very good examples how to not do it :-) > Yeah I guess using them as an example was "too easy" and it was late last evening. But often people would refer and look at giants such as the JDK and Spring. I

Re: [DISCUSS] - Apache Camel 2.8.1 release

It makes sense. I will take a look on the Jira to see what we could merge. Regards JB On 08/25/2011 10:12 AM, Claus Ibsen wrote: On Thu, Aug 25, 2011 at 10:05 AM, Jean-Baptiste Onofré wrote: Hi Claus, +1, I guess that we could merge some fixes in this release (for instance, the xstream 1.4

Re: [DISCUSS] - Apache Camel 2.8.1 release

On 2011-8-25, at 下午4:12, Claus Ibsen wrote: On Thu, Aug 25, 2011 at 10:05 AM, Jean-Baptiste Onofré t> wrote: Hi Claus, +1, I guess that we could merge some fixes in this release (for instance, the xstream 1.4.1 update, etc).WDYT ? I would actually discourage against bigger dependency up

Re: Scope of org.apache.camel.spi

On Thu, Aug 25, 2011 at 9:40 AM, Christian Schneider wrote: > I have another proposal that could work better and is quite near to what we > have. > > org.apache.camel.management.api > org.apache.camel.management.event > org.apache.camel.management.impl > This kind of split into fine grained sub p

[jira] [Commented] (CAMEL-4377) camel-zookeper - Add features.xml

[ https://issues.apache.org/jira/browse/CAMEL-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090860#comment-13090860 ] Freeman Fang commented on CAMEL-4377: - The zookeeper 3.3.3 is already OSGi friendly F

[jira] [Work started] (CAMEL-4377) camel-zookeper - Add features.xml

[ https://issues.apache.org/jira/browse/CAMEL-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4377 started by Freeman Fang. > camel-zookeper - Add features.xml > - > > Key: CAMEL-4377 >

Re: [DISCUSS] - Apache Camel 2.8.1 release

On Thu, Aug 25, 2011 at 10:05 AM, Jean-Baptiste Onofré wrote: > Hi Claus, > > +1, > > I guess that we could merge some fixes in this release (for instance, the > xstream 1.4.1 update, etc).WDYT ? > I would actually discourage against bigger dependency updates such as xstream 1.3 -> 1.4. There wa

Re: [DISCUSS] - Apache Camel 2.8.1 release

+1 Freeman On 2011-8-25, at 下午3:58, Claus Ibsen wrote: Hi Its been 1 month since Camel 2.8.0 was released. And we have a 2.8 branch where we have merged bug fixes. I suggest that we consider doing a 2.8.1 release in the near term, for example in about 1 - 2 weeks. Apache ActiveMQ 5.6.0 is up

Re: [DISCUSS] - Apache Camel 2.8.1 release

Hi Claus, +1, I guess that we could merge some fixes in this release (for instance, the xstream 1.4.1 update, etc).WDYT ? I will update ServiceMix to include Camel 2.8.1. Regards JB On 08/25/2011 09:58 AM, Claus Ibsen wrote: Hi Its been 1 month since Camel 2.8.0 was released. And we have

[DISCUSS] - Apache Camel 2.8.1 release

Hi Its been 1 month since Camel 2.8.0 was released. And we have a 2.8 branch where we have merged bug fixes. I suggest that we consider doing a 2.8.1 release in the near term, for example in about 1 - 2 weeks. Apache ActiveMQ 5.6.0 is upgrading to Apache Camel 2.8.x. And as we have a bug fixed i

[jira] [Commented] (CAMEL-2472) A Zookeeper Component for Camel

[ https://issues.apache.org/jira/browse/CAMEL-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090850#comment-13090850 ] Stephen Gargan commented on CAMEL-2472: --- Very welcome, glad to help. > A Zookeeper

Re: Scope of org.apache.camel.spi

I have another proposal that could work better and is quite near to what we have. org.apache.camel.management.api org.apache.camel.management.event org.apache.camel.management.impl eventually we could have org.apache.camel.management.api.annotations So the idea in this case is to have the modu

[jira] [Issue Comment Edited] (CAMEL-2472) A Zookeeper Component for Camel

[ https://issues.apache.org/jira/browse/CAMEL-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090830#comment-13090830 ] Claus Ibsen edited comment on CAMEL-2472 at 8/25/11 7:05 AM: -

[jira] [Commented] (CAMEL-4327) Resequencer should include option to never deliver out-of-sequence messages

[ https://issues.apache.org/jira/browse/CAMEL-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090831#comment-13090831 ] Chris VERBRUGGEN commented on CAMEL-4327: - I would not say to "throw away" late me

[jira] [Commented] (CAMEL-2472) A Zookeeper Component for Camel

[ https://issues.apache.org/jira/browse/CAMEL-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090830#comment-13090830 ] Claus Ibsen commented on CAMEL-2472: Thanks Stephan for this new great component. I h