Build failed in Jenkins: Camel #1288

See Changes: [dkulp] Set the isCreateCamelContextPerClass on tests that can pass with it to speed up the tests [davsclaus] CAMEL-4283: Fixed dump as xml if message is already xml. [davsclaus] CAMEL-4282: Example and archetypes should enable JMX

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

See Changes: [dkulp] Set the isCreateCamelContextPerClass on tests that can pass with it to speed up the tests -- [INFO]

[jira] [Created] (CAMEL-4284) missing documentation in binary distribution tarballs

missing documentation in binary distribution tarballs - Key: CAMEL-4284 URL: https://issues.apache.org/jira/browse/CAMEL-4284 Project: Camel Issue Type: Bug Components: build syst

[jira] [Updated] (CAMEL-4255) Avoid using "\n" as line seperator while doing I/O and preferably stick to System.getProperty("line.separator")

[ https://issues.apache.org/jira/browse/CAMEL-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-4255: Summary: Avoid using "\n" as line seperator while doing I/O and preferably stick to System.getPrope

[jira] [Updated] (CAMEL-4275) Don't ignore java.io.File.delete() returned boolean value

[ https://issues.apache.org/jira/browse/CAMEL-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-4275: Summary: Don't ignore java.io.File.delete() returned boolean value (was: don't ignore/neglect java

[jira] [Commented] (CAMEL-4278) Additional methods added to example QuickfixConverters

[ https://issues.apache.org/jira/browse/CAMEL-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072894#comment-13072894 ] Claus Ibsen commented on CAMEL-4278: Why do you do a copy from 0 to length - 2 ? > Ad

[jira] [Resolved] (CAMEL-4283) dump as xml fails if message body is already xml

[ https://issues.apache.org/jira/browse/CAMEL-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4283. Resolution: Fixed > dump as xml fails if message body is already xml >

[jira] [Created] (CAMEL-4283) dump as xml fails if message body is already xml

dump as xml fails if message body is already xml Key: CAMEL-4283 URL: https://issues.apache.org/jira/browse/CAMEL-4283 Project: Camel Issue Type: Bug Components: camel-core Affec

[jira] [Commented] (CAMEL-4278) Additional methods added to example QuickfixConverters

[ https://issues.apache.org/jira/browse/CAMEL-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072848#comment-13072848 ] Pablo Venini commented on CAMEL-4278: - Modified the methods to obtain charset from exc

[jira] [Updated] (CAMEL-4278) Additional methods added to example QuickfixConverters

[ https://issues.apache.org/jira/browse/CAMEL-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pablo Venini updated CAMEL-4278: Attachment: patchfile_1.txt > Additional methods added to example QuickfixConverters >

[jira] [Commented] (CAMEL-4265) Fail to close stream in DefaultPropertiesResolver

[ https://issues.apache.org/jira/browse/CAMEL-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072842#comment-13072842 ] edge wang commented on CAMEL-4265: -- ok, thanks. > Fail to close stream in DefaultPropert

Re: [DISCUSS] - Dynamic to endpoint

On Thu, Jul 28, 2011 at 4:22 PM, Daniel Kulp wrote: >> Ah seems like I finally got it. By specifying all the possible >> expressions we should support. > > But doesn't that then require the camel-core to know about all the possible > sub-expressions?   Not exactly extensible. > > I personally thin

[jira] [Commented] (CAMEL-4265) Fail to close stream in DefaultPropertiesResolver

[ https://issues.apache.org/jira/browse/CAMEL-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072808#comment-13072808 ] Claus Ibsen commented on CAMEL-4265: When we are to cut a 2.8.1 release, we will look

[jira] [Resolved] (CAMEL-4282) Camel archetypes and examples should enable JMX for ActiveMQ

[ https://issues.apache.org/jira/browse/CAMEL-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4282. Resolution: Fixed > Camel archetypes and examples should enable JMX for ActiveMQ >

[jira] [Updated] (CAMEL-4265) Fail to close stream in DefaultPropertiesResolver

[ https://issues.apache.org/jira/browse/CAMEL-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4265: --- Fix Version/s: (was: 2.8.1) Please dont change the fix versions as its only committers who does t

[jira] [Commented] (CAMEL-4265) Fail to close stream in DefaultPropertiesResolver

[ https://issues.apache.org/jira/browse/CAMEL-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072802#comment-13072802 ] edge wang commented on CAMEL-4265: -- Can I modify it's fixed version, to add 2.8.1？ > Fai

[jira] [Updated] (CAMEL-4265) Fail to close stream in DefaultPropertiesResolver

[ https://issues.apache.org/jira/browse/CAMEL-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] edge wang updated CAMEL-4265: - Fix Version/s: 2.8.1 > Fail to close stream in DefaultPropertiesResolver > --

Re: How to correctly handle multiple consumers

Hi, If you just want the endpoint has the multiple thread to call the consumer process method, you can do it in your consumer. I don't know what the other use case that you may have. On Fri Jul 29 16:25:47 2011, E.Gherardini wrote: Hi all, I need to support multiple consumers inside the comp

[jira] [Resolved] (CAMEL-4095) camel-cxf - Using dynamic assigned ports for unit testing

[ https://issues.apache.org/jira/browse/CAMEL-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CAMEL-4095. Resolution: Fixed All the tests now use dynamic ports. > camel-cxf - Using dynamic assigned ports

[jira] [Updated] (CAMEL-4280) Out of date OSGi version

[ https://issues.apache.org/jira/browse/CAMEL-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated CAMEL-4280: Issue Type: Improvement (was: Bug) > Out of date OSGi version > --

[jira] [Created] (CAMEL-4282) Camel archetypes and examples should enable JMX for ActiveMQ

Camel archetypes and examples should enable JMX for ActiveMQ Key: CAMEL-4282 URL: https://issues.apache.org/jira/browse/CAMEL-4282 Project: Camel Issue Type: Improvement

[jira] [Resolved] (CAMEL-4280) Out of date OSGi version

[ https://issues.apache.org/jira/browse/CAMEL-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved CAMEL-4280. - Resolution: Fixed Fixed on trunk: revision 1152174. > Out of date OSGi version >

[jira] [Resolved] (CAMEL-3968) camel-soap - Add support for multiple parameters

[ https://issues.apache.org/jira/browse/CAMEL-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-3968. - Resolution: Fixed > camel-soap - Add support for multiple parameters > --

[jira] [Commented] (CAMEL-3968) camel-soap - Add support for multiple parameters

[ https://issues.apache.org/jira/browse/CAMEL-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072778#comment-13072778 ] Willem Jiang commented on CAMEL-3968: - Applied patch with thanks to Rich, I also fixed

Jenkins build is back to normal : Camel #1287

See

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

See

Jenkins build is back to normal : Camel » Camel :: Web #1287

See

[jira] [Created] (CAMEL-4281) would be good for FileEndpoint to implement BrowsableEndpoint (ditto any other components we can find that are easy to do)...

would be good for FileEndpoint to implement BrowsableEndpoint (ditto any other components we can find that are easy to do)... - Key: CAMEL-4281

[jira] [Updated] (CAMEL-4280) Out of date OSGi version

[ https://issues.apache.org/jira/browse/CAMEL-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated CAMEL-4280: Fix Version/s: (was: 2.8.1) (was: 2.7.4) > Out of date O

[jira] [Commented] (CAMEL-4280) Out of date OSGi version

[ https://issues.apache.org/jira/browse/CAMEL-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072747#comment-13072747 ] Jean-Baptiste Onofré commented on CAMEL-4280: - The OSGi 4.2.0 requires some up

How to correctly handle multiple consumers

Hi all, I need to support multiple consumers inside the component I am developing. I am wondering which is, in your opinion, the best way to handle it. I see two options: 1) create 1 Camel Consumer and, inside it, create multiple "endpoint consumers" (each in its own thread, using an ExecutorSer

[jira] [Resolved] (CAMEL-4276) camel-cxf OSGi bundle uses an incorrect CXF version range

[ https://issues.apache.org/jira/browse/CAMEL-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved CAMEL-4276. - Resolution: Fixed > camel-cxf OSGi bundle uses an incorrect CXF version range > -

[jira] [Commented] (CAMEL-4276) camel-cxf OSGi bundle uses an incorrect CXF version range

[ https://issues.apache.org/jira/browse/CAMEL-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072728#comment-13072728 ] Jean-Baptiste Onofré commented on CAMEL-4276: - Fixed on camel-2.7.x branch: re

[jira] [Commented] (CAMEL-4276) camel-cxf OSGi bundle uses an incorrect CXF version range

[ https://issues.apache.org/jira/browse/CAMEL-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072724#comment-13072724 ] Jean-Baptiste Onofré commented on CAMEL-4276: - Fixed on camel-2.8.x branch: re

[jira] [Commented] (CAMEL-4278) Additional methods added to example QuickfixConverters

[ https://issues.apache.org/jira/browse/CAMEL-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072710#comment-13072710 ] Bengt Rodehav commented on CAMEL-4278: -- The character set "UTF-8" is hardcoded in the