[jira] Created: (CAMEL-3399) Tidying up strategy for managing resources in JMX

Tidying up strategy for managing resources in JMX - Key: CAMEL-3399 URL: https://issues.apache.org/jira/browse/CAMEL-3399 Project: Camel Issue Type: Improvement Components: camel-core

[jira] Commented: (CAMEL-3391) Upgrade to quartz 1.8.4

[ https://issues.apache.org/jira/browse/CAMEL-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968609#action_12968609 ] Jean-Baptiste Onofré commented on CAMEL-3391: - ServiceMix bundle for Quartz 1.8

[jira] Commented: (CAMEL-3398) Automatically imported beans are not taken into account in camel-blueprint (InterceptStrategy, LifecycleStrategy, etc...)

[ https://issues.apache.org/jira/browse/CAMEL-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968481#action_12968481 ] Guillaume Nodet commented on CAMEL-3398: This issue seems much more complicated tha

[jira] Assigned: (CAMEL-3295) camel-blueprint - Dependency Injection seems not working

[ https://issues.apache.org/jira/browse/CAMEL-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned CAMEL-3295: -- Assignee: Guillaume Nodet > camel-blueprint - Dependency Injection seems not working >

Hudson build is back to stable : Camel.trunk.fulltest #64

See

Hudson build is back to stable : Cam el.trunk.fulltest » Camel :: MINA #64

See

Hudson build is back to stable : Came l.trunk.fulltest » Camel :: Cometd #64

See

Hudson build is back to stable : Camel.tru nk.fulltest » Camel :: Example :: Axis #64

See

Hudson build is back to stable : Camel.trunk .fulltest » Camel :: Example :: CXF Proxy #64

See

Hudson build is back to stable : Camel.trun k.fulltest » Camel :: Integration Tests #64

See

Hudson build is back to stable : Came l.trunk.fulltest » Camel :: Jetty #64

See

Hudson build is back to stable : Camel.trunk.fulltest » Camel :: Example :: Report Incident :: WS-Security #64

See

Hudson build is back to stable : Camel.trunk.fu lltest » Camel :: Example :: Report Incident #64

See

Hudson build is back to stable : Camel .trunk.fulltest » Camel :: Restlet #64

See

[jira] Created: (CAMEL-3398) Automatically imported beans are not taken into account in camel-blueprint (InterceptStrategy, LifecycleStrategy, etc...)

Automatically imported beans are not taken into account in camel-blueprint (InterceptStrategy, LifecycleStrategy, etc...) - Key: CAMEL-3398 URL

[jira] Commented: (CAMEL-3396) Problem in message listener - Camel 2.5 + JMS + WebsphereMQ

[ https://issues.apache.org/jira/browse/CAMEL-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968407#action_12968407 ] Richard Kettelerij commented on CAMEL-3396: --- What Spring version do you use? The

[jira] Commented: (CAMEL-3279) Let custom Processor be managed in JMX when implementing ManagementAware

[ https://issues.apache.org/jira/browse/CAMEL-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968402#action_12968402 ] Richard Kettelerij commented on CAMEL-3279: --- Claus, this looks like a really nice

[jira] Resolved: (CAMEL-3271) packageScan does not work with camel-blueprint

[ https://issues.apache.org/jira/browse/CAMEL-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved CAMEL-3271. Resolution: Fixed Assignee: Guillaume Nodet Committing to https://svn.apache.org/repo

[jira] Work started: (CAMEL-3397) Support in-only semantic for file and ftp component

[ https://issues.apache.org/jira/browse/CAMEL-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-3397 started by Hadrian Zbarcea. > Support in-only semantic for file and ftp component > --- > >

[jira] Created: (CAMEL-3397) Support in-only semantic for file and ftp component

Support in-only semantic for file and ftp component --- Key: CAMEL-3397 URL: https://issues.apache.org/jira/browse/CAMEL-3397 Project: Camel Issue Type: Improvement Components: camel-

[jira] Created: (CAMEL-3396) Problem in message listener - Camel 2.5 + JMS + WebsphereMQ

Problem in message listener - Camel 2.5 + JMS + WebsphereMQ --- Key: CAMEL-3396 URL: https://issues.apache.org/jira/browse/CAMEL-3396 Project: Camel Issue Type: Bug Affects Versions

[jira] Commented: (CAMEL-3389) PackageHelper - issue with version numbers which contains non decimal

[ https://issues.apache.org/jira/browse/CAMEL-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967246#action_12967246 ] Peter Chandler commented on CAMEL-3389: --- Thanks, > PackageHelper - issue with versi

[jira] Resolved: (CAMEL-3386) Support destination address override by CxfProvider and CxfrsProvider

[ https://issues.apache.org/jira/browse/CAMEL-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Tam resolved CAMEL-3386. Resolution: Fixed Committed to trunk revision 1042677. > Support destination address override by

[jira] Resolved: (CAMEL-3395) Splitter - Exchange.CORRELATION_ID should point back to parent Exchange id

[ https://issues.apache.org/jira/browse/CAMEL-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3395. Resolution: Fixed trunk: 1042676. > Splitter - Exchange.CORRELATION_ID should point back to parent

[jira] Created: (CAMEL-3395) Splitter - Exchange.CORRELATION_ID should point back to parent Exchange id

Splitter - Exchange.CORRELATION_ID should point back to parent Exchange id -- Key: CAMEL-3395 URL: https://issues.apache.org/jira/browse/CAMEL-3395 Project: Camel Issue

[jira] Resolved: (CAMEL-3394) Splitter and Multicast EIP marks exchange as exhausted to early if exception was thrown from an evaluation

[ https://issues.apache.org/jira/browse/CAMEL-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3394. Resolution: Fixed trunk: 1042656. > Splitter and Multicast EIP marks exchange as exhausted to earl

[jira] Resolved: (CAMEL-3382) Publish OSGi EventAdmin events for important camel events

[ https://issues.apache.org/jira/browse/CAMEL-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved CAMEL-3382. Resolution: Fixed > Publish OSGi EventAdmin events for important camel events > ---

[jira] Created: (CAMEL-3394) Splitter and Multicast EIP marks exchange as exhausted to early if exception was thrown from an evaluation

Splitter and Multicast EIP marks exchange as exhausted to early if exception was thrown from an evaluation -- Key: CAMEL-3394 URL: https://issues.apache.org/ji

[jira] Resolved: (CAMEL-3381) CamelContext should be published in the OSGi registry

[ https://issues.apache.org/jira/browse/CAMEL-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved CAMEL-3381. Resolution: Fixed > CamelContext should be published in the OSGi registry > ---

Hudson build became unstable: Came l.trunk.fulltest » Camel :: MINA #63

See

Hudson build became unstable: Camel .trunk.fulltest » Camel :: Cometd #63

See

Hudson build became unstable: Camel.trunk. fulltest » Camel :: Example :: CXF Proxy #63

See

Hudson build became unstable: Camel .trunk.fulltest » Camel :: Jetty #63

See

Hudson build became unstable: Camel.trun k.fulltest » Camel :: Example :: Axis #63

See

Hudson build became unstable: Camel.trunk .fulltest » Camel :: Integration Tests #63

See

Hudson build became unstable: Camel. trunk.fulltest » Camel :: Restlet #63

See

Hudson build became unstable: Camel.trunk.ful ltest » Camel :: Example :: Report Incident #63

See

Hudson build is back to stable : Came l.trunk.fulltest » Camel :: HawtDB #63

See

Hudson build became unstable: Camel.trunk.fulltest » Camel :: Example :: Report Incident :: WS-Security #63

See

[jira] Resolved: (CAMEL-3279) Let custom Processor be managed in JMX when implementing ManagementAware

[ https://issues.apache.org/jira/browse/CAMEL-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3279. Resolution: Fixed trunk: 1042541. See example here https://cwiki.apache.org/confluence/display/CAM

[jira] Resolved: (CAMEL-3392) Using processor (non Service) with the process DSL should be managed in JMX

[ https://issues.apache.org/jira/browse/CAMEL-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3392. Resolution: Fixed trunk: 1042541. > Using processor (non Service) with the process DSL should be m