[jira] [Commented] (CAMEL-12982) Add support for alternative RAW() syntax

[ https://issues.apache.org/jira/browse/CAMEL-12982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739986#comment-16739986 ] Tadayoshi Sato commented on CAMEL-12982: [~zregvart] [~davsclaus] Zoran's suggestion looks

[jira] [Commented] (CAMEL-13038) Type Convert Problem for XQuery Build In founction

[ https://issues.apache.org/jira/browse/CAMEL-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739723#comment-16739723 ] W.Y commented on CAMEL-13038: - Any Feedback? Thanks and Rgds Yan > Type Convert Problem for XQuery Build

[jira] [Resolved] (CAMEL-13046) Remove Camel-Openshift

[ https://issues.apache.org/jira/browse/CAMEL-13046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13046. -- Resolution: Fixed > Remove Camel-Openshift > -- > >

[jira] [Commented] (CAMEL-13046) Remove Camel-Openshift

[ https://issues.apache.org/jira/browse/CAMEL-13046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739449#comment-16739449 ] Andrea Cosentino commented on CAMEL-13046: -- This is the Openshift v2 component. Very old and

[jira] [Created] (CAMEL-13046) Remove Camel-Openshift

Andrea Cosentino created CAMEL-13046: Summary: Remove Camel-Openshift Key: CAMEL-13046 URL: https://issues.apache.org/jira/browse/CAMEL-13046 Project: Camel Issue Type: Task

[jira] [Comment Edited] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739421#comment-16739421 ] Jean-Baptiste Onofré edited comment on CAMEL-12980 at 1/10/19 1:59 PM:

[jira] [Commented] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739410#comment-16739410 ] Claus Ibsen commented on CAMEL-12980: - In Gregors example then with autoStartup=false, we should

[jira] [Commented] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739421#comment-16739421 ] Jean-Baptiste Onofré commented on CAMEL-12980: -- I would do the following: 1.

[jira] [Commented] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739409#comment-16739409 ] Jean-Baptiste Onofré commented on CAMEL-12980: -- I would extend to blueprint lifecycle. >

[jira] [Commented] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739411#comment-16739411 ] Grzegorz Grzybek commented on CAMEL-12980: -- Thanks. But because it's

[jira] [Commented] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739403#comment-16739403 ] Claus Ibsen commented on CAMEL-12980: - autoStartup=false means only the routes are not started.

[jira] [Commented] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739394#comment-16739394 ] Oliver Wulff commented on CAMEL-12980: -- I agree with you it's true if autoStart is false. In this

[jira] [Comment Edited] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739379#comment-16739379 ] Grzegorz Grzybek edited comment on CAMEL-12980 at 1/10/19 1:20 PM: --- I

[jira] [Updated] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-12980: - Priority: Critical (was: Major) > Bundle in 'Active' State but Camel Context not

[jira] [Commented] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739379#comment-16739379 ] Grzegorz Grzybek commented on CAMEL-12980: -- I understand the problem... CAMEL-10513 was a big

[jira] [Comment Edited] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739379#comment-16739379 ] Grzegorz Grzybek edited comment on CAMEL-12980 at 1/10/19 1:16 PM: --- I

[jira] [Updated] (CAMEL-13012) camel-olingo4 - AbstractFutureCallback generates NPE when response is a 401

[ https://issues.apache.org/jira/browse/CAMEL-13012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-13012: --- Fix Version/s: 2.21.5 > camel-olingo4 - AbstractFutureCallback generates NPE when response

[jira] [Commented] (CAMEL-12980) Bundle in 'Active' State but Camel Context not initialized

[ https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739262#comment-16739262 ] Oliver Wulff commented on CAMEL-12980: -- This issue becomes more critical when your camel route

[jira] [Resolved] (CAMEL-13012) camel-olingo4 - AbstractFutureCallback generates NPE when response is a 401

[ https://issues.apache.org/jira/browse/CAMEL-13012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-13012. Resolution: Fixed Thanks, [~phantomjinx] for reporting. > camel-olingo4 -

[jira] [Resolved] (CAMEL-13044) Camel-AWS MQ: it is not possible to set Broker "Public accessibility" parameter using createBroker command

[ https://issues.apache.org/jira/browse/CAMEL-13044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13044. -- Resolution: Fixed > Camel-AWS MQ: it is not possible to set Broker "Public

[jira] [Updated] (CAMEL-13044) Camel-AWS MQ: it is not possible to set Broker "Public accessibility" parameter using createBroker command

[ https://issues.apache.org/jira/browse/CAMEL-13044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13044: - Fix Version/s: 2.21.5 2.23.1 2.24.0

[jira] [Work logged] (CAMEL-13012) camel-olingo4 - AbstractFutureCallback generates NPE when response is a 401

[ https://issues.apache.org/jira/browse/CAMEL-13012?focusedWorklogId=183634=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-183634 ] ASF GitHub Bot logged work on CAMEL-13012: -- Author: ASF GitHub Bot