[jira] [Commented] (CAMEL-11069) Make docker socket support usable

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941248#comment-15941248
 ] 

ASF GitHub Bot commented on CAMEL-11069:


GitHub user jhliptak reopened a pull request:

https://github.com/apache/camel/pull/1570

CAMEL-11069 docker socket support

pull request for https://issues.apache.org/jira/browse/CAMEL-11069 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jhliptak/camel CAMEL-11069

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1570.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1570


commit 142b6e59c0c8bba1926d28558a6feb1e20c711e8
Author: John Liptak 
Date:   2017-03-24T22:20:45Z

CAMEL-11069 docker socket support




> Make docker socket support usable
> -
>
> Key: CAMEL-11069
> URL: https://issues.apache.org/jira/browse/CAMEL-11069
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-docker
>Affects Versions: 2.18.3
> Environment: Linux docker enviroments
>Reporter: John Liptak
>Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Our docker environment does not expose the remote API socket over TCP, so I 
> wanted to get the unix:///var/run/docker.sock endpoint to work.
> This needed two changes:
> 1. The DockerClientProfile toUrl() method appends a :port which is not valid 
> for the unit port.
> 2. The URI parameter for socket has the wrong name and isn't in the valid URI 
> parameters map.
> I will submit a pull request once I have the issue #.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11069) Make docker socket support usable

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941249#comment-15941249
 ] 

ASF GitHub Bot commented on CAMEL-11069:


Github user jhliptak closed the pull request at:

https://github.com/apache/camel/pull/1570


> Make docker socket support usable
> -
>
> Key: CAMEL-11069
> URL: https://issues.apache.org/jira/browse/CAMEL-11069
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-docker
>Affects Versions: 2.18.3
> Environment: Linux docker enviroments
>Reporter: John Liptak
>Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Our docker environment does not expose the remote API socket over TCP, so I 
> wanted to get the unix:///var/run/docker.sock endpoint to work.
> This needed two changes:
> 1. The DockerClientProfile toUrl() method appends a :port which is not valid 
> for the unit port.
> 2. The URI parameter for socket has the wrong name and isn't in the valid URI 
> parameters map.
> I will submit a pull request once I have the issue #.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11069) Make docker socket support usable

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941247#comment-15941247
 ] 

ASF GitHub Bot commented on CAMEL-11069:


Github user jhliptak closed the pull request at:

https://github.com/apache/camel/pull/1570


> Make docker socket support usable
> -
>
> Key: CAMEL-11069
> URL: https://issues.apache.org/jira/browse/CAMEL-11069
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-docker
>Affects Versions: 2.18.3
> Environment: Linux docker enviroments
>Reporter: John Liptak
>Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Our docker environment does not expose the remote API socket over TCP, so I 
> wanted to get the unix:///var/run/docker.sock endpoint to work.
> This needed two changes:
> 1. The DockerClientProfile toUrl() method appends a :port which is not valid 
> for the unit port.
> 2. The URI parameter for socket has the wrong name and isn't in the valid URI 
> parameters map.
> I will submit a pull request once I have the issue #.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11069) Make docker socket support usable

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941246#comment-15941246
 ] 

ASF GitHub Bot commented on CAMEL-11069:


GitHub user jhliptak opened a pull request:

https://github.com/apache/camel/pull/1570

CAMEL-11069 docker socket support

pull request for https://issues.apache.org/jira/browse/CAMEL-11069 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jhliptak/camel CAMEL-11069

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1570.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1570


commit 142b6e59c0c8bba1926d28558a6feb1e20c711e8
Author: John Liptak 
Date:   2017-03-24T22:20:45Z

CAMEL-11069 docker socket support




> Make docker socket support usable
> -
>
> Key: CAMEL-11069
> URL: https://issues.apache.org/jira/browse/CAMEL-11069
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-docker
>Affects Versions: 2.18.3
> Environment: Linux docker enviroments
>Reporter: John Liptak
>Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Our docker environment does not expose the remote API socket over TCP, so I 
> wanted to get the unix:///var/run/docker.sock endpoint to work.
> This needed two changes:
> 1. The DockerClientProfile toUrl() method appends a :port which is not valid 
> for the unit port.
> 2. The URI parameter for socket has the wrong name and isn't in the valid URI 
> parameters map.
> I will submit a pull request once I have the issue #.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11069) Make docker socket support usable

[John Liptak (JIRA)]

John Liptak created CAMEL-11069:
---

 Summary: Make docker socket support usable
 Key: CAMEL-11069
 URL: https://issues.apache.org/jira/browse/CAMEL-11069
 Project: Camel
  Issue Type: New Feature
  Components: camel-docker
Affects Versions: 2.18.3
 Environment: Linux docker enviroments
Reporter: John Liptak
Priority: Minor


Our docker environment does not expose the remote API socket over TCP, so I 
wanted to get the unix:///var/run/docker.sock endpoint to work.

This needed two changes:
1. The DockerClientProfile toUrl() method appends a :port which is not valid 
for the unit port.
2. The URI parameter for socket has the wrong name and isn't in the valid URI 
parameters map.

I will submit a pull request once I have the issue #.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (CAMEL-11046) camel-undertow - Allow to consume from root path more without ending slash

[Zoran Regvart (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart reassigned CAMEL-11046:
-

Assignee: Zoran Regvart

> camel-undertow - Allow to consume from root path more without ending slash
> --
>
> Key: CAMEL-11046
> URL: https://issues.apache.org/jira/browse/CAMEL-11046
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-undertow
>Affects Versions: 2.18.3
>Reporter: Claus Ibsen
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 2.19.0
>
>
> So you can do
> {code}
> @Inject @Uri("undertow:http://0.0.0.0:8080;)
> private Endpoint undertow;
> {code}
> Without having to append ending slash, eg
> {code}
> @Inject @Uri("undertow:http://0.0.0.0:8080/;)
> private Endpoint undertow;
> {code}
> As otherwise you get a stacktrace
> {code}
> 2017-03-21 18:06:15,764 ERROR [stderr] (main) 
> java.lang.IllegalArgumentException: UT09: Path must be specified
> 2017-03-21 18:06:15,764 ERROR [stderr] (main) at 
> io.undertow.util.PathMatcher.addPrefixPath(PathMatcher.java:115)
> 2017-03-21 18:06:15,764 ERROR [stderr] (main) at 
> io.undertow.server.handlers.PathHandler.addPrefixPath(PathHandler.java:132)
> 2017-03-21 18:06:15,765 ERROR [stderr] (main) at 
> org.wildfly.extension.undertow.Host.registerHandler(Host.java:213)
> 2017-03-21 18:06:15,765 ERROR [stderr] (main) at 
> org.wildfly.extension.camel.undertow.CamelUndertowHostService$WildFlyUndertowHost.registerHandler(CamelUndertowHostService.java:187)
> 2017-03-21 18:06:15,765 ERROR [stderr] (main) at 
> org.apache.camel.component.undertow.UndertowConsumer.doStart(UndertowConsumer.java:73)
> 2017-03-21 18:06:15,765 ERROR [stderr] (main) at 
> org.wildfly.extension.camel.undertow.WildFlyUndertowComponent$WildFlyUndertowUndertowConsumer.doStart(WildFlyUndertowComponent.java:90)
> 2017-03-21 18:06:15,765 ERROR [stderr] (main) at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> 2017-03-21 18:06:15,766 ERROR [stderr] (main) at 
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3375)
> 2017-03-21 18:06:15,766 ERROR [stderr] (main) at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:3692)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-11068) Remove deprecated usage from Salesforce component

[Zoran Regvart (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart resolved CAMEL-11068.
---
   Resolution: Done
Fix Version/s: 2.19.0

> Remove deprecated usage from Salesforce component
> -
>
> Key: CAMEL-11068
> URL: https://issues.apache.org/jira/browse/CAMEL-11068
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-salesforce
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 2.19.0
>
>
> Salesforce component could use a bit less of the deprecated APIs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11068) Remove deprecated usage from Salesforce component

[Zoran Regvart (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart updated CAMEL-11068:
--
Summary: Remove deprecated usage from Salesforce component  (was: Remove 
some deprecated usage from Salesforce component)

> Remove deprecated usage from Salesforce component
> -
>
> Key: CAMEL-11068
> URL: https://issues.apache.org/jira/browse/CAMEL-11068
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-salesforce
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Minor
>
> Salesforce component could use a bit less of the deprecated APIs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11068) Remove some deprecated usage from Salesforce component

[Zoran Regvart (JIRA)]

Zoran Regvart created CAMEL-11068:
-

 Summary: Remove some deprecated usage from Salesforce component
 Key: CAMEL-11068
 URL: https://issues.apache.org/jira/browse/CAMEL-11068
 Project: Camel
  Issue Type: Improvement
  Components: camel-salesforce
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Priority: Minor


Salesforce component could use a bit less of the deprecated APIs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11067) camel-hystrix - Include default values in spring-boot auto configuration

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11067:

Attachment: Screen Shot 2017-03-24 at 9.20.39 PM.png

> camel-hystrix - Include default values in spring-boot auto configuration
> 
>
> Key: CAMEL-11067
> URL: https://issues.apache.org/jira/browse/CAMEL-11067
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-hystrix
>Reporter: Claus Ibsen
> Attachments: Screen Shot 2017-03-24 at 9.20.39 PM.png
>
>
> It would be good to include the default values in the spring boot auto 
> configuration.
> Currently its empty. See screenshot



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11067) camel-hystrix - Include default values in spring-boot auto configuration

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-11067:
---

 Summary: camel-hystrix - Include default values in spring-boot 
auto configuration
 Key: CAMEL-11067
 URL: https://issues.apache.org/jira/browse/CAMEL-11067
 Project: Camel
  Issue Type: Improvement
  Components: camel-hystrix
Reporter: Claus Ibsen
 Attachments: Screen Shot 2017-03-24 at 9.20.39 PM.png

It would be good to include the default values in the spring boot auto 
configuration.

Currently its empty. See screenshot




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-11066) Make salesforce authentication options simpler to configure

[Zoran Regvart (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart resolved CAMEL-11066.
---
   Resolution: Done
Fix Version/s: 2.19.0

> Make salesforce authentication options simpler to configure
> ---
>
> Key: CAMEL-11066
> URL: https://issues.apache.org/jira/browse/CAMEL-11066
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-salesforce
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 2.19.0
>
>
> Currently Camel Salesforce component has three different methods to 
> authenticate to Salesforce. Much of the logic that determines what method of 
> authentication to use is duplicated in {{SalesforceComponent}} or 
> {{SalesforceLoginConfig}}. This should be in one place and the options should 
> be documented better.
> This was partial done already in CAMEL-10938.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11066) Make salesforce authentication options simpler to configure

[Zoran Regvart (JIRA)]

Zoran Regvart created CAMEL-11066:
-

 Summary: Make salesforce authentication options simpler to 
configure
 Key: CAMEL-11066
 URL: https://issues.apache.org/jira/browse/CAMEL-11066
 Project: Camel
  Issue Type: Improvement
  Components: camel-salesforce
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Priority: Minor


Currently Camel Salesforce component has three different methods to 
authenticate to Salesforce. Much of the logic that determines what method of 
authentication to use is duplicated in {{SalesforceComponent}} or 
{{SalesforceLoginConfig}}. This should be in one place and the options should 
be documented better.
This was partial done already in CAMEL-10938.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11065) Cannot parse CSV record starting with separator character

[JIRA]

Tomáš Livora created CAMEL-11065:


 Summary: Cannot parse CSV record starting with separator character
 Key: CAMEL-11065
 URL: https://issues.apache.org/jira/browse/CAMEL-11065
 Project: Camel
  Issue Type: Bug
  Components: camel-bindy
Affects Versions: 2.18.3
Reporter: Tomáš Livora


Camel Bindy is not able to parse a CSV file where one value starts with a 
separator character. Example of such a record:

{code}
'text1',',text2',3
{code}

And the Java class used:

{code:title=Bar.java|borderStyle=solid}
@CsvRecord(separator = ",", quote = "'")
public class Record {

@DataField(pos = 1)
private String text1;

@DataField(pos = 2)
private String text2;

@DataField(pos = 3, pattern = ".##")
private BigDecimal number;

}
{code}

You will get an exception like this:
{code}
java.lang.IllegalArgumentException: Parsing error detected for field defined at 
the position: 3, line: 1
at 
org.apache.camel.dataformat.bindy.BindyCsvFactory.bind(BindyCsvFactory.java:213)
at 
org.apache.camel.dataformat.bindy.csv.BindyCsvDataFormat.unmarshal(BindyCsvDataFormat.java:173)
at 
org.apache.camel.processor.UnmarshalProcessor.process(UnmarshalProcessor.java:69)
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at 
org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
at 
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at 
org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:681)
at 
org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:609)
at 
org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:238)
at org.apache.camel.processor.Splitter.process(Splitter.java:108)
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at 
org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:460)
at 
org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:227)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:191)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:175)
at 
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:102)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NumberFormatException: null
at java.math.BigDecimal.(BigDecimal.java:494)
at java.math.BigDecimal.(BigDecimal.java:383)
at java.math.BigDecimal.(BigDecimal.java:806)
at 

[jira] [Resolved] (CAMEL-11024) service call eip: add an option to add additional configurations via spring-boot properties

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli resolved CAMEL-11024.
-
Resolution: Fixed

> service call eip:  add an option to add additional configurations via 
> spring-boot properties
> 
>
> Key: CAMEL-11024
> URL: https://issues.apache.org/jira/browse/CAMEL-11024
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot-starters
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.19.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-10938) Camel Salesforce : add an option to retrieve login information for testing purpose from env var or system properties

[Zoran Regvart (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart resolved CAMEL-10938.
---
Resolution: Fixed

Now the tests can be run configured with environment variables 
({{SALESFORCE_USERNAME}}), system properties ({{-Dsalesforce.username}}) or 
using the {{test-salesforce-login.properties}} file.

> Camel Salesforce : add an option to retrieve login information for testing 
> purpose from env var or system properties
> 
>
> Key: CAMEL-10938
> URL: https://issues.apache.org/jira/browse/CAMEL-10938
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-salesforce
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 2.19.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11024) service call eip: add an option to add additional configurations via spring-boot properties

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-11024:

Fix Version/s: (was: Future)

> service call eip:  add an option to add additional configurations via 
> spring-boot properties
> 
>
> Key: CAMEL-11024
> URL: https://issues.apache.org/jira/browse/CAMEL-11024
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot-starters
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.19.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Work started] (CAMEL-11024) service call eip: add an option to add additional configurations via spring-boot properties

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-11024 started by Luca Burgazzoli.
---
> service call eip:  add an option to add additional configurations via 
> spring-boot properties
> 
>
> Key: CAMEL-11024
> URL: https://issues.apache.org/jira/browse/CAMEL-11024
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot-starters
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.19.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11064) Add activemq-amqp to parent POM

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940343#comment-15940343
 ] 

ASF GitHub Bot commented on CAMEL-11064:


GitHub user jamesnetherton opened a pull request:

https://github.com/apache/camel/pull/1569

CAMEL-11064: Add activemq-amqp to parent POM

https://issues.apache.org/jira/browse/CAMEL-11064

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jamesnetherton/camel CAMEL-11064

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1569.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1569


commit 9880f442b3fdf88b27d10e523ca2d81db74bf887
Author: James Netherton 
Date:   2017-03-24T13:34:08Z

CAMEL-11064: Add activemq-amqp to parent POM




> Add activemq-amqp to parent POM
> ---
>
> Key: CAMEL-11064
> URL: https://issues.apache.org/jira/browse/CAMEL-11064
> Project: Camel
>  Issue Type: Task
>Affects Versions: 2.18.3, 2.19.0
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
>
> We have most ActiveMQ dependencies covered in the Camel parent POM. But, 
> activemq-amqp is currently missing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-11063) PGP Decryptor does not make Integrity check

[Franz Forsthofer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Franz Forsthofer resolved CAMEL-11063.
--
Resolution: Fixed

> PGP Decryptor does not make Integrity check
> ---
>
> Key: CAMEL-11063
> URL: https://issues.apache.org/jira/browse/CAMEL-11063
> Project: Camel
>  Issue Type: Bug
>  Components:  camel-crypto
>Reporter: Franz Forsthofer
>Assignee: Franz Forsthofer
> Fix For: 2.17.7, 2.18.4, 2.19.0
>
>
> A PGP Message can contain a Modification Code Detection Packet (MDC) which 
> contains a hash value of the clear text data. This hash value can be used to 
> check the integrity of the clear text data. Currently this check is not 
> executed in the unmarshall method of the PGP Data Formater.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11064) Add activemq-amqp to parent POM

[James Netherton (JIRA)]

James Netherton created CAMEL-11064:
---

 Summary: Add activemq-amqp to parent POM
 Key: CAMEL-11064
 URL: https://issues.apache.org/jira/browse/CAMEL-11064
 Project: Camel
  Issue Type: Task
Affects Versions: 2.18.3, 2.19.0
Reporter: James Netherton
Assignee: James Netherton
Priority: Minor


We have most ActiveMQ dependencies covered in the Camel parent POM. But, 
activemq-amqp is currently missing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (CAMEL-11063) PGP Decryptor does not make Integrity check

[Franz Forsthofer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Franz Forsthofer reassigned CAMEL-11063:


Assignee: Franz Forsthofer

> PGP Decryptor does not make Integrity check
> ---
>
> Key: CAMEL-11063
> URL: https://issues.apache.org/jira/browse/CAMEL-11063
> Project: Camel
>  Issue Type: Bug
>  Components:  camel-crypto
>Reporter: Franz Forsthofer
>Assignee: Franz Forsthofer
> Fix For: 2.17.7, 2.18.4, 2.19.0
>
>
> A PGP Message can contain a Modification Code Detection Packet (MDC) which 
> contains a hash value of the clear text data. This hash value can be used to 
> check the integrity of the clear text data. Currently this check is not 
> executed in the unmarshall method of the PGP Data Formater.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11063) PGP Decryptor does not make Integrity check

[Franz Forsthofer (JIRA)]

Franz Forsthofer created CAMEL-11063:


 Summary: PGP Decryptor does not make Integrity check
 Key: CAMEL-11063
 URL: https://issues.apache.org/jira/browse/CAMEL-11063
 Project: Camel
  Issue Type: Bug
  Components:  camel-crypto
Reporter: Franz Forsthofer
 Fix For: 2.17.7, 2.18.4, 2.19.0


A PGP Message can contain a Modification Code Detection Packet (MDC) which 
contains a hash value of the clear text data. This hash value can be used to 
check the integrity of the clear text data. Currently this check is not 
executed in the unmarshall method of the PGP Data Formater.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-10565) camel-undertow - Allow configuring thread pool and other options

[Nicola Ferraro (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicola Ferraro resolved CAMEL-10565.

Resolution: Done

> camel-undertow - Allow configuring thread pool and other options
> 
>
> Key: CAMEL-10565
> URL: https://issues.apache.org/jira/browse/CAMEL-10565
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-undertow
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
> Fix For: 2.19.0
>
>
> The undertow component creates 1 worker thread per CPU and this can be a 
> problem when running in docker containers on machines with 64+ cores (Java 
> containers currently see the number of CPUs of the host machine, even when 
> resource limitation is enabled).
> We need to add configuration options to the component to limit the number of 
> threads (and possibly other available options).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-10565) camel-undertow - Allow configuring thread pool and other options

[Nicola Ferraro (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicola Ferraro updated CAMEL-10565:
---
Fix Version/s: 2.19.0

> camel-undertow - Allow configuring thread pool and other options
> 
>
> Key: CAMEL-10565
> URL: https://issues.apache.org/jira/browse/CAMEL-10565
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-undertow
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
> Fix For: 2.19.0
>
>
> The undertow component creates 1 worker thread per CPU and this can be a 
> problem when running in docker containers on machines with 64+ cores (Java 
> containers currently see the number of CPUs of the host machine, even when 
> resource limitation is enabled).
> We need to add configuration options to the component to limit the number of 
> threads (and possibly other available options).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11028) camel-spark-rest - Adds duplicate content-type

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940146#comment-15940146
 ] 

ASF GitHub Bot commented on CAMEL-11028:


GitHub user jbridger opened a pull request:

https://github.com/apache/camel/pull/1568

CAMEL-11028: Avoid duplicating content-type headers for camel-spark-rest

Fix for: https://issues.apache.org/jira/browse/CAMEL-11028

Fix is as suggested in the Jira issue. Additionally, we changed the 
`DefaultSparkBindingTest.java` to exclude the `Content-Type` header when adding 
request headers to the camel headers map.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sky-uk/camel CAMEL-11028

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1568.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1568


commit ca175b9344113fef2bc3960611cf24513ae26afa
Author: Charlie McNeill, Karthikeyan Gurunathan and Jonathan Bridger 

Date:   2017-03-23T14:35:35Z

CAMEL-11028: Avoid duplicating content-type headers for camel-spark-rest




> camel-spark-rest - Adds duplicate content-type
> --
>
> Key: CAMEL-11028
> URL: https://issues.apache.org/jira/browse/CAMEL-11028
> Project: Camel
>  Issue Type: Bug
>  Components: rest
>Affects Versions: 2.18.3
>Reporter: Adam Dougal
>Assignee: Andrea Cosentino
> Fix For: 2.18.4, 2.19.0
>
>
> This is essentially the same as 
> https://issues.apache.org/jira/browse/CAMEL-9613 . When I send a request 
> containing a 'content-type' header it will get sent with duplicate values. 
> E.g. Content-Type: \[application/json, application/json\].
> My RouteBuilder is very simple at the moment:
> {code}
> restConfiguration().component("spark-rest").port(8585);
> rest("/").post("/charges").to("direct:charges");
> from("direct:charges").to("http://localhost:8080/charges?bridgeEndpoint=true=false;);
> {code}
> Having looked at the code I can see it being added in two places:
> https://github.com/apache/camel/blob/master/components/camel-spark-rest/src/main/java/org/apache/camel/component/sparkrest/DefaultSparkBinding.java#L73
> https://github.com/apache/camel/blob/master/components/camel-spark-rest/src/main/java/org/apache/camel/component/sparkrest/DefaultSparkBinding.java#L109
> Is this intended behaviour? If so, how would I disable it? Thanks



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11062) New camel-digitalocean component

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940140#comment-15940140
 ] 

ASF GitHub Bot commented on CAMEL-11062:


GitHub user tlehoux opened a pull request:

https://github.com/apache/camel/pull/1567

CAMEL-11062 : Camel digitalocean component

I've created a new component to work with DigitalOcean API 
(https://developers.digitalocean.com/). It's based on work I did at 
https://github.com/tlehoux/camel-digitalocean where you can find in Readme.md 
the documentation I wrote.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tlehoux/camel camel-digitalocean

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1567.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1567


commit 26f888c298dea5a7263088d6d8d0659c1993927a
Author: Thomas Lehoux 
Date:   2017-03-24T10:15:54Z

initial commit

commit 9687b4a1849e0ef411540a177a65f70d14dc1c08
Author: Thomas Lehoux 
Date:   2017-03-24T10:18:48Z

remove .gitignore file

commit ce4b160b5ca43f785a49820e725a53a3a5d7852c
Author: Thomas Lehoux 
Date:   2017-03-24T10:27:58Z

Refactor com.viwilo to org.apache.camel

commit a23398ae1f2534e1807a977d8b3c1cf74d1aca46
Author: Thomas Lehoux 
Date:   2017-03-24T10:29:48Z

Change version to 2.19.0-SNAPSHOT

commit c66cecd159afd960dc7cb1de79124b2997e52e06
Author: Thomas Lehoux 
Date:   2017-03-24T10:36:35Z

Add Ignore annotation for integration tests class.

commit d1c27bb0656e7d644818217d92f282dd8d825ca0
Author: Thomas Lehoux 
Date:   2017-03-24T10:37:31Z

Fixes enumeration issue.

commit 5fada2d10c6cc7f91ba2d2cdaddf6c8cc30642dd
Author: Thomas Lehoux 
Date:   2017-03-24T10:38:52Z

Refactor com.viwilo to org.apache.camel

commit 1664b0a370f142c970f7b63ce5dd89850fc04e50
Author: Thomas Lehoux 
Date:   2017-03-24T10:40:18Z

remove README.md and LICENSE




> New camel-digitalocean component
> 
>
> Key: CAMEL-11062
> URL: https://issues.apache.org/jira/browse/CAMEL-11062
> Project: Camel
>  Issue Type: New Feature
>Reporter: Thomas Lehoux
> Fix For: 2.19.0
>
>
> I've created a new component to work with DigitalOcean API 
> (https://developers.digitalocean.com/). It's based on work I did at 
> https://github.com/tlehoux/camel-digitalocean where you can find in Readme.md 
> the documentation I wrote.
> I will create a pull request.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11062) New camel-digitalocean component

[Thomas Lehoux (JIRA)]

Thomas Lehoux created CAMEL-11062:
-

 Summary: New camel-digitalocean component
 Key: CAMEL-11062
 URL: https://issues.apache.org/jira/browse/CAMEL-11062
 Project: Camel
  Issue Type: New Feature
Reporter: Thomas Lehoux
 Fix For: 2.19.0


I've created a new component to work with DigitalOcean API 
(https://developers.digitalocean.com/). It's based on work I did at 
https://github.com/tlehoux/camel-digitalocean where you can find in Readme.md 
the documentation I wrote.

I will create a pull request.





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11052) Soap11DataFormatAdapter throwing exception when using JAXB/JAX-WS generated code

[Kieran Simpson (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940126#comment-15940126
 ] 

Kieran Simpson commented on CAMEL-11052:


Thanks [~davsclaus]. I've started working on a patch.  Can this issue be 
assigned to me?

> Soap11DataFormatAdapter throwing exception when using JAXB/JAX-WS generated 
> code
> 
>
> Key: CAMEL-11052
> URL: https://issues.apache.org/jira/browse/CAMEL-11052
> Project: Camel
>  Issue Type: Bug
>  Components: camel-soap
>Affects Versions: 2.18.3
>Reporter: Kieran Simpson
>Priority: Minor
>  Labels: soap11
>
> When using WsImport, the structure of the generated Exception class for SOAP 
> Faults have only a two arg constructor generated ie:
> {code:java}public MyException(String message,  faultInfo) {}{code}
> However in {{Soap11DataFormatAdapter::createExceptionFromFault}} the code is 
> trying to get a reference to the single argument constructor, before it tries 
> to find/use the two argument constructor, which would cause a 
> {{NoSuchMethodException}} to be thrown as no such constructor exits on the 
> class.
> The solution is to move the {{messageConstructor}} variable inside the catch 
> block.  So we try to get/use the two arg constructor and if that fails then 
> we try to get/use the single argument constructor, which is the real logic of 
> that try/catch block anyway.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-11061) service call eip: add an option to set global defaults

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli resolved CAMEL-11061.
-
Resolution: Fixed

> service call eip: add an option to set global defaults
> --
>
> Key: CAMEL-11061
> URL: https://issues.apache.org/jira/browse/CAMEL-11061
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.19.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11061) service call eip: add an option to set global defaults

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11061:
---

 Summary: service call eip: add an option to set global defaults
 Key: CAMEL-11061
 URL: https://issues.apache.org/jira/browse/CAMEL-11061
 Project: Camel
  Issue Type: Improvement
  Components: camel-spring-boot
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor
 Fix For: 2.19.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11058) camel-olingo2 component doesn't support OData 3.0

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940048#comment-15940048
 ] 

ASF GitHub Bot commented on CAMEL-11058:


Github user dmvolod closed the pull request at:

https://github.com/apache/camel/pull/1564


> camel-olingo2 component doesn't support OData 3.0
> -
>
> Key: CAMEL-11058
> URL: https://issues.apache.org/jira/browse/CAMEL-11058
> Project: Camel
>  Issue Type: Task
>  Components: camel-olingo2
>Affects Versions: 2.19.0
> Environment: Created a sample to demonstrate this incompatibility
> https://github.com/dmvolod/test-olingo2-odata3
>Reporter: Dmitry Volodin
>Assignee: Andrea Cosentino
>Priority: Trivial
> Fix For: 2.19.0
>
>
> Component camel-olingo2 doesn't support OData 3.0 as olingo-odata2 library 
> never did it.
> It would be nice to remove this info (OData 3.0) from the documentation and 
> component descriptions



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11056) Create a new camel-olingo4 component for supporting OData 4.0

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940049#comment-15940049
 ] 

ASF GitHub Bot commented on CAMEL-11056:


Github user dmvolod closed the pull request at:

https://github.com/apache/camel/pull/1562


> Create a new camel-olingo4 component for supporting OData 4.0
> -
>
> Key: CAMEL-11056
> URL: https://issues.apache.org/jira/browse/CAMEL-11056
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-olingo2
>Affects Versions: 2.19.0
>Reporter: Dmitry Volodin
>Assignee: Andrea Cosentino
>Priority: Minor
>  Labels: odata4, olingo4, rest_api
> Fix For: 2.19.0
>
>
> We required Camel Olingo component with the OData 4.0 support as now OData 
> Version 4.0 is OASIS based and widely using standard. For backward 
> compatibility we've migrated current camel-olingo2 to the new camel-olingo4 
> component, except deprecated and some new features.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-11058) camel-olingo2 component doesn't support OData 3.0

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-11058.
--
Resolution: Fixed

> camel-olingo2 component doesn't support OData 3.0
> -
>
> Key: CAMEL-11058
> URL: https://issues.apache.org/jira/browse/CAMEL-11058
> Project: Camel
>  Issue Type: Task
>  Components: camel-olingo2
>Affects Versions: 2.19.0
> Environment: Created a sample to demonstrate this incompatibility
> https://github.com/dmvolod/test-olingo2-odata3
>Reporter: Dmitry Volodin
>Assignee: Andrea Cosentino
>Priority: Trivial
> Fix For: 2.19.0
>
>
> Component camel-olingo2 doesn't support OData 3.0 as olingo-odata2 library 
> never did it.
> It would be nice to remove this info (OData 3.0) from the documentation and 
> component descriptions



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (CAMEL-11058) camel-olingo2 component doesn't support OData 3.0

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino reassigned CAMEL-11058:


Assignee: Andrea Cosentino

> camel-olingo2 component doesn't support OData 3.0
> -
>
> Key: CAMEL-11058
> URL: https://issues.apache.org/jira/browse/CAMEL-11058
> Project: Camel
>  Issue Type: Task
>  Components: camel-olingo2
>Affects Versions: 2.19.0
> Environment: Created a sample to demonstrate this incompatibility
> https://github.com/dmvolod/test-olingo2-odata3
>Reporter: Dmitry Volodin
>Assignee: Andrea Cosentino
>Priority: Trivial
> Fix For: 2.19.0
>
>
> Component camel-olingo2 doesn't support OData 3.0 as olingo-odata2 library 
> never did it.
> It would be nice to remove this info (OData 3.0) from the documentation and 
> component descriptions



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11058) camel-olingo2 component doesn't support OData 3.0

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-11058:
-
Fix Version/s: 2.19.0

> camel-olingo2 component doesn't support OData 3.0
> -
>
> Key: CAMEL-11058
> URL: https://issues.apache.org/jira/browse/CAMEL-11058
> Project: Camel
>  Issue Type: Task
>  Components: camel-olingo2
>Affects Versions: 2.19.0
> Environment: Created a sample to demonstrate this incompatibility
> https://github.com/dmvolod/test-olingo2-odata3
>Reporter: Dmitry Volodin
>Assignee: Andrea Cosentino
>Priority: Trivial
> Fix For: 2.19.0
>
>
> Component camel-olingo2 doesn't support OData 3.0 as olingo-odata2 library 
> never did it.
> It would be nice to remove this info (OData 3.0) from the documentation and 
> component descriptions



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11044) CLONE - EndpointHelper.resolveReferenceListParameter should not return immutable lists

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11044:

Fix Version/s: 2.19.0

> CLONE - EndpointHelper.resolveReferenceListParameter should not return 
> immutable lists
> --
>
> Key: CAMEL-11044
> URL: https://issues.apache.org/jira/browse/CAMEL-11044
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.17.3
>Reporter: Chandra Bose Renganathan
>Priority: Minor
> Fix For: 2.19.0
>
>
> EndpointHelper.resolveReferenceListParameter still sometimes return immutable 
> lists.
> Following is an example URL:
> jetty:http://0.0.0.0:8080/entitlements/v1?matchOnUriPrefix=true=true=myFilter
> Since it already has filter, when the component adds crossOriginFilter, it 
> fails with UnsupportedOperationException.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11044) CLONE - EndpointHelper.resolveReferenceListParameter should not return immutable lists

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11044:

Estimated Complexity: Novice  (was: Unknown)

> CLONE - EndpointHelper.resolveReferenceListParameter should not return 
> immutable lists
> --
>
> Key: CAMEL-11044
> URL: https://issues.apache.org/jira/browse/CAMEL-11044
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.17.3
>Reporter: Chandra Bose Renganathan
>Priority: Minor
> Fix For: 2.19.0
>
>
> EndpointHelper.resolveReferenceListParameter still sometimes return immutable 
> lists.
> Following is an example URL:
> jetty:http://0.0.0.0:8080/entitlements/v1?matchOnUriPrefix=true=true=myFilter
> Since it already has filter, when the component adds crossOriginFilter, it 
> fails with UnsupportedOperationException.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11044) CLONE - EndpointHelper.resolveReferenceListParameter should not return immutable lists

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940026#comment-15940026
 ] 

Claus Ibsen commented on CAMEL-11044:
-

Contributions is welcome as a github PR
http://camel.apache.org/contributing

> CLONE - EndpointHelper.resolveReferenceListParameter should not return 
> immutable lists
> --
>
> Key: CAMEL-11044
> URL: https://issues.apache.org/jira/browse/CAMEL-11044
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.17.3
>Reporter: Chandra Bose Renganathan
>Priority: Minor
> Fix For: 2.19.0
>
>
> EndpointHelper.resolveReferenceListParameter still sometimes return immutable 
> lists.
> Following is an example URL:
> jetty:http://0.0.0.0:8080/entitlements/v1?matchOnUriPrefix=true=true=myFilter
> Since it already has filter, when the component adds crossOriginFilter, it 
> fails with UnsupportedOperationException.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (CAMEL-11044) CLONE - EndpointHelper.resolveReferenceListParameter should not return immutable lists

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reassigned CAMEL-11044:
---

Assignee: (was: Claus Ibsen)

> CLONE - EndpointHelper.resolveReferenceListParameter should not return 
> immutable lists
> --
>
> Key: CAMEL-11044
> URL: https://issues.apache.org/jira/browse/CAMEL-11044
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.17.3
>Reporter: Chandra Bose Renganathan
>Priority: Minor
> Fix For: 2.19.0
>
>
> EndpointHelper.resolveReferenceListParameter still sometimes return immutable 
> lists.
> Following is an example URL:
> jetty:http://0.0.0.0:8080/entitlements/v1?matchOnUriPrefix=true=true=myFilter
> Since it already has filter, when the component adds crossOriginFilter, it 
> fails with UnsupportedOperationException.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11052) Soap11DataFormatAdapter throwing exception when using JAXB/JAX-WS generated code

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940023#comment-15940023
 ] 

Claus Ibsen commented on CAMEL-11052:
-

You are welcome to work on a github PR
http://camel.apache.org/contributing

> Soap11DataFormatAdapter throwing exception when using JAXB/JAX-WS generated 
> code
> 
>
> Key: CAMEL-11052
> URL: https://issues.apache.org/jira/browse/CAMEL-11052
> Project: Camel
>  Issue Type: Bug
>  Components: camel-soap
>Affects Versions: 2.18.3
>Reporter: Kieran Simpson
>Priority: Minor
>  Labels: soap11
>
> When using WsImport, the structure of the generated Exception class for SOAP 
> Faults have only a two arg constructor generated ie:
> {code:java}public MyException(String message,  faultInfo) {}{code}
> However in {{Soap11DataFormatAdapter::createExceptionFromFault}} the code is 
> trying to get a reference to the single argument constructor, before it tries 
> to find/use the two argument constructor, which would cause a 
> {{NoSuchMethodException}} to be thrown as no such constructor exits on the 
> class.
> The solution is to move the {{messageConstructor}} variable inside the catch 
> block.  So we try to get/use the two arg constructor and if that fails then 
> we try to get/use the single argument constructor, which is the real logic of 
> that try/catch block anyway.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11058) camel-olingo2 component doesn't support OData 3.0

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11058:

Issue Type: Task  (was: Bug)

> camel-olingo2 component doesn't support OData 3.0
> -
>
> Key: CAMEL-11058
> URL: https://issues.apache.org/jira/browse/CAMEL-11058
> Project: Camel
>  Issue Type: Task
>  Components: camel-olingo2
>Affects Versions: 2.19.0
> Environment: Created a sample to demonstrate this incompatibility
> https://github.com/dmvolod/test-olingo2-odata3
>Reporter: Dmitry Volodin
>Priority: Trivial
>
> Component camel-olingo2 doesn't support OData 3.0 as olingo-odata2 library 
> never did it.
> It would be nice to remove this info (OData 3.0) from the documentation and 
> component descriptions



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11056) Create a new camel-olingo4 component for supporting OData 4.0

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-11056:
-
Fix Version/s: 2.19.0

> Create a new camel-olingo4 component for supporting OData 4.0
> -
>
> Key: CAMEL-11056
> URL: https://issues.apache.org/jira/browse/CAMEL-11056
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-olingo2
>Affects Versions: 2.19.0
>Reporter: Dmitry Volodin
>Assignee: Andrea Cosentino
>Priority: Minor
>  Labels: odata4, olingo4, rest_api
> Fix For: 2.19.0
>
>
> We required Camel Olingo component with the OData 4.0 support as now OData 
> Version 4.0 is OASIS based and widely using standard. For backward 
> compatibility we've migrated current camel-olingo2 to the new camel-olingo4 
> component, except deprecated and some new features.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11060) dn shouldn't be strictly required for Spring LDAP component

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940022#comment-15940022
 ] 

Claus Ibsen commented on CAMEL-11060:
-

You are welcome to work on a github PR
http://camel.apache.org/contributing

> dn shouldn't be strictly required for Spring LDAP component
> ---
>
> Key: CAMEL-11060
> URL: https://issues.apache.org/jira/browse/CAMEL-11060
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Ken Geis
>Priority: Minor
>
> I set a base DN in my LdapContextSource underlying the LdapTemplate. It's 
> redundant to need to set it in my route, but if I don't, the 
> SpringLdapProducer complains "DN must not be empty, but you provided an empty 
> DN".
> In other code, I do this and regularly pass an empty string as the base to 
> LdapTemplate.search(base, ...).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11060) dn shouldn't be strictly required for Spring LDAP component

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11060:

Estimated Complexity: Novice  (was: Unknown)

> dn shouldn't be strictly required for Spring LDAP component
> ---
>
> Key: CAMEL-11060
> URL: https://issues.apache.org/jira/browse/CAMEL-11060
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Ken Geis
>Priority: Minor
>
> I set a base DN in my LdapContextSource underlying the LdapTemplate. It's 
> redundant to need to set it in my route, but if I don't, the 
> SpringLdapProducer complains "DN must not be empty, but you provided an empty 
> DN".
> In other code, I do this and regularly pass an empty string as the base to 
> LdapTemplate.search(base, ...).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11060) dn shouldn't be strictly required for Spring LDAP component

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11060:

Priority: Minor  (was: Major)

> dn shouldn't be strictly required for Spring LDAP component
> ---
>
> Key: CAMEL-11060
> URL: https://issues.apache.org/jira/browse/CAMEL-11060
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Ken Geis
>Priority: Minor
>
> I set a base DN in my LdapContextSource underlying the LdapTemplate. It's 
> redundant to need to set it in my route, but if I don't, the 
> SpringLdapProducer complains "DN must not be empty, but you provided an empty 
> DN".
> In other code, I do this and regularly pass an empty string as the base to 
> LdapTemplate.search(base, ...).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-11056) Create a new camel-olingo4 component for supporting OData 4.0

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-11056.
--
Resolution: Fixed

> Create a new camel-olingo4 component for supporting OData 4.0
> -
>
> Key: CAMEL-11056
> URL: https://issues.apache.org/jira/browse/CAMEL-11056
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-olingo2
>Affects Versions: 2.19.0
>Reporter: Dmitry Volodin
>Assignee: Andrea Cosentino
>Priority: Minor
>  Labels: odata4, olingo4, rest_api
> Fix For: 2.19.0
>
>
> We required Camel Olingo component with the OData 4.0 support as now OData 
> Version 4.0 is OASIS based and widely using standard. For backward 
> compatibility we've migrated current camel-olingo2 to the new camel-olingo4 
> component, except deprecated and some new features.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (CAMEL-11056) Create a new camel-olingo4 component for supporting OData 4.0

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino reassigned CAMEL-11056:


Assignee: Andrea Cosentino

> Create a new camel-olingo4 component for supporting OData 4.0
> -
>
> Key: CAMEL-11056
> URL: https://issues.apache.org/jira/browse/CAMEL-11056
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-olingo2
>Affects Versions: 2.19.0
>Reporter: Dmitry Volodin
>Assignee: Andrea Cosentino
>Priority: Minor
>  Labels: odata4, olingo4, rest_api
>
> We required Camel Olingo component with the OData 4.0 support as now OData 
> Version 4.0 is OASIS based and widely using standard. For backward 
> compatibility we've migrated current camel-olingo2 to the new camel-olingo4 
> component, except deprecated and some new features.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11060) dn shouldn't be strictly required for Spring LDAP component

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11060:

Issue Type: Improvement  (was: Bug)

> dn shouldn't be strictly required for Spring LDAP component
> ---
>
> Key: CAMEL-11060
> URL: https://issues.apache.org/jira/browse/CAMEL-11060
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.18.3
>Reporter: Ken Geis
>
> I set a base DN in my LdapContextSource underlying the LdapTemplate. It's 
> redundant to need to set it in my route, but if I don't, the 
> SpringLdapProducer complains "DN must not be empty, but you provided an empty 
> DN".
> In other code, I do this and regularly pass an empty string as the base to 
> LdapTemplate.search(base, ...).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)