[jira] [Commented] (CAMEL-10197) camel-spring-boot - Extend the configuration hints to nested properties

2016-09-19 Thread Dhiraj Bokde (JIRA) 

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

Dhiraj Bokde commented on CAMEL-10197:
--

Nested properties would only work for first level properties, i.e. if a 
component has a property of type {{ClassA}}, and it's marked 
{{@NestedConfigurationProperty}}, Spring will only allow setting properties of 
that bean. This actually makes it easier to set properties of properties and 
create simple bean property fields on the fly. 
I've tried to think of a solution to it, but Camel refs won't work in the 
spring boot context, since properties can't be set as _ref_ string fields to 
point to the referenced bean. For e.g. if a component has property {{propA}} of 
type {{ClassA}}, Spring Boot won't allow setting it as propA=#refA, since it 
will try to convert it using it's own binding mechanism. 
I haven't tried it, but Spring Boot should support setting complex component 
with bean references using  {{${}}}. 

> camel-spring-boot - Extend the configuration hints to nested properties
> ---
>
> Key: CAMEL-10197
> URL: https://issues.apache.org/jira/browse/CAMEL-10197
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot
>Reporter: Nicola Ferraro
>Assignee: Dhiraj Bokde
>
> Support for spring-boot configuration allows users to configure the component 
> properties but does not give any hint on nested properties.
> There are many components that declare properties on nested beans.
> Eg. camel-docker has only one property named _configuration_ .  I found this 
> pattern in components that allow users to specify a default value on the 
> component and override it on each endpoint, if necessary.
> Setting the property:
> {code}
> camel.component.docker.configuration.host=172.28.128.4
> {code}
> allows a user to specify the docker host, but the tooling does not give 
> suggestions about that property.
> A way to allow the users to view the nested properties is using the 
> {{NestedConfigurationProperty}} annotation on the spring-boot configuration 
> class. The spring-boot inspector will scan the nested class for properties.
> The drawback is that the javadoc is not read from setters. Another drawback 
> is that we will be using a different approach respect to the "read-the-json" 
> one.
> We need to figure out how to add these properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10307) Upgrade docker java version

2016-09-19 Thread Fabrizio Spataro (JIRA) 

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

Fabrizio Spataro commented on CAMEL-10307:
--

I decided to start again, then the times are getting longer :-(

> Upgrade docker java version
> ---
>
> Key: CAMEL-10307
> URL: https://issues.apache.org/jira/browse/CAMEL-10307
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-docker
>Reporter: Fabrizio Spataro
>
> Hello,
> Today the component use a very old docker-java lib 1.0.4, current docker-java 
> version is 3.0.5
> Could be nice to upgrade all component code



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-7891) SetMessageEmmiter addition not work with latest Saxon

2016-09-19 Thread Luca Burgazzoli (JIRA) 

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

Luca Burgazzoli reassigned CAMEL-7891:
--

Assignee: Luca Burgazzoli  (was: Willem Jiang)

> SetMessageEmmiter addition not work with latest Saxon
> -
>
> Key: CAMEL-7891
> URL: https://issues.apache.org/jira/browse/CAMEL-7891
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-xslt
>Affects Versions: 2.14.0
>Reporter: Mateusz Nowakowski
>Assignee: Luca Burgazzoli
> Fix For: 2.18.0
>
>
> Saxon 9.6 introduces a couple of non-backward compatible changes:
> - template.newTransformer() does not return net.sf.saxon.Controller anymore
> so setting setMessageEmmiter won't work on the latest Saxon.
> - DOMResult provided to transform method  cannot have null node field 
> (current DomResultHandler won't work) that's backward compatibility change 
> will be fixed : https://saxonica.plan.io/issues/2164



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (CAMEL-7891) SetMessageEmmiter addition not work with latest Saxon

2016-09-19 Thread Luca Burgazzoli (JIRA) 

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

Luca Burgazzoli closed CAMEL-7891.
--
   Resolution: Fixed
Fix Version/s: 2.18.0

> SetMessageEmmiter addition not work with latest Saxon
> -
>
> Key: CAMEL-7891
> URL: https://issues.apache.org/jira/browse/CAMEL-7891
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-xslt
>Affects Versions: 2.14.0
>Reporter: Mateusz Nowakowski
>Assignee: Luca Burgazzoli
> Fix For: 2.18.0
>
>
> Saxon 9.6 introduces a couple of non-backward compatible changes:
> - template.newTransformer() does not return net.sf.saxon.Controller anymore
> so setting setMessageEmmiter won't work on the latest Saxon.
> - DOMResult provided to transform method  cannot have null node field 
> (current DomResultHandler won't work) that's backward compatibility change 
> will be fixed : https://saxonica.plan.io/issues/2164



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-7891) SetMessageEmmiter addition not work with latest Saxon

2016-09-19 Thread Luca Burgazzoli (JIRA) 

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

Luca Burgazzoli commented on CAMEL-7891:


So I'll close it, hoping no-one will reopen it again ;)

> SetMessageEmmiter addition not work with latest Saxon
> -
>
> Key: CAMEL-7891
> URL: https://issues.apache.org/jira/browse/CAMEL-7891
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-xslt
>Affects Versions: 2.14.0
>Reporter: Mateusz Nowakowski
>Assignee: Willem Jiang
>
> Saxon 9.6 introduces a couple of non-backward compatible changes:
> - template.newTransformer() does not return net.sf.saxon.Controller anymore
> so setting setMessageEmmiter won't work on the latest Saxon.
> - DOMResult provided to transform method  cannot have null node field 
> (current DomResultHandler won't work) that's backward compatibility change 
> will be fixed : https://saxonica.plan.io/issues/2164



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-7891) SetMessageEmmiter addition not work with latest Saxon

2016-09-19 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen commented on CAMEL-7891:


Luca, no I dont, maybe they changed APIs again in 9.7 etc.

This ticket was just a reminder that Saxon upgrade is not easy.

> SetMessageEmmiter addition not work with latest Saxon
> -
>
> Key: CAMEL-7891
> URL: https://issues.apache.org/jira/browse/CAMEL-7891
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-xslt
>Affects Versions: 2.14.0
>Reporter: Mateusz Nowakowski
>Assignee: Willem Jiang
>
> Saxon 9.6 introduces a couple of non-backward compatible changes:
> - template.newTransformer() does not return net.sf.saxon.Controller anymore
> so setting setMessageEmmiter won't work on the latest Saxon.
> - DOMResult provided to transform method  cannot have null node field 
> (current DomResultHandler won't work) that's backward compatibility change 
> will be fixed : https://saxonica.plan.io/issues/2164



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10304) Apache Camel Docker component not working in OSGi environment

2016-09-19 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino commented on CAMEL-10304:
--

Hello [~philip142au], we are actually in the process of upgrading the 
dependency.. There is a PR on the way :-)

Hopefully we will be able to test the component with the latest release in OSGi 
environment.

> Apache Camel Docker component not working in OSGi environment
> -
>
> Key: CAMEL-10304
> URL: https://issues.apache.org/jira/browse/CAMEL-10304
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.17.3
> Environment: Windows
>Reporter: Philip Andrew
>Priority: Minor
>
> I can not use camel-docker in the OSGi environment, exception is thrown.
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider 
> org.glass fish.jersey.internal.RuntimeDelegateImpl could not be instantiated: 
> java.lang.Il legalStateException: No generator was provided and there is no 
> default generator registered
> If I do the following workaround then it can work
> RuntimeDelegate.setInstance(new 
> org.glassfish.jersey.server.internal.RuntimeDelegateImpl())
> http://stackoverflow.com/questions/39382056/how-to-get-apache-camel-docker-component-to-work-in-osgi-or-jersey-does-not-wo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10304) Apache Camel Docker component not working in OSGi environment

2016-09-19 Thread Philip Andrew (JIRA) 

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

Philip Andrew commented on CAMEL-10304:
---

Hi Claus, my feeling is that the Camel Docker component is very out of date and 
not really usable in the OSGi environment. This is what I find.

Here are instructions on how to get Docker TLS working if its at all helpful

https://github.com/PhilAndrew/JumpMicro/blob/master/core/src/main/scala/jumpmicro/impl/util/docker/README.md

a) The demo as given in the documentation page does run, but does not work in a 
non-OSGi environment with the current docker server due to API changes, 
http://camel.apache.org/docker.html 
from("docker://events?host=192.168.59.103=2375").to("log:event") as the 
Docker API has changed and the result back from the docker server doesn't match 
the docker-java version. However it does connect to the docker server using TLS 
when I turn on the secure mode.

b) In the non-OSGi environment I must add RuntimeDelegate.setInstance(new 
org.glassfish.jersey.server.internal.RuntimeDelegateImpl()) but I don't know 
why, that's enough to get it to work.

c) In the OSGi environment down at the lower level this uses Jersey which gives 
the error as shown in this Stackoverflow 
http://stackoverflow.com/questions/25740556/error-while-using-jersey-client-in-osgi-no-generator-was-provided
I followed their instructions but still couldn't get it to work in OSGi. OSGi 
is confusing most of the time.

d) The docker-java dependency version is quite old. Is it docker-java version 
1.4.0? That was released 07-Jul-2015, now docker-java current version is 3.0.6.


> Apache Camel Docker component not working in OSGi environment
> -
>
> Key: CAMEL-10304
> URL: https://issues.apache.org/jira/browse/CAMEL-10304
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.17.3
> Environment: Windows
>Reporter: Philip Andrew
>Priority: Minor
>
> I can not use camel-docker in the OSGi environment, exception is thrown.
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider 
> org.glass fish.jersey.internal.RuntimeDelegateImpl could not be instantiated: 
> java.lang.Il legalStateException: No generator was provided and there is no 
> default generator registered
> If I do the following workaround then it can work
> RuntimeDelegate.setInstance(new 
> org.glassfish.jersey.server.internal.RuntimeDelegateImpl())
> http://stackoverflow.com/questions/39382056/how-to-get-apache-camel-docker-component-to-work-in-osgi-or-jersey-does-not-wo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10321) New Component camel-asterisk

2016-09-19 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-10321:


GitHub user Fabryprog opened a pull request:

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

Camel 10321

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

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

$ git pull https://github.com/Fabryprog/camel CAMEL-10321

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

https://github.com/apache/camel/pull/1180.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 #1180


commit 5a198305600d62a88030d9649a1b9b45517e86a6
Author: Fabrizio Spataro 
Date:   2016-09-15T16:08:23Z

CAMEL-10321, camel-asterisk component (without test and doc)

commit dad6af0e7333e1566fd573d8a0bd18e7aa318fa3
Author: Fabryprog 
Date:   2016-09-16T21:25:59Z

CAMEL-10321, Asterisk Component: test added

commit ff16f2838d29171c8006e6b427acee48b9b7db96
Author: Fabryprog 
Date:   2016-09-16T22:15:14Z

CAMEL-10321, Asterisk Component: documentation adoc

commit 9c0d3a1318f3cd88d3abb9f6d35838faa6a7acec
Author: Fabryprog 
Date:   2016-09-16T22:22:46Z

CAMEL-10321, Asterisk Component: fix rename class




> New Component camel-asterisk
> 
>
> Key: CAMEL-10321
> URL: https://issues.apache.org/jira/browse/CAMEL-10321
> Project: Camel
>  Issue Type: New Feature
>Reporter: Fabrizio Spataro
>
> Hello,
> i wrote a component to send and receive event from an asterisk VOIP server.
> Can i send my PR? Is it compatible with apache camel code license?
> King Regard



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-7891) SetMessageEmmiter addition not work with latest Saxon

2016-09-19 Thread Luca Burgazzoli (JIRA) 

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

Luca Burgazzoli commented on CAMEL-7891:


[~davsclaus] do you know if this issue is still relevant ? I have not found 
references of setMessageEmmiter or error because of DomResultHandler so far

> SetMessageEmmiter addition not work with latest Saxon
> -
>
> Key: CAMEL-7891
> URL: https://issues.apache.org/jira/browse/CAMEL-7891
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-xslt
>Affects Versions: 2.14.0
>Reporter: Mateusz Nowakowski
>Assignee: Willem Jiang
>
> Saxon 9.6 introduces a couple of non-backward compatible changes:
> - template.newTransformer() does not return net.sf.saxon.Controller anymore
> so setting setMessageEmmiter won't work on the latest Saxon.
> - DOMResult provided to transform method  cannot have null node field 
> (current DomResultHandler won't work) that's backward compatibility change 
> will be fixed : https://saxonica.plan.io/issues/2164



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8830) Upgrade to Saxon HE 9.7

2016-09-19 Thread Luca Burgazzoli (JIRA) 

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

Luca Burgazzoli commented on CAMEL-8830:


OSGi import range for Saxon should then be changed to: 

{code}
net.sf.saxon.*;version="[9.7.0,9.8)",
{code}



> Upgrade to Saxon HE 9.7
> ---
>
> Key: CAMEL-8830
> URL: https://issues.apache.org/jira/browse/CAMEL-8830
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-saxon
>Affects Versions: 2.15.2
>Reporter: Kartik
>Assignee: Luca Burgazzoli
> Fix For: 2.18.0
>
>
> Upgrade to Saxon HE 9.6 which uses XQuery 3.0 by default, allowing to use 
> powerful new XQuery 3.0 features such as 'group by'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10252) Upgrade Weld embedded Arquillian adapter to version 2.0.0.Beta3

2016-09-19 Thread Antonin Stefanutti (JIRA) 

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

Antonin Stefanutti updated CAMEL-10252:
---
Summary: Upgrade Weld embedded Arquillian adapter to version 2.0.0.Beta3  
(was: Upgrade Weld embedded Arquillian adapter to version 2.0.0.Beta2)

> Upgrade Weld embedded Arquillian adapter to version 2.0.0.Beta3
> ---
>
> Key: CAMEL-10252
> URL: https://issues.apache.org/jira/browse/CAMEL-10252
> Project: Camel
>  Issue Type: Task
>  Components: camel-cdi
>Reporter: Antonin Stefanutti
>Assignee: Antonin Stefanutti
>Priority: Minor
> Fix For: 2.18.0
>
>
> See http://weld.cdi-spec.org/news/2016/07/21/arq-container-weld-releasel/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10329) Camel SES component when using URI option "to" it can be not overriden with 'CamelAwsSesTo' header

2016-09-19 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen commented on CAMEL-10329:
-

Yeah you can likely just iterate it, then you can use a string with a single 
value and separate with comma

ObjectHelper.createIterator has a method that can help with this which we use 
in other use-cases.

> Camel SES component when using URI option "to" it can be not overriden with 
> 'CamelAwsSesTo' header
> --
>
> Key: CAMEL-10329
> URL: https://issues.apache.org/jira/browse/CAMEL-10329
> Project: Camel
>  Issue Type: Bug
>  Components: camel-aws
>Affects Versions: 2.17.3
>Reporter: SunChaoqun
>Assignee: Andrea Cosentino
>
> When I am using URI option "to" it can be not overriden with 'CamelAwsSesTo' 
> header. 
> BTW , CamelAwsSesSubject header works 
> Java DSL:
>   from("").setBody()
>   
> .constant("Hello").setHeader("CamelAwsSesSubject", constant("BBB"))
>   .setHeader("CamelAwsSesTo", 
> constant("overr...@somesite.com"))
>   .to("aws-ses:f...@somesite.com" + 
> "?amazonSESClient=#awsConn" + "=AAA"
>   + "=t...@somesite.com" + 
> "=x...@xxx.com")
> expected: send the email to overr...@somesite.com 
> actually: send the email to t...@somesite.com



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10329) Camel SES component when using URI option "to" it can be not overriden with 'CamelAwsSesTo' header

2016-09-19 Thread SunChaoqun (JIRA) 

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

SunChaoqun commented on CAMEL-10329:


BTW, if it can accept string as header value , it will be more convenient  . 
Thanks.

> Camel SES component when using URI option "to" it can be not overriden with 
> 'CamelAwsSesTo' header
> --
>
> Key: CAMEL-10329
> URL: https://issues.apache.org/jira/browse/CAMEL-10329
> Project: Camel
>  Issue Type: Bug
>  Components: camel-aws
>Affects Versions: 2.17.3
>Reporter: SunChaoqun
>Assignee: Andrea Cosentino
>
> When I am using URI option "to" it can be not overriden with 'CamelAwsSesTo' 
> header. 
> BTW , CamelAwsSesSubject header works 
> Java DSL:
>   from("").setBody()
>   
> .constant("Hello").setHeader("CamelAwsSesSubject", constant("BBB"))
>   .setHeader("CamelAwsSesTo", 
> constant("overr...@somesite.com"))
>   .to("aws-ses:f...@somesite.com" + 
> "?amazonSESClient=#awsConn" + "=AAA"
>   + "=t...@somesite.com" + 
> "=x...@xxx.com")
> expected: send the email to overr...@somesite.com 
> actually: send the email to t...@somesite.com



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10329) Camel SES component when using URI option "to" it can be not overriden with 'CamelAwsSesTo' header

2016-09-19 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino commented on CAMEL-10329:
--

Thanks for spotting anyway :-)

> Camel SES component when using URI option "to" it can be not overriden with 
> 'CamelAwsSesTo' header
> --
>
> Key: CAMEL-10329
> URL: https://issues.apache.org/jira/browse/CAMEL-10329
> Project: Camel
>  Issue Type: Bug
>  Components: camel-aws
>Affects Versions: 2.17.3
>Reporter: SunChaoqun
>Assignee: Andrea Cosentino
>
> When I am using URI option "to" it can be not overriden with 'CamelAwsSesTo' 
> header. 
> BTW , CamelAwsSesSubject header works 
> Java DSL:
>   from("").setBody()
>   
> .constant("Hello").setHeader("CamelAwsSesSubject", constant("BBB"))
>   .setHeader("CamelAwsSesTo", 
> constant("overr...@somesite.com"))
>   .to("aws-ses:f...@somesite.com" + 
> "?amazonSESClient=#awsConn" + "=AAA"
>   + "=t...@somesite.com" + 
> "=x...@xxx.com")
> expected: send the email to overr...@somesite.com 
> actually: send the email to t...@somesite.com



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (CAMEL-10329) Camel SES component when using URI option "to" it can be not overriden with 'CamelAwsSesTo' header

2016-09-19 Thread SunChaoqun (JIRA) 

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

SunChaoqun closed CAMEL-10329.
--
Resolution: Not A Bug

Sorry , I found the reason , the value of the contant must be a List , 
I gave the value which is string , so It ignored the header of values .

> Camel SES component when using URI option "to" it can be not overriden with 
> 'CamelAwsSesTo' header
> --
>
> Key: CAMEL-10329
> URL: https://issues.apache.org/jira/browse/CAMEL-10329
> Project: Camel
>  Issue Type: Bug
>  Components: camel-aws
>Affects Versions: 2.17.3
>Reporter: SunChaoqun
>Assignee: Andrea Cosentino
>
> When I am using URI option "to" it can be not overriden with 'CamelAwsSesTo' 
> header. 
> BTW , CamelAwsSesSubject header works 
> Java DSL:
>   from("").setBody()
>   
> .constant("Hello").setHeader("CamelAwsSesSubject", constant("BBB"))
>   .setHeader("CamelAwsSesTo", 
> constant("overr...@somesite.com"))
>   .to("aws-ses:f...@somesite.com" + 
> "?amazonSESClient=#awsConn" + "=AAA"
>   + "=t...@somesite.com" + 
> "=x...@xxx.com")
> expected: send the email to overr...@somesite.com 
> actually: send the email to t...@somesite.com



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10327) New Apache drill component

2016-09-19 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino commented on CAMEL-10327:
--

Good idea.

> New Apache drill component
> --
>
> Key: CAMEL-10327
> URL: https://issues.apache.org/jira/browse/CAMEL-10327
> Project: Camel
>  Issue Type: New Feature
>Reporter: Fabrizio Spataro
>Priority: Minor
>
> Hello,
> the main idea is to create a producer to run queries on the apache drill 
> cluster. Can i start to develop this "simple" producer?
> kings regards



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-10329) Camel SES component when using URI option "to" it can be not overriden with 'CamelAwsSesTo' header

2016-09-19 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino reassigned CAMEL-10329:


Assignee: Andrea Cosentino

> Camel SES component when using URI option "to" it can be not overriden with 
> 'CamelAwsSesTo' header
> --
>
> Key: CAMEL-10329
> URL: https://issues.apache.org/jira/browse/CAMEL-10329
> Project: Camel
>  Issue Type: Bug
>  Components: camel-aws
>Affects Versions: 2.17.3
>Reporter: SunChaoqun
>Assignee: Andrea Cosentino
>
> When I am using URI option "to" it can be not overriden with 'CamelAwsSesTo' 
> header. 
> BTW , CamelAwsSesSubject header works 
> Java DSL:
>   from("").setBody()
>   
> .constant("Hello").setHeader("CamelAwsSesSubject", constant("BBB"))
>   .setHeader("CamelAwsSesTo", 
> constant("overr...@somesite.com"))
>   .to("aws-ses:f...@somesite.com" + 
> "?amazonSESClient=#awsConn" + "=AAA"
>   + "=t...@somesite.com" + 
> "=x...@xxx.com")
> expected: send the email to overr...@somesite.com 
> actually: send the email to t...@somesite.com



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10329) Camel SES component when using URI option "to" it can be not overriden with 'CamelAwsSesTo' header

2016-09-19 Thread SunChaoqun (JIRA) 
SunChaoqun created CAMEL-10329:
--

 Summary: Camel SES component when using URI option "to" it can be 
not overriden with 'CamelAwsSesTo' header
 Key: CAMEL-10329
 URL: https://issues.apache.org/jira/browse/CAMEL-10329
 Project: Camel
  Issue Type: Bug
  Components: camel-aws
Affects Versions: 2.17.3
Reporter: SunChaoqun


When I am using URI option "to" it can be not overriden with 'CamelAwsSesTo' 
header. 

BTW , CamelAwsSesSubject header works 

Java DSL:
from("").setBody()

.constant("Hello").setHeader("CamelAwsSesSubject", constant("BBB"))
.setHeader("CamelAwsSesTo", 
constant("overr...@somesite.com"))
.to("aws-ses:f...@somesite.com" + 
"?amazonSESClient=#awsConn" + "=AAA"
+ "=t...@somesite.com" + 
"=x...@xxx.com")

expected: send the email to overr...@somesite.com 

actually: send the email to t...@somesite.com



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)