[jira] [Created] (CAMEL-9926) HTTP Proxy support in Salesforce component is broken with upgrade to Jetty9

[Dhiraj Bokde (JIRA)]

Dhiraj Bokde created CAMEL-9926:
---

 Summary: HTTP Proxy support in Salesforce component is broken with 
upgrade to Jetty9
 Key: CAMEL-9926
 URL: https://issues.apache.org/jira/browse/CAMEL-9926
 Project: Camel
  Issue Type: Bug
  Components: camel-salesforce
Affects Versions: 2.17.1, 2.18.0
Reporter: Dhiraj Bokde
Assignee: Dhiraj Bokde
Priority: Critical


HTTP Proxy support in Jetty9 Client is broken, which causes HTTP Proxy tests in 
the Salesforce components to fail. 

They have been marked as ignored for now, but it MUST be fixed in Jetty9 ASAP 
and the component updated to use the new version of Jetty9 client with working 
support for Proxy authentication. 



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

[jira] [Commented] (CAMEL-9869) Create Apache Flink Component

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-9869:
---

GitHub user sbcd90 opened a pull request:

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

[CAMEL-9869] Create Apache Flink Component

@davsclaus Created the .adoc file. Please review.

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

$ git pull https://github.com/sbcd90/camel CAMEL-9869

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

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


commit d0eb5e7295242a8cc59143a20a1bd7580e621957
Author: Subhobrata Dey 
Date:   2016-04-29T02:40:04Z

[CAMEL-9869] Create Apache Flink Component




> Create Apache Flink Component
> -
>
> Key: CAMEL-9869
> URL: https://issues.apache.org/jira/browse/CAMEL-9869
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-flink
>Reporter: Subhobrata Dey
>Assignee: Claus Ibsen
> Fix For: 2.18.0
>
>
> Hello,
> I have created an Apache Flink component for Camel which makes it easier to 
> use Flink for analytics. One can use DataSet callbacks with Spring beans/OSGI 
> services.
> Using Spring's application context, it can be accessed like 
> {noformat}
> @Bean
> public DataSetCallback countLinesContaining() {
> return new DataSetCallback() {
> public Long onDataSet(DataSet dataSet, Object... objects) {
> try {
> dataSet.print();
> return new Long(0);
> } catch (Exception e) {
> return new Long(-1);
> }
> }
> };
> }
> @Bean
> public DataSet myDataSet() {
> final ExecutionEnvironment env = 
> ExecutionEnvironment.getExecutionEnvironment();
> DataSet text = env.fromElements(
> "Who's there?",
> "I think I hear them. Stand ho! Who's there?");
> return text;
> }
> {noformat}
> The results can be accessed like 
> {noformat}
> Long count = 
> template.requestBody("flink:dataSet?dataSet=#myDataSet=#countLinesContaining",
>  pattern, Long.class);
> {noformat}
> Please review & accept my contribution.



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

[jira] [Created] (CAMEL-9925) Update Salesforce component to use Jetty9

[Dhiraj Bokde (JIRA)]

Dhiraj Bokde created CAMEL-9925:
---

 Summary: Update Salesforce component to use Jetty9
 Key: CAMEL-9925
 URL: https://issues.apache.org/jira/browse/CAMEL-9925
 Project: Camel
  Issue Type: Improvement
  Components: camel-salesforce
Affects Versions: 2.17.0, 2.18.0
Reporter: Dhiraj Bokde
Assignee: Dhiraj Bokde


Jetty8 has been outdated for a while now, so the component must be updated to 
use the new Jetty9 client API to be supported in the future. 



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

[jira] [Commented] (CAMEL-9911) RestBindingMode auto not honored

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-9911:
---

Github user johnament closed the pull request at:

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


> RestBindingMode auto not honored
> 
>
> Key: CAMEL-9911
> URL: https://issues.apache.org/jira/browse/CAMEL-9911
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.17.0
>Reporter: John D. Ament
>Assignee: John D. Ament
> Fix For: 2.17.1, 2.18.0
>
>
> The usage of rest binding mode is confusing/doesn't work consistently.
> If you look at the field definition:
> {code}
> @XmlAttribute @Metadata(defaultValue = "auto")
> private RestBindingMode bindingMode;
> {code}
> You would expect that the default value is "auto" but in fact there is no 
> default when running.
> You need to explicitly set it in configuration, like this:
> {code}
> restConfiguration()
> .component("jetty")
> .port(9097)
> .bindingMode(RestBindingMode.auto)
> ;
> {code}



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

[jira] [Updated] (CAMEL-9823) Exploring Consumer groups feature in Camel-kafka consumer side

[Anbumani Balusamy (JIRA)]

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

Anbumani Balusamy updated CAMEL-9823:
-
Attachment: KafkaConsumer.java

Hi [~ancosen],

Please find the attachment. Kindly review and let me know your 
comments/suggestions.

Thanks!
Anbu

> Exploring Consumer groups feature in Camel-kafka consumer side
> --
>
> Key: CAMEL-9823
> URL: https://issues.apache.org/jira/browse/CAMEL-9823
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-kafka
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.18.0
>
> Attachments: KafkaConsumer.java
>
>
> I guess we can take advantage from consumer groups feature in camel-kafka.
> http://www.confluent.io/blog/tutorial-getting-started-with-the-new-apache-kafka-0.9-consumer-client



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

[jira] [Commented] (CAMEL-8207) camel-smpp - trying to create multiple receiver binds

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-8207:


Can you look more into this. Do you see a bunch of logs with "Trying to 
reconnect to ..". It seems the consumer has some logic to fork a thread to 
create a sesseion and re-connect if the connection was closed.



> camel-smpp - trying to create multiple receiver binds
> -
>
> Key: CAMEL-8207
> URL: https://issues.apache.org/jira/browse/CAMEL-8207
> Project: Camel
>  Issue Type: Bug
>  Components: camel-smpp
>Affects Versions: 2.14.1
> Environment: n/a
>Reporter: Daniel Pocock
>
> I've noticed that the producer is just creating one transmitter bind but the 
> consumer appears to try and create multiple receiver binds.
> I tried putting threads(1, 1) into the consumer route but it still appears to 
> try and create multiple receiver binds.
> There are many scenarios where somebody would only want to use a single 
> receiver bind
> Many providers limit the number of binds and the component creates a lot of 
> noise in the log file when it can't create additional binds because the SMSC 
> rejects the additional connections with negative response code 5.
> I went looking for information about this and found the following related 
> comments about threading issues in jSMPP:
> https://issues.jboss.org/browse/MR-838



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

[jira] [Resolved] (CAMEL-9200) Context component conflates endpoints with the same local id from different CamelContexts

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9200.

Resolution: Fixed

Thanks for the patch. Sorry for the delay of merging.

> Context component conflates endpoints with the same local id from different 
> CamelContexts
> -
>
> Key: CAMEL-9200
> URL: https://issues.apache.org/jira/browse/CAMEL-9200
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.15.3
>Reporter: Aaron Birkland
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.4, 2.17.1, 2.18.0
>
> Attachments: CAMEL-9200.patch
>
>
> The context component experiences clashes between endpoints with the same 
> local name, but from different contexts.  If two contexts both contain a 
> local endpoint "direct:out", any route involving both endpoints will fail to 
> start due to a FailedToStartRouteException; "Multiple consumers for the same 
> endpoint is not allowed: Endpoint[direct://out]."
> As an example, the following set of routes will fail due to this issue:
> from("direct:in").to("blackBox:in");
> from("blackBox:out").to("direct:out");
> from("direct:out").to("mock:results");
> See  thread:
> http://camel.465427.n5.nabble.com/Context-Component-issue-td5770975.html



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

[jira] [Commented] (CAMEL-9920) Handle SocketTimeoutException on accept

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-9920:
---

Github user hqstevenson closed the pull request at:

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


> Handle SocketTimeoutException on accept
> ---
>
> Key: CAMEL-9920
> URL: https://issues.apache.org/jira/browse/CAMEL-9920
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mllp
>Affects Versions: 2.17.0
>Reporter: Quinn Stevenson
>Assignee: Quinn Stevenson
> Fix For: 2.17.1, 2.18.0
>
>
> The MLLP receiver logs and error when a SocketTimeoutException is encountered 
> while waiting for a connection.  It will not successfully accept connections 
> after that.



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

[jira] [Commented] (CAMEL-7489) Bindy CSV DataField position requires @Section or @KeyValuePairDataField

[Marco Carvalho (JIRA)]

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

Marco Carvalho commented on CAMEL-7489:
---

Either need to add to the documentation that session or keyvaluepair
annotation is also needed or remove that requirement.

Thank you for viewing it.

Regards
Marco




> Bindy CSV DataField position requires @Section or  @KeyValuePairDataField
> -
>
> Key: CAMEL-7489
> URL: https://issues.apache.org/jira/browse/CAMEL-7489
> Project: Camel
>  Issue Type: Bug
>  Components: camel-bindy
>Reporter: Marco Carvalho
>Priority: Minor
>
> When using DataField as in "case 8" of the documentation page (sorry, no 
> anchor links):
> http://camel.apache.org/bindy.html
> A exception is risen for a missing Section annotation.
> "@Section and/or @KeyValuePairDataField have not been defined"



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

[jira] [Updated] (CAMEL-9200) Context component conflates endpoints with the same local id from different CamelContexts

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9200:
---
Fix Version/s: 2.18.0
   2.17.1
   2.16.4

> Context component conflates endpoints with the same local id from different 
> CamelContexts
> -
>
> Key: CAMEL-9200
> URL: https://issues.apache.org/jira/browse/CAMEL-9200
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.15.3
>Reporter: Aaron Birkland
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.4, 2.17.1, 2.18.0
>
> Attachments: CAMEL-9200.patch
>
>
> The context component experiences clashes between endpoints with the same 
> local name, but from different contexts.  If two contexts both contain a 
> local endpoint "direct:out", any route involving both endpoints will fail to 
> start due to a FailedToStartRouteException; "Multiple consumers for the same 
> endpoint is not allowed: Endpoint[direct://out]."
> As an example, the following set of routes will fail due to this issue:
> from("direct:in").to("blackBox:in");
> from("blackBox:out").to("direct:out");
> from("direct:out").to("mock:results");
> See  thread:
> http://camel.465427.n5.nabble.com/Context-Component-issue-td5770975.html



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

[jira] [Assigned] (CAMEL-9200) Context component conflates endpoints with the same local id from different CamelContexts

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-9200:
--

Assignee: Claus Ibsen

> Context component conflates endpoints with the same local id from different 
> CamelContexts
> -
>
> Key: CAMEL-9200
> URL: https://issues.apache.org/jira/browse/CAMEL-9200
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.15.3
>Reporter: Aaron Birkland
>Assignee: Claus Ibsen
>Priority: Minor
> Attachments: CAMEL-9200.patch
>
>
> The context component experiences clashes between endpoints with the same 
> local name, but from different contexts.  If two contexts both contain a 
> local endpoint "direct:out", any route involving both endpoints will fail to 
> start due to a FailedToStartRouteException; "Multiple consumers for the same 
> endpoint is not allowed: Endpoint[direct://out]."
> As an example, the following set of routes will fail due to this issue:
> from("direct:in").to("blackBox:in");
> from("blackBox:out").to("direct:out");
> from("direct:out").to("mock:results");
> See  thread:
> http://camel.465427.n5.nabble.com/Context-Component-issue-td5770975.html



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

[jira] [Resolved] (CAMEL-8308) RabbitMQEndpoint: setting prefetchEnabled=false or prefetchCount=0 (default values) locks all messages on RabbitMQ

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-8308.

Resolution: Not A Problem
  Assignee: Claus Ibsen

Okay thanks for the explanation Ramon

> RabbitMQEndpoint: setting prefetchEnabled=false or prefetchCount=0 (default 
> values) locks all messages on RabbitMQ
> --
>
> Key: CAMEL-8308
> URL: https://issues.apache.org/jira/browse/CAMEL-8308
> Project: Camel
>  Issue Type: Bug
>  Components: camel-rabbitmq
>Affects Versions: 2.14.1
>Reporter: Daniel Neugebauer
>Assignee: Claus Ibsen
>
> If RabbitMQEndpoint is configured with either prefetchEnabled=false or 
> prefetchCount=0 (both are default values), then messages appear to be locked 
> on server-side (getting prefetched with high/no limit?).
> To reproduce:
> # add multiple messages to a RabbitMQ queue which define an expiration header 
> (after expiration, RabbitMQ will remove those message from queue without 
> delivering them to consumers)
> # watch RabbitMQ admin panel, you should see n messages are "Ready", 0 
> messages are "Unacknowledged"
> # configure & run one concurrent RabbitMQEndpoint from Camel with above 
> settings + autoAck=false and delay/block processing of messages (e.g. by 
> running Thread.wait(1) in a Processor)
> # watch the admin panel again: 0 messages are "Ready", n messages are 
> "Unacknowledged" - so Camel appears to have prefetched all messages?
> # wait until messages should have expired
> # admin panel still shows all unprocessed messages as unacknowledged although 
> they should have been removed from queue
> # Camel still processes those messages after expiration
> # stop Camel (returns all unacknowledged messages to ready state)
> # admin panel shows that all messages now have been purged from queue (much 
> later than they should have)
> Workaround: Repeating with prefetchEnabled=true and prefetchCount=1 shows 
> only 1 message "unacknowledged" while queue is being processed by Camel, all 
> other messages remain "ready" and expire in time (thus skipping the Camel 
> queue as expected).
> Expected behaviour: If the prefetcher is disabled, no messages should get 
> locked on server-side, so messages can be expired by RabbitMQ as intended by 
> the message sender.



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

[jira] [Resolved] (CAMEL-8838) Setting HttpConnectionManager Override Property in URI using HttpClientParams is not working

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-8838.

Resolution: Won't Fix
  Assignee: Claus Ibsen

Yeah you cannot set all options in the uri

> Setting HttpConnectionManager Override Property in URI using HttpClientParams 
> is not working
> 
>
> Key: CAMEL-8838
> URL: https://issues.apache.org/jira/browse/CAMEL-8838
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http
>Affects Versions: 2.13.4, 2.15.0, 2.15.2
>Reporter: Deepak
>Assignee: Claus Ibsen
>  Labels: camel, http
>
> Hi, 
> When we pass HttpClientParams in EndPoint URI, to override 
> HttpConnectionManager class, the HttpComponent is not considering the 
> overridden parameter, 
> Example URL 
> https://myapplication.com/myappservice/?bridgeEndpoint=true=false=org.apache.commons.httpclient.SimpleHttpConnectionManager
>  
> In org.apache.camel.component.http.HttpComponent, if there is no bean 
> injection of httpConnectionManager class, by default a new instance of 
> MultiThreadedHttpConnectionManager class is created. 
> In HttpComponent class, while constructing the HttpEndPoint, the same above 
> HttpConnection Manager class is sent as reference. 
> In HttpEndPoint class, createHttpClient method, although all the Http client 
> params are considered, HttpConnectionManager class sent by the HttpClient 
> Params is not considered. 
> Please clarify or fix it. 
> HttpClient answer = new HttpClient(getClientParams()); // Line Number 110 
> answer.setHttpConnectionManager(httpConnectionManager); // Line Number 144



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

[jira] [Resolved] (CAMEL-9882) Support importing Camel XML configuration files in Camel CDI

[Antonin Stefanutti (JIRA)]

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

Antonin Stefanutti resolved CAMEL-9882.
---
Resolution: Fixed

> Support importing Camel XML configuration files in Camel CDI
> 
>
> Key: CAMEL-9882
> URL: https://issues.apache.org/jira/browse/CAMEL-9882
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-cdi
>Reporter: Antonin Stefanutti
>Assignee: Antonin Stefanutti
> Fix For: 2.18.0
>
>
> So that user can use their existing Camel XML files with CDI or use Camel XML 
> for configuring their Camel contexts.
> For example, given the following Camel XML:
> {code}
>xmlns="http://camel.apache.org/schema/spring;>
>type="LoggingErrorHandler"
>   logName="error"
>   level="WARN"/>
> 
> 
> 
> 
> ${body} contains 'exception'
> 
> 
> 
> 
> Response to ${body}
> 
> 
> 
> 
> 
> 
> {code}
> And following bean:
> {code}
> @Named
> @Produces
> Exception failure = new CamelException("failure message!");
> {code}
> The Camel XML elements with an {{id}} attributes ({{errorHandler}} in the 
> example) get deployed as CDI beans and vice-versa the {{ref}} attributes can 
> refer to CDI beans ({{@Named("failure")}} in the example).
> The current proposition is to expose an annotation that the developer can use 
> on any CDI bean to declare the Camel XML files to import in her/his Camel CDI 
> application, e.g.:
> {code}
> @ImportResource("imported-context.xml")
> class MyCamelCdiBean {
> }
> {code}



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

[jira] [Updated] (CAMEL-9107) Exception thrown when reading a mail with an attached file, which name contains a semicolon

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9107:
---
Fix Version/s: Future

> Exception thrown when reading a mail with an attached file, which name 
> contains a semicolon
> ---
>
> Key: CAMEL-9107
> URL: https://issues.apache.org/jira/browse/CAMEL-9107
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mail
>Affects Versions: 2.15.2
>Reporter: Thierry Frossard
>Priority: Minor
> Fix For: Future
>
>
> Hi, 
> I posted this issue in Camel users forum but unfortunately got no response.
> I'm using Camel 2.15.2 with JDK 1.7 under Windows 7 and Eclipse 4.2.2 as 
> development tool. 
> My route reads from an IMAP server (IBM Lotus Notes). I have one big problem 
> : when the route handles an email, which contains a PDF attached file with a 
> semicolon in his name (for exemple my;pdf.pdf), then the route always throws 
> this exception : 
> Failed to extract body due to: Unable to load BODYSTRUCTURE. 
> 4.08.15 15:10:11:313 CEST] 0172 SystemOut O [15:10:11.313] WARN  
> [Camel (Mail vers Indexation) thread #0 - imap://myimapserver.ch] 
> org.apache.camel.util.CamelLogger.log:224 : Caused by: 
> [org.apache.camel.RuntimeCamelException - Failed to extract body due to: 
> Unable to load BODYSTRUCTURE. Exchange: Exchange[MailMessage@0x862446e3]. 
> Message: com.sun.mail.imap.IMAPMessage@16e6c70e] 
> org.apache.camel.RuntimeCamelException: Failed to extract body due to: Unable 
> to load BODYSTRUCTURE. Exchange: Exchange[MailMessage@0x862446e3]. Message: 
> com.sun.mail.imap.IMAPMessage@16e6c70e 
> at 
> org.apache.camel.component.mail.MailBinding.extractBodyFromMail(MailBinding.java:275)
>  ~[camel-mail-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.component.mail.MailMessage.createBody(MailMessage.java:103) 
> ~[camel-mail-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41) 
> ~[camel-core-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.component.mail.MailConsumer.createExchanges(MailConsumer.java:326)
>  ~[camel-mail-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:121) 
> ~[camel-mail-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>  [camel-core-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>  [camel-core-2.15.2.jar:2.15.2] 
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:482) 
> [na:1.7.0] 
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:315) 
> [na:1.7.0] 
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:189)
>  [na:1.7.0] 
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
>  [na:1.7.0] 
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
>  [na:1.7.0] 
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
>  [na:1.7.0] 
> at java.lang.Thread.run(Thread.java:804) [na:1.7.0] 
> Caused by: javax.mail.MessagingException: Unable to load BODYSTRUCTURE 
> at 
> com.sun.mail.imap.IMAPMessage.loadBODYSTRUCTURE(IMAPMessage.java:1261) 
> ~[com.ibm.ws.prereq.javamail.jar:na] 
> at com.sun.mail.imap.IMAPMessage.getDataHandler(IMAPMessage.java:597) 
> ~[com.ibm.ws.prereq.javamail.jar:na] 
> at javax.mail.internet.MimeMessage.getContent(MimeMessage.java:1395) 
> ~[com.ibm.ws.prereq.javamail.jar:na] 
> at 
> org.apache.camel.component.mail.MailBinding.extractBodyFromMail(MailBinding.java:247)
>  ~[camel-mail-2.15.2.jar:2.15.2] 
> ... 13 common frames omitted 
> Here is the route (very simple) : 
>   @Override 
>   public void configure() throws Exception { 
> from(getPropertiesUri()) 
> /**/.to("log:dummy"); 
>   } 
>   protected String getPropertiesUri() { 
> String prefix = Constants.MAIL.concat(provider); 
> StringBuilder uri = new StringBuilder(); 
> 
> uri.append(getContext().getProperties().get(prefix.concat(".protocol"))).append("://");
>  
> 
> uri.append(getContext().getProperties().get(prefix.concat(".host"))).append("?");
>  
> 
> uri.append("username=").append(getContext().getProperties().get(prefix.concat(".user")));
>  
> 
> uri.append("=").append(getContext().getProperties().get(prefix.concat(".password")));
>  
> 
> uri.append("=").append(getContext().getProperties().get(prefix.concat(".folder")));
>  
> 
> 

[jira] [Commented] (CAMEL-9107) Exception thrown when reading a mail with an attached file, which name contains a semicolon

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9107:


We could do a try .. catch to ignore when attempting to check the email for 
attachments. But this would cause that you cannot get the attachments from 
those invalid emails.

You cannot even read the mail body. What would you like to be able to do? That 
Camel has some option to ignore this so the route can process, and then at  the 
end mark the mail as SEEN so the consumer can pickup the next email?

> Exception thrown when reading a mail with an attached file, which name 
> contains a semicolon
> ---
>
> Key: CAMEL-9107
> URL: https://issues.apache.org/jira/browse/CAMEL-9107
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mail
>Affects Versions: 2.15.2
>Reporter: Thierry Frossard
>Priority: Minor
> Fix For: Future
>
>
> Hi, 
> I posted this issue in Camel users forum but unfortunately got no response.
> I'm using Camel 2.15.2 with JDK 1.7 under Windows 7 and Eclipse 4.2.2 as 
> development tool. 
> My route reads from an IMAP server (IBM Lotus Notes). I have one big problem 
> : when the route handles an email, which contains a PDF attached file with a 
> semicolon in his name (for exemple my;pdf.pdf), then the route always throws 
> this exception : 
> Failed to extract body due to: Unable to load BODYSTRUCTURE. 
> 4.08.15 15:10:11:313 CEST] 0172 SystemOut O [15:10:11.313] WARN  
> [Camel (Mail vers Indexation) thread #0 - imap://myimapserver.ch] 
> org.apache.camel.util.CamelLogger.log:224 : Caused by: 
> [org.apache.camel.RuntimeCamelException - Failed to extract body due to: 
> Unable to load BODYSTRUCTURE. Exchange: Exchange[MailMessage@0x862446e3]. 
> Message: com.sun.mail.imap.IMAPMessage@16e6c70e] 
> org.apache.camel.RuntimeCamelException: Failed to extract body due to: Unable 
> to load BODYSTRUCTURE. Exchange: Exchange[MailMessage@0x862446e3]. Message: 
> com.sun.mail.imap.IMAPMessage@16e6c70e 
> at 
> org.apache.camel.component.mail.MailBinding.extractBodyFromMail(MailBinding.java:275)
>  ~[camel-mail-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.component.mail.MailMessage.createBody(MailMessage.java:103) 
> ~[camel-mail-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41) 
> ~[camel-core-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.component.mail.MailConsumer.createExchanges(MailConsumer.java:326)
>  ~[camel-mail-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:121) 
> ~[camel-mail-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>  [camel-core-2.15.2.jar:2.15.2] 
> at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>  [camel-core-2.15.2.jar:2.15.2] 
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:482) 
> [na:1.7.0] 
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:315) 
> [na:1.7.0] 
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:189)
>  [na:1.7.0] 
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
>  [na:1.7.0] 
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
>  [na:1.7.0] 
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
>  [na:1.7.0] 
> at java.lang.Thread.run(Thread.java:804) [na:1.7.0] 
> Caused by: javax.mail.MessagingException: Unable to load BODYSTRUCTURE 
> at 
> com.sun.mail.imap.IMAPMessage.loadBODYSTRUCTURE(IMAPMessage.java:1261) 
> ~[com.ibm.ws.prereq.javamail.jar:na] 
> at com.sun.mail.imap.IMAPMessage.getDataHandler(IMAPMessage.java:597) 
> ~[com.ibm.ws.prereq.javamail.jar:na] 
> at javax.mail.internet.MimeMessage.getContent(MimeMessage.java:1395) 
> ~[com.ibm.ws.prereq.javamail.jar:na] 
> at 
> org.apache.camel.component.mail.MailBinding.extractBodyFromMail(MailBinding.java:247)
>  ~[camel-mail-2.15.2.jar:2.15.2] 
> ... 13 common frames omitted 
> Here is the route (very simple) : 
>   @Override 
>   public void configure() throws Exception { 
> from(getPropertiesUri()) 
> /**/.to("log:dummy"); 
>   } 
>   protected String getPropertiesUri() { 
> String prefix = Constants.MAIL.concat(provider); 
> StringBuilder uri = new StringBuilder(); 
> 
> uri.append(getContext().getProperties().get(prefix.concat(".protocol"))).append("://");
>  

[jira] [Commented] (CAMEL-9733) enable dynamic job name in component spring-batch

[Jose Luis Pedrosa (JIRA)]

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

Jose Luis Pedrosa commented on CAMEL-9733:
--

I've created the pull request,

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

I've added some extra tests, and previous tests are passing. I hope it's 
enough. 

Thanks!

> enable dynamic job name in component spring-batch
> -
>
> Key: CAMEL-9733
> URL: https://issues.apache.org/jira/browse/CAMEL-9733
> Project: Camel
>  Issue Type: Wish
>  Components: camel-spring-batch
>Affects Versions: 2.16.2, 2.17.0
> Environment: any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>   Original Estimate: 16m
>  Remaining Estimate: 16m
>
> Hi
> Currently springBatch accepts a parameter jobName in the url, which is 
> evaluated during the creation of the endpoint.
> This makes impossible to launch different jobs dinamically.The requested 
> feature would be to make it message context based, in the headers with a 
> parameter 
> "jobNameHeader", which would be evaluated per message. In a similar way as 
> SQL and the columns value parameters.
> If the project is interested and willing to incorporate it into the sources, 
> I could offer me to code it.



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

[jira] [Commented] (CAMEL-9733) enable dynamic job name in component spring-batch

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-9733:
---

GitHub user jlpedrosa opened a pull request:

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

Added support for dynamic spring batch job invoication based on message 
header

Pull request for issue: https://issues.apache.org/jira/browse/CAMEL-9733


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

$ git pull https://github.com/jlpedrosa/camel CAMEL-9733

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

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


commit d06d850cf0a6fe44790a8eda377f56a1514be1a6
Author: Joseluis Pedrosa 
Date:   2016-04-28T14:11:21Z

patch to support dynamic job execution based on message headers for 
sprinbatch component
https://issues.apache.org/jira/browse/CAMEL-9733




> enable dynamic job name in component spring-batch
> -
>
> Key: CAMEL-9733
> URL: https://issues.apache.org/jira/browse/CAMEL-9733
> Project: Camel
>  Issue Type: Wish
>  Components: camel-spring-batch
>Affects Versions: 2.16.2, 2.17.0
> Environment: any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>   Original Estimate: 16m
>  Remaining Estimate: 16m
>
> Hi
> Currently springBatch accepts a parameter jobName in the url, which is 
> evaluated during the creation of the endpoint.
> This makes impossible to launch different jobs dinamically.The requested 
> feature would be to make it message context based, in the headers with a 
> parameter 
> "jobNameHeader", which would be evaluated per message. In a similar way as 
> SQL and the columns value parameters.
> If the project is interested and willing to incorporate it into the sources, 
> I could offer me to code it.



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

[jira] [Commented] (CAMEL-9552) Cannot consume and produce to beanstalk component in the same route

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9552:


A workaround is to use




> Cannot consume and produce to beanstalk component in the same route
> ---
>
> Key: CAMEL-9552
> URL: https://issues.apache.org/jira/browse/CAMEL-9552
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.15.0, 2.16.0
>Reporter: J Smith
>
> It appears that when creating a route that consumes from one beanstalk tube 
> and produces to another, the exchange headers from the consumer somehow get 
> mixed in with the producer and cause errors.
> Example route:
> .from("beanstalk://localhost?tube=A")
> .setBody("hello")
> .to("beanstalk://localhost?tube=B")



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

[jira] [Resolved] (CAMEL-6256) Camel xmpp dynamic router is not sending incoming messages to openfire upon first failed groupchatroom join

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-6256.

   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: (was: Future)
   2.18.0
   2.17.1
   2.16.4

The stale connection is not kept anymore, but only a working connection is set 
to be used.

> Camel xmpp dynamic router is not sending incoming messages to openfire upon 
> first failed groupchatroom join
> ---
>
> Key: CAMEL-6256
> URL: https://issues.apache.org/jira/browse/CAMEL-6256
> Project: Camel
>  Issue Type: Bug
>  Components: camel-xmpp
>Affects Versions: 2.10.3
> Environment: camel xmpp routing with openfire xmpp server.  Used 
> groupchat configurations
>Reporter: Prakash Shetty
>Assignee: Claus Ibsen
>Priority: Minor
>  Labels: connection, groupchat, xmpp
> Fix For: 2.16.4, 2.17.1, 2.18.0
>
>
> Reference : 
> http://camel.465427.n5.nabble.com/Camel-xmpp-dynamic-router-is-not-connecting-to-openfire-td5730506.html#a5730537
> {code:xml} 
> 
> 
>
>  method="processEvent"/>
> 
>  
> {code}
> In eventRouterBean's processEvent method, we are building xmpp groupchat room 
> url depending upon the message and forwading the same message into respective 
> groupchatrooms. 
> If resulting groupchat room is not existing, it will log message 
> WARN 2013-04-05 17:55:48,190 (UnitOfWorkProcessor.java processAsync:162) - 
> Caught unhandled exception while processing ExchangeId: 
> ID-INGBTCPIC8NB038-63130-1365164745141-0-3 
> org.apache.camel.FailedToCreateProducerException: Failed to create Producer 
> for endpoint: 
> Endpoint[xmpp://:5222/?password=**=zone_4fc100e4-d004-4a0b-a7e2-7cf910585af6_51=zone_4fc100e4-d004-4a0b-a7e2-7cf910585af6_51%40conference.test.com=ispf.com=messagepublisher%40test.com].
>  Reason: not-allowed(405) 
> at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:395) 
> at 
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:278) 
> at 
> org.apache.camel.processor.RoutingSlip.processExchange(RoutingSlip.java:280) 
> at 
> org.apache.camel.processor.RoutingSlip.doRoutingSlip(RoutingSlip.java:205) 
> at 
> org.apache.camel.processor.RoutingSlip.process(RoutingSlip.java:135) 
> at 
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
>  
> at 
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
>  
> at 
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
>  
> at 
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73)
>  
> at 
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
>  
> and .. 
> Caused by: not-allowed(405) 
> at 
> org.jivesoftware.smackx.muc.MultiUserChat.join(MultiUserChat.java:501) 
> at 
> org.apache.camel.component.xmpp.XmppGroupChatProducer.doStart(XmppGroupChatProducer.java:84)
>  
> at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:60) 
> at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:62) 
> at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:393) 
> ... 40 more 
> This is still fine. 
> But issue is if I create a groupchat room in openfire, it should forward new 
> incoming message to same groupchat room. But it is not forwarding.
> It is keep on logging error message as 'Not connected to the server' 
> repeatedly for all messages.
> But if I restart the camel context, then it starts working. 
> Looks like it is caching url and its connection as not allowed in dynamic 
> router. 
> What will be the solution? 
> And even the exception is thowing at ProducerCache.doGetProducer().. 
> So how to clear cache for failed connections?



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

[jira] [Commented] (CAMEL-9733) enable dynamic job name in component spring-batch

[Jose Luis Pedrosa (JIRA)]

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

Jose Luis Pedrosa commented on CAMEL-9733:
--

Ok, Then I'll use a keyword to allow the backwards compatible bheaviour, and 
the dynamic one, like jobName "dynamic".  



> enable dynamic job name in component spring-batch
> -
>
> Key: CAMEL-9733
> URL: https://issues.apache.org/jira/browse/CAMEL-9733
> Project: Camel
>  Issue Type: Wish
>  Components: camel-spring-batch
>Affects Versions: 2.16.2, 2.17.0
> Environment: any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>   Original Estimate: 16m
>  Remaining Estimate: 16m
>
> Hi
> Currently springBatch accepts a parameter jobName in the url, which is 
> evaluated during the creation of the endpoint.
> This makes impossible to launch different jobs dinamically.The requested 
> feature would be to make it message context based, in the headers with a 
> parameter 
> "jobNameHeader", which would be evaluated per message. In a similar way as 
> SQL and the columns value parameters.
> If the project is interested and willing to incorporate it into the sources, 
> I could offer me to code it.



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

[jira] [Commented] (CAMEL-9643) CXF SOAP consumer fails when running in Karaf

[John Yin (JIRA)]

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

John Yin commented on CAMEL-9643:
-

Hi Claus,

Thanks for reaching out and following up on this issue.  With 2.17.0, I have 
not been able to install it successfully in Karaf 4.0.4.  When I install my 
application bundle, I received an error:

Exception:
Configuration problem: Failed to import bean definitions from URL location 
[classpath:META-INF/spring/camel-cxf.xml]
Offending resource: URL [bundle://188.0:0/META-INF/spring/camel-context.xml]; 
nested exception is 
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: 
Configuration problem: Unable to locate Spring NamespaceHandler for XML schema 
namespace [http://camel.apache.org/schema/cxf]
Offending resource: OSGi 
resource[classpath:META-INF/spring/camel-cxf.xml|bnd.id=188|bnd.sym=TestCxfWs]

In the release notes, there was a mentioning about camel-spring not installed 
by default.  But camel-spring is brought in by camel-cxf automatically.  

Here is what I installed in karaf 4.0.4:

feature:repo-add cxf 3.1.6
feature:install cxf cxf-rt-security
feature:repo-add camel 2.17.0
feature:install camel-core camel-cxf camel-groovy

bundle:install -s file:/.../TestCxfWs-1.0-SNAPSHOT.jar

Thank you for your help!

> CXF SOAP consumer fails when running in Karaf
> -
>
> Key: CAMEL-9643
> URL: https://issues.apache.org/jira/browse/CAMEL-9643
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxf, karaf
>Affects Versions: 2.16.2
> Environment: Windows 10 Pro.  Java 1.8.  Karaf 4.0.4.  CXF 3.1.4
>Reporter: John Yin
> Attachments: TestCxfWs-submit.zip
>
>
> A simple Camel CXF SOAP web services consumer (server) works fine in 
> standalone mode.  But when deploying it in Karaf, it would fail if Camel 
> 2.16.x is used.  It would work fine if 2.15.x is used.  streamCache is set to 
> true.  The following error was received.  A zip file is attached containing a 
> maven project (along with Karaf config info) that can reproduce this issue.  
> This is critical because we cannot move to 2.16.x until this issue is 
> resolved.
> javax.xml.transform.TransformerException: Can't transform a Source of type 
> javax.xml.transform.stax.StAXSource 
> at 
> org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:419)
>  
> at 
> org.apache.camel.converter.jaxp.XmlConverter.toResult(XmlConverter.java:132) 
> at 
> org.apache.camel.converter.jaxp.XmlConverter.toResult(XmlConverter.java:116) 
> at 
> org.apache.camel.component.cxf.converter.CachedCxfPayload.(CachedCxfPayload.java:75)
>  
> at 
> org.apache.camel.component.cxf.converter.CxfPayloadConverter.cxfPayLoadToStreamCache(CxfPayloadConverter.java:118)
>  
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)[:1.8.0_60] 
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_60]
>  
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_60]
>  
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_60] 
> at 
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1243)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:293)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.convertTo(BaseTypeConverterRegistry.java:120)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.core.osgi.OsgiTypeConverter.convertTo(OsgiTypeConverter.java:117)[171:org.apache.camel.camel-spring:2.16.2]
>  
> at 
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:72)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:47)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.impl.DefaultStreamCachingStrategy.cache(DefaultStreamCachingStrategy.java:189)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.processor.CamelInternalProcessor$StreamCachingAdvice.before(CamelInternalProcessor.java:765)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.processor.CamelInternalProcessor$StreamCachingAdvice.before(CamelInternalProcessor.java:744)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> 

[jira] [Commented] (CAMEL-9733) enable dynamic job name in component spring-batch

[Tomas Rohovsky (JIRA)]

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

Tomas Rohovsky commented on CAMEL-9733:
---

You still need to declare initial path of the endpoint. There isn't (and 
shouldn't exist) a way how to omit it

> enable dynamic job name in component spring-batch
> -
>
> Key: CAMEL-9733
> URL: https://issues.apache.org/jira/browse/CAMEL-9733
> Project: Camel
>  Issue Type: Wish
>  Components: camel-spring-batch
>Affects Versions: 2.16.2, 2.17.0
> Environment: any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>   Original Estimate: 16m
>  Remaining Estimate: 16m
>
> Hi
> Currently springBatch accepts a parameter jobName in the url, which is 
> evaluated during the creation of the endpoint.
> This makes impossible to launch different jobs dinamically.The requested 
> feature would be to make it message context based, in the headers with a 
> parameter 
> "jobNameHeader", which would be evaluated per message. In a similar way as 
> SQL and the columns value parameters.
> If the project is interested and willing to incorporate it into the sources, 
> I could offer me to code it.



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

[jira] [Resolved] (CAMEL-6376) The doCatch(xxx).handled(false) affects all catch clauses

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-6376.

Resolution: Won't Fix
  Assignee: Claus Ibsen

> The doCatch(xxx).handled(false) affects all catch clauses
> -
>
> Key: CAMEL-6376
> URL: https://issues.apache.org/jira/browse/CAMEL-6376
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core, eip
>Affects Versions: 2.11.0
>Reporter: Guillaume Nodet
>Assignee: Claus Ibsen
>Priority: Minor
>
> The reason is that doCatch returns the TryDefinition and the handled() 
> implementation does not support block definitions.



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

[jira] [Resolved] (CAMEL-6433) Invalid KeyStore format error is generated using camel websocket secure on osgi platform

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-6433.

   Resolution: Fixed
Fix Version/s: (was: 2.17.1)

There were a bunch of changes so pushing this to master for know

> Invalid KeyStore format error is generated using camel websocket secure on 
> osgi platform
> 
>
> Key: CAMEL-6433
> URL: https://issues.apache.org/jira/browse/CAMEL-6433
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mina2, camel-websocket, osgi
>Reporter: Charles Moulliard
>Assignee: Claus Ibsen
> Fix For: 2.18.0
>
> Attachments: Screen Shot 2013-06-06 at 10.21.53.png
>
>
> When the following camel websocket secure route is deployed on karaf, we get 
> this error 
> {code}
> Caused by: java.io.IOException: Invalid keystore format
>   at 
> sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:633)[:1.6.0_45]
>   at 
> sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)[:1.6.0_45]
>   at java.security.KeyStore.load(KeyStore.java:1185)[:1.6.0_45]
>   at 
> org.apache.camel.util.jsse.KeyStoreParameters.createKeyStore(KeyStoreParameters.java:175)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
>   at 
> org.apache.camel.util.jsse.KeyManagersParameters.createKeyManagers(KeyManagersParameters.java:108)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
>   at 
> org.apache.camel.util.jsse.SSLContextParameters.createSSLContext(SSLContextParameters.java:236)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
> {code}
> {code}
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:camel="http://camel.apache.org/schema/spring;
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>   http://www.springframework.org/schema/beans/spring-beans.xsd
>http://camel.apache.org/schema/spring
>   http://camel.apache.org/schema/spring/camel-spring.xsd;>
>  class="org.apache.activemq.camel.component.ActiveMQComponent">
> 
> 
>  id="sslContextParameters">
>  keyPassword="changeit">
>  resource="jsse/websocket.jks"
>   password="changeit"/>
> 
> 
>  resource="jsse/websocket.jks"
>   password="changeit"/>
> 
>   
>   http://camel.apache.org/schema/spring;>
> 
>   com.fusesource.examples.camel.websocket.secure
> 
>   
> ...
>
> from("activemq:topic:newsTopic").routeId("fromJMStoWebSocketSecureNews")
>  .log(LoggingLevel.DEBUG, ">> News info received : ${body}")
>  .delay(5000)
>  .to("websocket://0.0.0.0:8443/newsTopic?sendToAll=true" +
>  
> "=#sslContextParameters=classpath:webapp");
> {code}



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

[jira] [Commented] (CAMEL-6433) Invalid KeyStore format error is generated using camel websocket secure on osgi platform

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-6433:


Also I think we should let the ClassResolver load the resource first instead of 
trying the TCCL and whatnot known tricks.

> Invalid KeyStore format error is generated using camel websocket secure on 
> osgi platform
> 
>
> Key: CAMEL-6433
> URL: https://issues.apache.org/jira/browse/CAMEL-6433
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mina2, camel-websocket, osgi
>Reporter: Charles Moulliard
>Assignee: Claus Ibsen
> Fix For: 2.17.1, 2.18.0
>
> Attachments: Screen Shot 2013-06-06 at 10.21.53.png
>
>
> When the following camel websocket secure route is deployed on karaf, we get 
> this error 
> {code}
> Caused by: java.io.IOException: Invalid keystore format
>   at 
> sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:633)[:1.6.0_45]
>   at 
> sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)[:1.6.0_45]
>   at java.security.KeyStore.load(KeyStore.java:1185)[:1.6.0_45]
>   at 
> org.apache.camel.util.jsse.KeyStoreParameters.createKeyStore(KeyStoreParameters.java:175)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
>   at 
> org.apache.camel.util.jsse.KeyManagersParameters.createKeyManagers(KeyManagersParameters.java:108)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
>   at 
> org.apache.camel.util.jsse.SSLContextParameters.createSSLContext(SSLContextParameters.java:236)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
> {code}
> {code}
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:camel="http://camel.apache.org/schema/spring;
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>   http://www.springframework.org/schema/beans/spring-beans.xsd
>http://camel.apache.org/schema/spring
>   http://camel.apache.org/schema/spring/camel-spring.xsd;>
>  class="org.apache.activemq.camel.component.ActiveMQComponent">
> 
> 
>  id="sslContextParameters">
>  keyPassword="changeit">
>  resource="jsse/websocket.jks"
>   password="changeit"/>
> 
> 
>  resource="jsse/websocket.jks"
>   password="changeit"/>
> 
>   
>   http://camel.apache.org/schema/spring;>
> 
>   com.fusesource.examples.camel.websocket.secure
> 
>   
> ...
>
> from("activemq:topic:newsTopic").routeId("fromJMStoWebSocketSecureNews")
>  .log(LoggingLevel.DEBUG, ">> News info received : ${body}")
>  .delay(5000)
>  .to("websocket://0.0.0.0:8443/newsTopic?sendToAll=true" +
>  
> "=#sslContextParameters=classpath:webapp");
> {code}



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

[jira] [Commented] (CAMEL-6433) Invalid KeyStore format error is generated using camel websocket secure on osgi platform

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-6433:


We need to inject CamelContext on the SSL parameters so when it attempts to 
load those resources it can have access to the bundle classloader (via Camel's 
ClassResolver)

> Invalid KeyStore format error is generated using camel websocket secure on 
> osgi platform
> 
>
> Key: CAMEL-6433
> URL: https://issues.apache.org/jira/browse/CAMEL-6433
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mina2, camel-websocket, osgi
>Reporter: Charles Moulliard
>Assignee: Claus Ibsen
> Fix For: 2.17.1, 2.18.0
>
> Attachments: Screen Shot 2013-06-06 at 10.21.53.png
>
>
> When the following camel websocket secure route is deployed on karaf, we get 
> this error 
> {code}
> Caused by: java.io.IOException: Invalid keystore format
>   at 
> sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:633)[:1.6.0_45]
>   at 
> sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)[:1.6.0_45]
>   at java.security.KeyStore.load(KeyStore.java:1185)[:1.6.0_45]
>   at 
> org.apache.camel.util.jsse.KeyStoreParameters.createKeyStore(KeyStoreParameters.java:175)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
>   at 
> org.apache.camel.util.jsse.KeyManagersParameters.createKeyManagers(KeyManagersParameters.java:108)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
>   at 
> org.apache.camel.util.jsse.SSLContextParameters.createSSLContext(SSLContextParameters.java:236)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
> {code}
> {code}
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:camel="http://camel.apache.org/schema/spring;
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>   http://www.springframework.org/schema/beans/spring-beans.xsd
>http://camel.apache.org/schema/spring
>   http://camel.apache.org/schema/spring/camel-spring.xsd;>
>  class="org.apache.activemq.camel.component.ActiveMQComponent">
> 
> 
>  id="sslContextParameters">
>  keyPassword="changeit">
>  resource="jsse/websocket.jks"
>   password="changeit"/>
> 
> 
>  resource="jsse/websocket.jks"
>   password="changeit"/>
> 
>   
>   http://camel.apache.org/schema/spring;>
> 
>   com.fusesource.examples.camel.websocket.secure
> 
>   
> ...
>
> from("activemq:topic:newsTopic").routeId("fromJMStoWebSocketSecureNews")
>  .log(LoggingLevel.DEBUG, ">> News info received : ${body}")
>  .delay(5000)
>  .to("websocket://0.0.0.0:8443/newsTopic?sendToAll=true" +
>  
> "=#sslContextParameters=classpath:webapp");
> {code}



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

[jira] [Commented] (CAMEL-9733) enable dynamic job name in component spring-batch

[Jose Luis Pedrosa (JIRA)]

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

Jose Luis Pedrosa commented on CAMEL-9733:
--

I got troubles with one small detail (it's almost ready), how can I write an 
URI without an path? I don't manage to make the URI parses to accept it:

{code:java}
from("direct:start").to("spring-batch:mockJob").to("mock:test"); //original 
test line
from("direct:dynamic").to("spring-batch:").to("mock:test"); //URL type with 
dynamic Job
{code}

I mean as the jobName is read during the exchange it is not passed to the URI, 
but it keeps on failing:
{noformat}
[From[direct:dynamic]] -> [To[spring-batch:?]... because of Failed to resolve 
endpoint: spring-batch:// due to: Expected authority at index 15:
{noformat}

is there any way to achieve a endpoint without path? I tried to annotate the 
uri definition.. but no luck...

{code:java}
@UriPath(defaultValue = "dynamic")
@Metadata(required = "false", defaultValue = "dynamic")
  private String jobName;
{code}
  

> enable dynamic job name in component spring-batch
> -
>
> Key: CAMEL-9733
> URL: https://issues.apache.org/jira/browse/CAMEL-9733
> Project: Camel
>  Issue Type: Wish
>  Components: camel-spring-batch
>Affects Versions: 2.16.2, 2.17.0
> Environment: any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>   Original Estimate: 16m
>  Remaining Estimate: 16m
>
> Hi
> Currently springBatch accepts a parameter jobName in the url, which is 
> evaluated during the creation of the endpoint.
> This makes impossible to launch different jobs dinamically.The requested 
> feature would be to make it message context based, in the headers with a 
> parameter 
> "jobNameHeader", which would be evaluated per message. In a similar way as 
> SQL and the columns value parameters.
> If the project is interested and willing to incorporate it into the sources, 
> I could offer me to code it.



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

[jira] [Assigned] (CAMEL-6433) Invalid KeyStore format error is generated using camel websocket secure on osgi platform

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-6433:
--

Assignee: Claus Ibsen

> Invalid KeyStore format error is generated using camel websocket secure on 
> osgi platform
> 
>
> Key: CAMEL-6433
> URL: https://issues.apache.org/jira/browse/CAMEL-6433
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mina2, camel-websocket, osgi
>Reporter: Charles Moulliard
>Assignee: Claus Ibsen
> Fix For: 2.17.1, 2.18.0
>
> Attachments: Screen Shot 2013-06-06 at 10.21.53.png
>
>
> When the following camel websocket secure route is deployed on karaf, we get 
> this error 
> {code}
> Caused by: java.io.IOException: Invalid keystore format
>   at 
> sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:633)[:1.6.0_45]
>   at 
> sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)[:1.6.0_45]
>   at java.security.KeyStore.load(KeyStore.java:1185)[:1.6.0_45]
>   at 
> org.apache.camel.util.jsse.KeyStoreParameters.createKeyStore(KeyStoreParameters.java:175)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
>   at 
> org.apache.camel.util.jsse.KeyManagersParameters.createKeyManagers(KeyManagersParameters.java:108)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
>   at 
> org.apache.camel.util.jsse.SSLContextParameters.createSSLContext(SSLContextParameters.java:236)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
> {code}
> {code}
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:camel="http://camel.apache.org/schema/spring;
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>   http://www.springframework.org/schema/beans/spring-beans.xsd
>http://camel.apache.org/schema/spring
>   http://camel.apache.org/schema/spring/camel-spring.xsd;>
>  class="org.apache.activemq.camel.component.ActiveMQComponent">
> 
> 
>  id="sslContextParameters">
>  keyPassword="changeit">
>  resource="jsse/websocket.jks"
>   password="changeit"/>
> 
> 
>  resource="jsse/websocket.jks"
>   password="changeit"/>
> 
>   
>   http://camel.apache.org/schema/spring;>
> 
>   com.fusesource.examples.camel.websocket.secure
> 
>   
> ...
>
> from("activemq:topic:newsTopic").routeId("fromJMStoWebSocketSecureNews")
>  .log(LoggingLevel.DEBUG, ">> News info received : ${body}")
>  .delay(5000)
>  .to("websocket://0.0.0.0:8443/newsTopic?sendToAll=true" +
>  
> "=#sslContextParameters=classpath:webapp");
> {code}



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

[jira] [Updated] (CAMEL-6433) Invalid KeyStore format error is generated using camel websocket secure on osgi platform

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-6433:
---
Fix Version/s: 2.18.0
   2.17.1

> Invalid KeyStore format error is generated using camel websocket secure on 
> osgi platform
> 
>
> Key: CAMEL-6433
> URL: https://issues.apache.org/jira/browse/CAMEL-6433
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mina2, camel-websocket, osgi
>Reporter: Charles Moulliard
>Assignee: Claus Ibsen
> Fix For: 2.17.1, 2.18.0
>
> Attachments: Screen Shot 2013-06-06 at 10.21.53.png
>
>
> When the following camel websocket secure route is deployed on karaf, we get 
> this error 
> {code}
> Caused by: java.io.IOException: Invalid keystore format
>   at 
> sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:633)[:1.6.0_45]
>   at 
> sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)[:1.6.0_45]
>   at java.security.KeyStore.load(KeyStore.java:1185)[:1.6.0_45]
>   at 
> org.apache.camel.util.jsse.KeyStoreParameters.createKeyStore(KeyStoreParameters.java:175)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
>   at 
> org.apache.camel.util.jsse.KeyManagersParameters.createKeyManagers(KeyManagersParameters.java:108)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
>   at 
> org.apache.camel.util.jsse.SSLContextParameters.createSSLContext(SSLContextParameters.java:236)[130:org.apache.camel.camel-core:2.10.0.redhat-60024]
> {code}
> {code}
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:camel="http://camel.apache.org/schema/spring;
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>   http://www.springframework.org/schema/beans/spring-beans.xsd
>http://camel.apache.org/schema/spring
>   http://camel.apache.org/schema/spring/camel-spring.xsd;>
>  class="org.apache.activemq.camel.component.ActiveMQComponent">
> 
> 
>  id="sslContextParameters">
>  keyPassword="changeit">
>  resource="jsse/websocket.jks"
>   password="changeit"/>
> 
> 
>  resource="jsse/websocket.jks"
>   password="changeit"/>
> 
>   
>   http://camel.apache.org/schema/spring;>
> 
>   com.fusesource.examples.camel.websocket.secure
> 
>   
> ...
>
> from("activemq:topic:newsTopic").routeId("fromJMStoWebSocketSecureNews")
>  .log(LoggingLevel.DEBUG, ">> News info received : ${body}")
>  .delay(5000)
>  .to("websocket://0.0.0.0:8443/newsTopic?sendToAll=true" +
>  
> "=#sslContextParameters=classpath:webapp");
> {code}



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

[jira] [Commented] (CAMEL-6784) PollingConsumer.receiveNoWait() never returns null consuming from AMQPComponent endpoint in browsing mode

[Dmytro Puzhay (JIRA)]

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

Dmytro Puzhay commented on CAMEL-6784:
--

[~davsclaus] oh no! But why, why? :)

> PollingConsumer.receiveNoWait() never returns null consuming from 
> AMQPComponent endpoint in browsing mode
> -
>
> Key: CAMEL-6784
> URL: https://issues.apache.org/jira/browse/CAMEL-6784
> Project: Camel
>  Issue Type: Bug
>  Components: camel-amqp
>Affects Versions: 2.10.2
>Reporter: Dmytro Puzhay
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
>
> I create PollingConsumer for my AMQP queue and consume with receiveNoWait() 
> until null is received. It worked nicely in default mode, but in browsing 
> mode (queue name suffixed with "{mode: browse}", see 
> https://qpid.apache.org/books/0.12/Programming-In-Apache-Qpid/html/ch02s04.html
>  "2.4.3.3. browse" for details) my PollingConsumer keeps running infinitely.



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

[jira] [Resolved] (CAMEL-6720) SoapJaxbDataFormat not handling correctly SOAP action with request wrapper element

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-6720.

   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: (was: Future)
   2.18.0
   2.17.1
   2.16.4

Thanks Movee for the idea for the fix.

> SoapJaxbDataFormat not handling correctly SOAP action with request wrapper 
> element
> --
>
> Key: CAMEL-6720
> URL: https://issues.apache.org/jira/browse/CAMEL-6720
> Project: Camel
>  Issue Type: Bug
>  Components: camel-soap
>Affects Versions: 2.12.0
>Reporter: Ondrej Fischer
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.4, 2.17.1, 2.18.0
>
> Attachments: ServiceInterfaceStrategy.java
>
>
> If an interface to be used as SOAP service interface is configured to have 
> parameters wrapped in a request wrapper element (eg. using @RequestWrapper),
> then an attempt to invoke a its method will throw NPE:
> {code}
> java.lang.NullPointerException
>   at 
> org.apache.camel.dataformat.soap.name.ServiceInterfaceStrategy.findQNameForSoapActionOrType(ServiceInterfaceStrategy.java:207)
>   at 
> org.apache.camel.dataformat.soap.SoapJaxbDataFormat.createContentFromObject(SoapJaxbDataFormat.java:208)
>   at 
> org.apache.camel.dataformat.soap.Soap11DataFormatAdapter.doMarshal(Soap11DataFormatAdapter.java:77)
>   at 
> org.apache.camel.dataformat.soap.SoapJaxbDataFormat.marshal(SoapJaxbDataFormat.java:141)
>   at 
> org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:59)
> {code}
> The reason for this is sequence of following:
> # The ServiceInterfaceStrategy is creating a mapping of methods to MethodInfo.
> # In case of RequestWrapper, the wrapper class is used as a single input 
> TypeInfo, and no TypeInfo is being held for the real parameters.
> # At method invocation, it tries to lookup the TypeInfo in the MethodInfo, 
> but for the real parameter class, and it only contains mapping for the 
> request wrapper. So it fails with NPE.



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

[jira] [Resolved] (CAMEL-6784) PollingConsumer.receiveNoWait() never returns null consuming from AMQPComponent endpoint in browsing mode

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-6784.

Resolution: Won't Fix
  Assignee: Claus Ibsen

> PollingConsumer.receiveNoWait() never returns null consuming from 
> AMQPComponent endpoint in browsing mode
> -
>
> Key: CAMEL-6784
> URL: https://issues.apache.org/jira/browse/CAMEL-6784
> Project: Camel
>  Issue Type: Bug
>  Components: camel-amqp
>Affects Versions: 2.10.2
>Reporter: Dmytro Puzhay
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
>
> I create PollingConsumer for my AMQP queue and consume with receiveNoWait() 
> until null is received. It worked nicely in default mode, but in browsing 
> mode (queue name suffixed with "{mode: browse}", see 
> https://qpid.apache.org/books/0.12/Programming-In-Apache-Qpid/html/ch02s04.html
>  "2.4.3.3. browse" for details) my PollingConsumer keeps running infinitely.



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Catalina-Alina Dobrica (JIRA)]

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

Catalina-Alina Dobrica commented on CAMEL-9916:
---

This fix is needed but it doesn't fix the bigger part of this ticket: it does 
not add the feature of nodev/XML sjms (so that the SjmsComponent instance is 
not needed beforehand and required to be activated outside the route with a 
ConnectionFactory). Also, I need the connection factory on the endpoint level 
because in a setup of multiple camel contexts sharing the same registry I am 
restricted to using a single server or creating a new instance of sjms 
component with a different name for each server, and {code}sjms connection 
setup with options + sjms:queue:test, sjms2 setup with options + 
sjms2:queue:test, ... {code} is not nodev friendly, while 
{code}sjms:queue:test[?options]{code} with the connection configuration behind 
the scenes is much easier to use. 

Also, the idea is not that I want to share a pool across multiple camel 
contexts, it is that I don't want to, but _I am forced to share it_ when I am 
restricted to using the same registry for multiple contexts.

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Resolved] (CAMEL-7443) Remote Print URI changed to UNC Name

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-7443.

Resolution: Fixed

> Remote Print URI changed to UNC Name
> 
>
> Key: CAMEL-7443
> URL: https://issues.apache.org/jira/browse/CAMEL-7443
> Project: Camel
>  Issue Type: Bug
>  Components: camel-printer
>Affects Versions: 2.13.0
> Environment: Mac OS X with remote CUPS IPP Printer
>Reporter: Christian Mahnke
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.4, 2.17.1, 2.18.0
>
>
> I'm using a printing URI in the form of lpr://lh.abc.de:631/bbk-test 
> (Hostname changed) and getting an PrintException:
> Reason: javax.print.PrintException: No printer found with name: 
> \\lhgoe.gbv.de\bbk-test. Please verify that the host and printer are 
> registered and reachable from this machine.
> Which is true, since Camel Printer has changed my URI to a Windows UNC (see 
> backslashes).



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

[jira] [Assigned] (CAMEL-7443) Remote Print URI changed to UNC Name

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-7443:
--

Assignee: Claus Ibsen

> Remote Print URI changed to UNC Name
> 
>
> Key: CAMEL-7443
> URL: https://issues.apache.org/jira/browse/CAMEL-7443
> Project: Camel
>  Issue Type: Bug
>  Components: camel-printer
>Affects Versions: 2.13.0
> Environment: Mac OS X with remote CUPS IPP Printer
>Reporter: Christian Mahnke
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.4, 2.17.1, 2.18.0
>
>
> I'm using a printing URI in the form of lpr://lh.abc.de:631/bbk-test 
> (Hostname changed) and getting an PrintException:
> Reason: javax.print.PrintException: No printer found with name: 
> \\lhgoe.gbv.de\bbk-test. Please verify that the host and printer are 
> registered and reachable from this machine.
> Which is true, since Camel Printer has changed my URI to a Windows UNC (see 
> backslashes).



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

[jira] [Updated] (CAMEL-7443) Remote Print URI changed to UNC Name

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-7443:
---
Fix Version/s: (was: Future)
   2.18.0
   2.17.1
   2.16.4

> Remote Print URI changed to UNC Name
> 
>
> Key: CAMEL-7443
> URL: https://issues.apache.org/jira/browse/CAMEL-7443
> Project: Camel
>  Issue Type: Bug
>  Components: camel-printer
>Affects Versions: 2.13.0
> Environment: Mac OS X with remote CUPS IPP Printer
>Reporter: Christian Mahnke
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.4, 2.17.1, 2.18.0
>
>
> I'm using a printing URI in the form of lpr://lh.abc.de:631/bbk-test 
> (Hostname changed) and getting an PrintException:
> Reason: javax.print.PrintException: No printer found with name: 
> \\lhgoe.gbv.de\bbk-test. Please verify that the host and printer are 
> registered and reachable from this machine.
> Which is true, since Camel Printer has changed my URI to a Windows UNC (see 
> backslashes).



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

[jira] [Resolved] (CAMEL-9854) CXF Stream Cache contains duplicate namespace definition

[Akitoshi Yoshida (JIRA)]

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

Akitoshi Yoshida resolved CAMEL-9854.
-
   Resolution: Fixed
Fix Version/s: 2.18.0
   2.17.1
   2.16.4

> CXF Stream Cache contains duplicate namespace definition
> 
>
> Key: CAMEL-9854
> URL: https://issues.apache.org/jira/browse/CAMEL-9854
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.16.3
>Reporter: Stephan Siano
>Assignee: Akitoshi Yoshida
>Priority: Minor
> Fix For: 2.16.4, 2.17.1, 2.18.0
>
> Attachments: 
> 0001-CAMEL-9854-CXF-Stream-Cache-contains-duplicate-names.patch
>
>
> If stream caching is enabled for incoming messages in Camel-CXF and a 
> namespace defined on the SOAP envelope is also defined on the root tag of the 
> payload document the XML contained within the stream cache contains a 
> duplicate namespace definition.
> See attached unit test for details



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

[jira] [Commented] (CAMEL-9854) CXF Stream Cache contains duplicate namespace definition

[Akitoshi Yoshida (JIRA)]

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

Akitoshi Yoshida commented on CAMEL-9854:
-

Hi Claus,
I think I committed the patch but forgot to set this ticket as resolved.
thanks.
regards, aki

> CXF Stream Cache contains duplicate namespace definition
> 
>
> Key: CAMEL-9854
> URL: https://issues.apache.org/jira/browse/CAMEL-9854
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.16.3
>Reporter: Stephan Siano
>Assignee: Akitoshi Yoshida
>Priority: Minor
> Attachments: 
> 0001-CAMEL-9854-CXF-Stream-Cache-contains-duplicate-names.patch
>
>
> If stream caching is enabled for incoming messages in Camel-CXF and a 
> namespace defined on the SOAP envelope is also defined on the root tag of the 
> payload document the XML contained within the stream cache contains a 
> duplicate namespace definition.
> See attached unit test for details



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

[jira] [Commented] (CAMEL-9836) Add file id of the gridfs file created in the header of the exchange

[Jose Luis Pedrosa (JIRA)]

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

Jose Luis Pedrosa commented on CAMEL-9836:
--

Pull request closed, thanks!

> Add file id of the gridfs file created in the header of the exchange
> 
>
> Key: CAMEL-9836
> URL: https://issues.apache.org/jira/browse/CAMEL-9836
> Project: Camel
>  Issue Type: Wish
>  Components: camel-mongodb
>Affects Versions: 2.17.0
> Environment: Any
>Reporter: Jose Luis Pedrosa
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.17.1, 2.18.0
>
>
> Currently the camel-mongodb-gridfs component (which is not available in this 
> Jira) when a file is cretated does not return back the Id (_id) of the file 
> created, it only returns  the filename
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> {code}
> mongodb api has the method getid: 
> http://api.mongodb.org/java/current/com/mongodb/gridfs/GridFSFile.html#getId--
> So i'd like to ask to:
> a) create a header field (maybe GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED)
> b) Add the header after the creation
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> 
> exchange.getIn().setHeader(GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED, 
> gfsFile.getId());
> {code}
> Of course I can create a PR myself, but I think the administrative work would 
> be more? Up to you guys.



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

[jira] [Commented] (CAMEL-9836) Add file id of the gridfs file created in the header of the exchange

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-9836:
---

Github user jlpedrosa closed the pull request at:

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


> Add file id of the gridfs file created in the header of the exchange
> 
>
> Key: CAMEL-9836
> URL: https://issues.apache.org/jira/browse/CAMEL-9836
> Project: Camel
>  Issue Type: Wish
>  Components: camel-mongodb
>Affects Versions: 2.17.0
> Environment: Any
>Reporter: Jose Luis Pedrosa
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.17.1, 2.18.0
>
>
> Currently the camel-mongodb-gridfs component (which is not available in this 
> Jira) when a file is cretated does not return back the Id (_id) of the file 
> created, it only returns  the filename
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> {code}
> mongodb api has the method getid: 
> http://api.mongodb.org/java/current/com/mongodb/gridfs/GridFSFile.html#getId--
> So i'd like to ask to:
> a) create a header field (maybe GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED)
> b) Add the header after the creation
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> 
> exchange.getIn().setHeader(GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED, 
> gfsFile.getId());
> {code}
> Of course I can create a PR myself, but I think the administrative work would 
> be more? Up to you guys.



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

[jira] [Assigned] (CAMEL-9476) camel-bindy doesn't pad fixed length records

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli reassigned CAMEL-9476:
--

Assignee: Luca Burgazzoli

> camel-bindy doesn't pad fixed length records
> 
>
> Key: CAMEL-9476
> URL: https://issues.apache.org/jira/browse/CAMEL-9476
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-bindy
>Affects Versions: 2.16.1
>Reporter: Jostein Gogstad
>Assignee: Luca Burgazzoli
>Priority: Minor
>
> Reading CAMEL-6039 one gets the impression that camel-bindy will pad fixed 
> length records if the input record is smaller than the fixed length.
> https://camel.apache.org/bindy.html:
> {quote}
> When the size of the data does not fill completely the length of the field, 
> we can then add 'padd' characters.
> {quote}
> This is not the case as the following test demonstrates. It fails with
> {code:none}
> java.lang.IllegalArgumentException: Size of the record: 5 is not equal to the 
> value provided in the model: 10
>   at 
> org.apache.camel.dataformat.bindy.fixed.BindyFixedLengthDataFormat.createModel(BindyFixedLengthDataFormat.java:248)
>   at 
> org.apache.camel.dataformat.bindy.fixed.BindyFixedLengthDataFormat.unmarshal(BindyFixedLengthDataFormat.java:209)
>   at 
> org.apache.camel.processor.UnmarshalProcessor.process(UnmarshalProcessor.java:69)
> {code}
> {code:java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.dataformat.bindy.annotation.DataField;
> import org.apache.camel.dataformat.bindy.annotation.FixedLengthRecord;
> import org.apache.camel.model.dataformat.BindyType;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> public class BindyTest extends CamelTestSupport {
> public static final String URI_DIRECT_UNMARSHAL = "direct:unmarshall";
> public static final String URI_MOCK_UNMARSHAL_RESULT = 
> "mock:unmarshal_result";
> @EndpointInject(uri = URI_MOCK_UNMARSHAL_RESULT)
> private MockEndpoint unmarhsalResult;
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from(URI_DIRECT_UNMARSHAL)
> .unmarshal().bindy(BindyType.Fixed, MyBindyModel.class)
> .to(URI_MOCK_UNMARSHAL_RESULT);
> }
> };
> }
> @Test
> public void testUnmarshal() throws Exception {
> unmarhsalResult.expectedMessageCount(1);
> template.sendBody(URI_DIRECT_UNMARSHAL, "foo  \r\n");
> unmarhsalResult.assertIsSatisfied();
> MyBindyModel myBindyModel = 
> unmarhsalResult.getReceivedExchanges().get(0).getIn().getBody(MyBindyModel.class);
> assertEquals("foo  ", myBindyModel.foo);
> }
> @FixedLengthRecord(length = 10)
> public class MyBindyModel {
> @DataField(pos = 0, length = 5)
> String foo;
> @DataField(pos = 5, length = 5)
> String bar;
> }
> }
> {code}



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Catalina-Alina Dobrica (JIRA)]

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

Catalina-Alina Dobrica commented on CAMEL-9916:
---

Yes, this fix was added in my patch, but the ConnectionResource was handled on 
a per endpoint level

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9916:


You need to configure a custom ConnectionResource to share the pool across 
multiple camel contexts. And then also this fix that do not close the pool when 
using a custom connection resource, as then you are responsible for its 
lifecycle.
https://github.com/apache/camel/blob/master/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java#L119

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Commented] (CAMEL-7489) Bindy CSV DataField position requires @Section or @KeyValuePairDataField

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-7489:


Can you explain what is the problem?

> Bindy CSV DataField position requires @Section or  @KeyValuePairDataField
> -
>
> Key: CAMEL-7489
> URL: https://issues.apache.org/jira/browse/CAMEL-7489
> Project: Camel
>  Issue Type: Bug
>  Components: camel-bindy
>Reporter: Marco Carvalho
>Priority: Minor
>
> When using DataField as in "case 8" of the documentation page (sorry, no 
> anchor links):
> http://camel.apache.org/bindy.html
> A exception is risen for a missing Section annotation.
> "@Section and/or @KeyValuePairDataField have not been defined"



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

[jira] [Commented] (CAMEL-9103) camel-cxf does not handle soapfaults with ws-addressing headers in async mode

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9103:


Can you upload the attachment as a plain zip so anybody can download.
And try with newer release of Apache Camel.

> camel-cxf does not handle soapfaults with ws-addressing headers in async mode
> -
>
> Key: CAMEL-9103
> URL: https://issues.apache.org/jira/browse/CAMEL-9103
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxf
>Affects Versions: 2.15.3
>Reporter: Bjørn Hilstad
>Priority: Minor
> Attachments: camel-jboss-web.7z
>
>
> I am invoking a SOAP 1.1 webservice with WS-Addressing using camel-cxf. When 
> the webservice returns a soapfault that includes a ws-addressing header 
> (http://www.w3.org/2005/08/addressing/soap/fault) 
> which I believe is allowed per spec (ws-addressing) I can see in logs that 
> cxf processes the response but the response never reaches Camel (would be 
> handled by the DefaultErrorHandler). The thread just hangs forever.
> I have been able to get the same test to work if I configure the camel 
> endpoint for cxf to use synchronous=true.
> I am attaching a maven project that contains a test that reproduces the 
> issue. The test uses wiremock as a stub to return the response.
> If the endpoint in the camelcontext is changed to use synchronous=true the 
> test succeeds (it gets the soapfault that is expected).



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

[jira] [Updated] (CAMEL-9200) Context component conflates endpoints with the same local id from different CamelContexts

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9200:
---
Priority: Minor  (was: Major)

> Context component conflates endpoints with the same local id from different 
> CamelContexts
> -
>
> Key: CAMEL-9200
> URL: https://issues.apache.org/jira/browse/CAMEL-9200
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.15.3
>Reporter: Aaron Birkland
>Priority: Minor
> Attachments: CAMEL-9200.patch
>
>
> The context component experiences clashes between endpoints with the same 
> local name, but from different contexts.  If two contexts both contain a 
> local endpoint "direct:out", any route involving both endpoints will fail to 
> start due to a FailedToStartRouteException; "Multiple consumers for the same 
> endpoint is not allowed: Endpoint[direct://out]."
> As an example, the following set of routes will fail due to this issue:
> from("direct:in").to("blackBox:in");
> from("blackBox:out").to("direct:out");
> from("direct:out").to("mock:results");
> See  thread:
> http://camel.465427.n5.nabble.com/Context-Component-issue-td5770975.html



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

[jira] [Updated] (CAMEL-9378) camel-leveldb - Camel cannot be restarted - IO Error

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9378:
---
Priority: Minor  (was: Major)

> camel-leveldb - Camel cannot be restarted - IO Error
> 
>
> Key: CAMEL-9378
> URL: https://issues.apache.org/jira/browse/CAMEL-9378
> Project: Camel
>  Issue Type: Bug
>  Components: camel-leveldb
>Affects Versions: 2.15.2
>Reporter: Sergei Gorbunov
>Priority: Minor
>
> I am using "org.apache.camel.component.leveldb.LevelDBAggregationRepository" 
> as aggregation repository. Camel context imported to ActiveMQ context. 
> ActiveMQ installed as windows service.
> Case:
> 1. Execute restart command on activemq.
> 2. Camel cannot start.
> 3. If then start service manually - camel successfully starts.
> Exception:
> {code}
> INFO   | jvm 1| 2015/11/30 09:50:58 | {}
> INFO   | jvm 1| 2015/11/30 10:02:46 | Restarting broker
> INFO   | jvm 1| 2015/11/30 10:02:46 | Loading message broker from: 
> xbean:activemq.xml
> INFO   | jvm 1| 2015/11/30 10:02:47 | {}
> INFO   | jvm 1| 2015/11/30 10:02:54 | ERROR: java.lang.RuntimeException: 
> Failed to execute broker build task. Reason: 
> org.apache.camel.RuntimeCamelException: java.lang.RuntimeException: Error 
> opening LevelDB with file 
> F:\AMQ\bin\win64\..\..\data\aggregation\aggregate_%2A.%2A
> INFO   | jvm 1| 2015/11/30 10:02:54 | java.lang.RuntimeException: Failed 
> to execute broker build task. Reason: org.apache.camel.RuntimeCamelException: 
> java.lang.RuntimeException: Error opening LevelDB with file 
> F:\AMQ\bin\win64\..\..\data\aggregation\aggregate_%2A.%2A
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:101)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:150)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> java.lang.reflect.Method.invoke(Unknown Source)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.apache.activemq.console.Main.runTaskClass(Main.java:262)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.apache.activemq.console.Main.main(Main.java:115)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> java.lang.reflect.Method.invoke(Unknown Source)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at java.lang.Thread.run(Unknown 
> Source)
> INFO   | jvm 1| 2015/11/30 10:02:54 | Caused by: 
> org.apache.camel.RuntimeCamelException: java.lang.RuntimeException: Error 
> opening LevelDB with file 
> F:\AMQ\bin\win64\..\..\data\aggregation\aggregate_%2A.%2A
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1619)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:123)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:332)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)
> INFO   | jvm 1| 2015/11/30 10:02:54 | at 
> 

[jira] [Commented] (CAMEL-9200) Context component conflates endpoints with the same local id from different CamelContexts

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9200:


The camel-context component is depreacted

> Context component conflates endpoints with the same local id from different 
> CamelContexts
> -
>
> Key: CAMEL-9200
> URL: https://issues.apache.org/jira/browse/CAMEL-9200
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.15.3
>Reporter: Aaron Birkland
> Attachments: CAMEL-9200.patch
>
>
> The context component experiences clashes between endpoints with the same 
> local name, but from different contexts.  If two contexts both contain a 
> local endpoint "direct:out", any route involving both endpoints will fail to 
> start due to a FailedToStartRouteException; "Multiple consumers for the same 
> endpoint is not allowed: Endpoint[direct://out]."
> As an example, the following set of routes will fail due to this issue:
> from("direct:in").to("blackBox:in");
> from("blackBox:out").to("direct:out");
> from("direct:out").to("mock:results");
> See  thread:
> http://camel.465427.n5.nabble.com/Context-Component-issue-td5770975.html



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

[jira] [Commented] (CAMEL-9421) CxfEndpoint Not using proper Service Factory when javax.jws.WebService is proxied

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9421:


This is an old version of Camel. Try with latest release.

> CxfEndpoint Not using proper Service Factory when javax.jws.WebService is 
> proxied
> -
>
> Key: CAMEL-9421
> URL: https://issues.apache.org/jira/browse/CAMEL-9421
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxf
>Affects Versions: 2.13.3
> Environment: karaf 3.0.2
>Reporter: Joseph Kampf
>
> Clearing out the karaf/data/cache directory and then doing a fresh deploy of 
> the Bundle works fine.  
> However after restarting Karaf the 
> org.apache.cxf.jaxws.JaxWsServerFactoryBean is not used by the CxfEndpoint.  
> Instead the org.apache.cxf.frontend.ServerFactoryBean is used.  This causes 
> the mapping of WSDL Operations to SEI methods to not work.  
> This results in error messages:
> {quote}
> 2015-12-15 09:51:18,729 | WARN  | xtenderThread-42 | 
> ReflectionServiceFactoryBean | 194 - org.apache.cxf.cxf-rt-core - 2.7.11 
> | No method was found for the WSDL operation <%WSDL Operation%>{quote}
> It also causes the CXF page to not list the WSDL Operations under the SOAP 
> Port.
> The reason this is happening is because the annotations that are on the SEI 
> class are proxied.  This causes the annotation check in 
> org.apache.camel.component.cxf.CxfSpringEndpoint.createServerFactoryBean() to 
> seem as if the SEI does not have the javax.jws.WebService annotation.
> The annotation is on the list of annotations for the SEI, but they are 
> proxied by sun.reflect.annotation.AnnotationInvocationHandler.
> One solution I see would be to change the implementation of 
> org.apache.camel.component.cxf.CxfEndpointUtils.hasAnnotation() method.  
> Instead of relying on Class.getAnnoation(), instead loop through the 
> annotations on the class and not only check the annotation class directly, 
> but also try to reach into the annotation to determine if it is a proxy of 
> the annotation in question.



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

[jira] [Updated] (CAMEL-9476) camel-bindy doesn't pad fixed length records

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9476:
---
Issue Type: Improvement  (was: Bug)

> camel-bindy doesn't pad fixed length records
> 
>
> Key: CAMEL-9476
> URL: https://issues.apache.org/jira/browse/CAMEL-9476
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-bindy
>Affects Versions: 2.16.1
>Reporter: Jostein Gogstad
>Priority: Minor
>
> Reading CAMEL-6039 one gets the impression that camel-bindy will pad fixed 
> length records if the input record is smaller than the fixed length.
> https://camel.apache.org/bindy.html:
> {quote}
> When the size of the data does not fill completely the length of the field, 
> we can then add 'padd' characters.
> {quote}
> This is not the case as the following test demonstrates. It fails with
> {code:none}
> java.lang.IllegalArgumentException: Size of the record: 5 is not equal to the 
> value provided in the model: 10
>   at 
> org.apache.camel.dataformat.bindy.fixed.BindyFixedLengthDataFormat.createModel(BindyFixedLengthDataFormat.java:248)
>   at 
> org.apache.camel.dataformat.bindy.fixed.BindyFixedLengthDataFormat.unmarshal(BindyFixedLengthDataFormat.java:209)
>   at 
> org.apache.camel.processor.UnmarshalProcessor.process(UnmarshalProcessor.java:69)
> {code}
> {code:java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.dataformat.bindy.annotation.DataField;
> import org.apache.camel.dataformat.bindy.annotation.FixedLengthRecord;
> import org.apache.camel.model.dataformat.BindyType;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> public class BindyTest extends CamelTestSupport {
> public static final String URI_DIRECT_UNMARSHAL = "direct:unmarshall";
> public static final String URI_MOCK_UNMARSHAL_RESULT = 
> "mock:unmarshal_result";
> @EndpointInject(uri = URI_MOCK_UNMARSHAL_RESULT)
> private MockEndpoint unmarhsalResult;
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from(URI_DIRECT_UNMARSHAL)
> .unmarshal().bindy(BindyType.Fixed, MyBindyModel.class)
> .to(URI_MOCK_UNMARSHAL_RESULT);
> }
> };
> }
> @Test
> public void testUnmarshal() throws Exception {
> unmarhsalResult.expectedMessageCount(1);
> template.sendBody(URI_DIRECT_UNMARSHAL, "foo  \r\n");
> unmarhsalResult.assertIsSatisfied();
> MyBindyModel myBindyModel = 
> unmarhsalResult.getReceivedExchanges().get(0).getIn().getBody(MyBindyModel.class);
> assertEquals("foo  ", myBindyModel.foo);
> }
> @FixedLengthRecord(length = 10)
> public class MyBindyModel {
> @DataField(pos = 0, length = 5)
> String foo;
> @DataField(pos = 5, length = 5)
> String bar;
> }
> }
> {code}



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

[jira] [Commented] (CAMEL-9476) camel-bindy doesn't pad fixed length records

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9476:


Yeah Luca that sounds good. Contributions is welcome

> camel-bindy doesn't pad fixed length records
> 
>
> Key: CAMEL-9476
> URL: https://issues.apache.org/jira/browse/CAMEL-9476
> Project: Camel
>  Issue Type: Bug
>  Components: camel-bindy
>Affects Versions: 2.16.1
>Reporter: Jostein Gogstad
>Priority: Minor
>
> Reading CAMEL-6039 one gets the impression that camel-bindy will pad fixed 
> length records if the input record is smaller than the fixed length.
> https://camel.apache.org/bindy.html:
> {quote}
> When the size of the data does not fill completely the length of the field, 
> we can then add 'padd' characters.
> {quote}
> This is not the case as the following test demonstrates. It fails with
> {code:none}
> java.lang.IllegalArgumentException: Size of the record: 5 is not equal to the 
> value provided in the model: 10
>   at 
> org.apache.camel.dataformat.bindy.fixed.BindyFixedLengthDataFormat.createModel(BindyFixedLengthDataFormat.java:248)
>   at 
> org.apache.camel.dataformat.bindy.fixed.BindyFixedLengthDataFormat.unmarshal(BindyFixedLengthDataFormat.java:209)
>   at 
> org.apache.camel.processor.UnmarshalProcessor.process(UnmarshalProcessor.java:69)
> {code}
> {code:java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.dataformat.bindy.annotation.DataField;
> import org.apache.camel.dataformat.bindy.annotation.FixedLengthRecord;
> import org.apache.camel.model.dataformat.BindyType;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> public class BindyTest extends CamelTestSupport {
> public static final String URI_DIRECT_UNMARSHAL = "direct:unmarshall";
> public static final String URI_MOCK_UNMARSHAL_RESULT = 
> "mock:unmarshal_result";
> @EndpointInject(uri = URI_MOCK_UNMARSHAL_RESULT)
> private MockEndpoint unmarhsalResult;
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from(URI_DIRECT_UNMARSHAL)
> .unmarshal().bindy(BindyType.Fixed, MyBindyModel.class)
> .to(URI_MOCK_UNMARSHAL_RESULT);
> }
> };
> }
> @Test
> public void testUnmarshal() throws Exception {
> unmarhsalResult.expectedMessageCount(1);
> template.sendBody(URI_DIRECT_UNMARSHAL, "foo  \r\n");
> unmarhsalResult.assertIsSatisfied();
> MyBindyModel myBindyModel = 
> unmarhsalResult.getReceivedExchanges().get(0).getIn().getBody(MyBindyModel.class);
> assertEquals("foo  ", myBindyModel.foo);
> }
> @FixedLengthRecord(length = 10)
> public class MyBindyModel {
> @DataField(pos = 0, length = 5)
> String foo;
> @DataField(pos = 5, length = 5)
> String bar;
> }
> }
> {code}



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

[jira] [Resolved] (CAMEL-9463) Camel-guice OSGi dependency resolution fails

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9463.

   Resolution: Workaround
 Assignee: Claus Ibsen
Fix Version/s: 2.18.0

Using Guice 3.x on OSGi that works.

> Camel-guice OSGi dependency resolution fails
> 
>
> Key: CAMEL-9463
> URL: https://issues.apache.org/jira/browse/CAMEL-9463
> Project: Camel
>  Issue Type: Bug
>  Components: camel-guice
>Affects Versions: 2.16.1
> Environment: Karaf 3.0.5 / 4.0.3
>Reporter: Frédérik ROULEAU
>Assignee: Claus Ibsen
>Priority: Minor
>  Labels: karaf, osgi
> Fix For: 2.18.0
>
>
> Camel-guice feature file says it requires com.google.inject/guice/4.0. That 
> bundle do not export com.google.inject.internal.* classes that are required 
> by camel-guice bundle. This leads to the error:
> Unsatisfied requirement(s):
> ---
>
> package:(&(package=com.google.inject.internal)(version>=1.2.0)(!(version>=4.0.0)))
> In version 2.15, camel-guice feature was installing guice from service-mix 
> bundle which was exporting the com.google.inject.internal package.
> It seems that there is no equivalent  ServiceMix  version for guice-4



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Catalina-Alina Dobrica (JIRA)]

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

Catalina-Alina Dobrica commented on CAMEL-9916:
---

Although this would solve a single-context use-case, it's not the full solution 
for me. My original use-case is one where multiple contexts share the same 
registry which won't be fixed by keeping custom added components because when 
one of the contexts stops, the pool on the component is closed and the other 
contexts can no longer get a connection (java.lang.IllegalStateException: Pool 
not open)

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Commented] (CAMEL-9643) CXF SOAP consumer fails when running in Karaf

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9643:


Have you tried with Camel 2.17.x ?

> CXF SOAP consumer fails when running in Karaf
> -
>
> Key: CAMEL-9643
> URL: https://issues.apache.org/jira/browse/CAMEL-9643
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxf, karaf
>Affects Versions: 2.16.2
> Environment: Windows 10 Pro.  Java 1.8.  Karaf 4.0.4.  CXF 3.1.4
>Reporter: John Yin
> Attachments: TestCxfWs-submit.zip
>
>
> A simple Camel CXF SOAP web services consumer (server) works fine in 
> standalone mode.  But when deploying it in Karaf, it would fail if Camel 
> 2.16.x is used.  It would work fine if 2.15.x is used.  streamCache is set to 
> true.  The following error was received.  A zip file is attached containing a 
> maven project (along with Karaf config info) that can reproduce this issue.  
> This is critical because we cannot move to 2.16.x until this issue is 
> resolved.
> javax.xml.transform.TransformerException: Can't transform a Source of type 
> javax.xml.transform.stax.StAXSource 
> at 
> org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:419)
>  
> at 
> org.apache.camel.converter.jaxp.XmlConverter.toResult(XmlConverter.java:132) 
> at 
> org.apache.camel.converter.jaxp.XmlConverter.toResult(XmlConverter.java:116) 
> at 
> org.apache.camel.component.cxf.converter.CachedCxfPayload.(CachedCxfPayload.java:75)
>  
> at 
> org.apache.camel.component.cxf.converter.CxfPayloadConverter.cxfPayLoadToStreamCache(CxfPayloadConverter.java:118)
>  
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)[:1.8.0_60] 
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_60]
>  
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_60]
>  
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_60] 
> at 
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1243)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:293)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.convertTo(BaseTypeConverterRegistry.java:120)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.core.osgi.OsgiTypeConverter.convertTo(OsgiTypeConverter.java:117)[171:org.apache.camel.camel-spring:2.16.2]
>  
> at 
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:72)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:47)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.impl.DefaultStreamCachingStrategy.cache(DefaultStreamCachingStrategy.java:189)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.processor.CamelInternalProcessor$StreamCachingAdvice.before(CamelInternalProcessor.java:765)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.processor.CamelInternalProcessor$StreamCachingAdvice.before(CamelInternalProcessor.java:744)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:138)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.processor.Pipeline.process(Pipeline.java:121)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.processor.Pipeline.process(Pipeline.java:83)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)[164:org.apache.camel.camel-core:2.16.2]
>  
> at 
> org.apache.camel.component.cxf.CxfConsumer$1.asyncInvoke(CxfConsumer.java:95)[165:org.apache.camel.camel-cxf:2.16.2]
>  
> at 
> org.apache.camel.component.cxf.CxfConsumer$1.invoke(CxfConsumer.java:75)[165:org.apache.camel.camel-cxf:2.16.2]
>  
> at 
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)[63:org.apache.cxf.cxf-core:3.1.4]
>  
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_60]
>  
> at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60] 
> at 
> 

[jira] [Updated] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-6132:
---
Fix Version/s: (was: Future)
   2.18.0

> camel-test-karaf - To allow end users more easily do Camel and Karaf 
> integration test
> -
>
> Key: CAMEL-6132
> URL: https://issues.apache.org/jira/browse/CAMEL-6132
> Project: Camel
>  Issue Type: New Feature
>  Components: karaf
>Reporter: Claus Ibsen
>Assignee: Quinn Stevenson
> Fix For: 2.18.0
>
>
> We should introduce a proper camel-test-karaf component that *end users* can 
> use to do Camel and Karaf integration tests.
> The code we have in tests/camel-itest-karaf is for internal usage and testing 
> of Camel. The code is not polished and intended for end users.
> We should create a new module for that, and take the good parts of 
> camel-itest-karaf and make it user friendly etc. And of course have docs to 
> go with as well.
> And when its good, we can use that in camel-itest-karaf also (eat our own dog 
> food)



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

[jira] [Commented] (CAMEL-9802) Camel examples - Make them standalone and import Camel BOM

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9802:


Greg how is it going?

> Camel examples - Make them standalone and import Camel BOM
> --
>
> Key: CAMEL-9802
> URL: https://issues.apache.org/jira/browse/CAMEL-9802
> Project: Camel
>  Issue Type: Improvement
>  Components: examples
>Reporter: Claus Ibsen
>Assignee: Greg A.
>  Labels: maven
> Fix For: Future
>
>
> We should make the Camel examples not use a parent, but use Camel BOM 
> instead, to make them standalone.



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

[jira] [Commented] (CAMEL-9854) CXF Stream Cache contains duplicate namespace definition

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9854:


Aki did you commit this and can this ticket be closed? And set the fix versions.

> CXF Stream Cache contains duplicate namespace definition
> 
>
> Key: CAMEL-9854
> URL: https://issues.apache.org/jira/browse/CAMEL-9854
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.16.3
>Reporter: Stephan Siano
>Assignee: Akitoshi Yoshida
>Priority: Minor
> Attachments: 
> 0001-CAMEL-9854-CXF-Stream-Cache-contains-duplicate-names.patch
>
>
> If stream caching is enabled for incoming messages in Camel-CXF and a 
> namespace defined on the SOAP envelope is also defined on the root tag of the 
> payload document the XML contained within the stream cache contains a 
> duplicate namespace definition.
> See attached unit test for details



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

[jira] [Resolved] (CAMEL-9836) Add file id of the gridfs file created in the header of the exchange

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9836.

Resolution: Fixed
  Assignee: Claus Ibsen

Thanks for the PR

> Add file id of the gridfs file created in the header of the exchange
> 
>
> Key: CAMEL-9836
> URL: https://issues.apache.org/jira/browse/CAMEL-9836
> Project: Camel
>  Issue Type: Wish
>  Components: camel-mongodb
>Affects Versions: 2.17.0
> Environment: Any
>Reporter: Jose Luis Pedrosa
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.17.1, 2.18.0
>
>
> Currently the camel-mongodb-gridfs component (which is not available in this 
> Jira) when a file is cretated does not return back the Id (_id) of the file 
> created, it only returns  the filename
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> {code}
> mongodb api has the method getid: 
> http://api.mongodb.org/java/current/com/mongodb/gridfs/GridFSFile.html#getId--
> So i'd like to ask to:
> a) create a header field (maybe GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED)
> b) Add the header after the creation
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> 
> exchange.getIn().setHeader(GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED, 
> gfsFile.getId());
> {code}
> Of course I can create a PR myself, but I think the administrative work would 
> be more? Up to you guys.



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Catalina-Alina Dobrica (JIRA)]

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

Catalina-Alina Dobrica commented on CAMEL-9916:
---

Yes, precisely. This is also an issue when multiple context are created with 
the same registry => when one of the contexts stops, the pool on the component 
is closed and the other contexts can no longer get a connection 
(java.lang.IllegalStateException: Pool not open)

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Updated] (CAMEL-9836) Add file id of the gridfs file created in the header of the exchange

[Jose Luis Pedrosa (JIRA)]

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

Jose Luis Pedrosa updated CAMEL-9836:
-
Fix Version/s: (was: 2.17.2)
   2.17.1

> Add file id of the gridfs file created in the header of the exchange
> 
>
> Key: CAMEL-9836
> URL: https://issues.apache.org/jira/browse/CAMEL-9836
> Project: Camel
>  Issue Type: Wish
>  Components: camel-mongodb
>Affects Versions: 2.17.0
> Environment: Any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.1, 2.18.0
>
>
> Currently the camel-mongodb-gridfs component (which is not available in this 
> Jira) when a file is cretated does not return back the Id (_id) of the file 
> created, it only returns  the filename
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> {code}
> mongodb api has the method getid: 
> http://api.mongodb.org/java/current/com/mongodb/gridfs/GridFSFile.html#getId--
> So i'd like to ask to:
> a) create a header field (maybe GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED)
> b) Add the header after the creation
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> 
> exchange.getIn().setHeader(GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED, 
> gfsFile.getId());
> {code}
> Of course I can create a PR myself, but I think the administrative work would 
> be more? Up to you guys.



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

[jira] [Commented] (CAMEL-9836) Add file id of the gridfs file created in the header of the exchange

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-9836:
---

GitHub user jlpedrosa opened a pull request:

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

Add the _id of the file just persisted to the context

Hi,

this PR relates to: https://issues.apache.org/jira/browse/CAMEL-9836

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

$ git pull https://github.com/jlpedrosa/camel master

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

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


commit 999495ac9aae0abaa82892bf147a8be406960f8f
Author: Joseluis Pedrosa 
Date:   2016-04-28T10:41:45Z

Add the _id of the file just persisted to the context




> Add file id of the gridfs file created in the header of the exchange
> 
>
> Key: CAMEL-9836
> URL: https://issues.apache.org/jira/browse/CAMEL-9836
> Project: Camel
>  Issue Type: Wish
>  Components: camel-mongodb
>Affects Versions: 2.17.0
> Environment: Any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>
> Currently the camel-mongodb-gridfs component (which is not available in this 
> Jira) when a file is cretated does not return back the Id (_id) of the file 
> created, it only returns  the filename
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> {code}
> mongodb api has the method getid: 
> http://api.mongodb.org/java/current/com/mongodb/gridfs/GridFSFile.html#getId--
> So i'd like to ask to:
> a) create a header field (maybe GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED)
> b) Add the header after the creation
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> 
> exchange.getIn().setHeader(GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED, 
> gfsFile.getId());
> {code}
> Of course I can create a PR myself, but I think the administrative work would 
> be more? Up to you guys.



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

[jira] [Commented] (CAMEL-9836) Add file id of the gridfs file created in the header of the exchange

[Jose Luis Pedrosa (JIRA)]

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

Jose Luis Pedrosa commented on CAMEL-9836:
--

Hi Claus,

Thanks, there you have: https://github.com/apache/camel/pull/967


> Add file id of the gridfs file created in the header of the exchange
> 
>
> Key: CAMEL-9836
> URL: https://issues.apache.org/jira/browse/CAMEL-9836
> Project: Camel
>  Issue Type: Wish
>  Components: camel-mongodb
>Affects Versions: 2.17.0
> Environment: Any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>
> Currently the camel-mongodb-gridfs component (which is not available in this 
> Jira) when a file is cretated does not return back the Id (_id) of the file 
> created, it only returns  the filename
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> {code}
> mongodb api has the method getid: 
> http://api.mongodb.org/java/current/com/mongodb/gridfs/GridFSFile.html#getId--
> So i'd like to ask to:
> a) create a header field (maybe GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED)
> b) Add the header after the creation
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> 
> exchange.getIn().setHeader(GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED, 
> gfsFile.getId());
> {code}
> Of course I can create a PR myself, but I think the administrative work would 
> be more? Up to you guys.



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

[jira] [Commented] (CAMEL-9790) camel-kafka 2.17 not throwing TimeoutException back which is throw by Kafka client

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9790:


Andrea if you are able to work on it then that is fine too. The import piece is 
that the issue gets resolved.

> camel-kafka 2.17 not throwing TimeoutException back which is throw by Kafka 
> client 
> ---
>
> Key: CAMEL-9790
> URL: https://issues.apache.org/jira/browse/CAMEL-9790
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-kafka
>Reporter: Deelipkumar Daresh
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>
> if  org.apache.kafka.clients.producer.KafkaProducer.waitOnMetadata  throwing 
> org.apache.kafka.common.errors.TimeoutException exception  then it catching 
> warping  up in FutureFailure(e)
> passing to camel KafkaProducer but camel KafkaProuder is not doing anything 
> with that.
> it will be good if camel KafkaProducer  throws it so, we can set for retry 
> it. 
> http://camel.465427.n5.nabble.com/camel-kafka-2-17-not-throwing-TimeoutException-back-which-is-throw-by-Kafka-client-td5780199.html#a5780249



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

[jira] [Commented] (CAMEL-9922) activemq broker cannot start

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9922:


Its the activemq-osig bundle that has problems. There is another AMQ ticket 
about this.

> activemq broker cannot start
> 
>
> Key: CAMEL-9922
> URL: https://issues.apache.org/jira/browse/CAMEL-9922
> Project: Camel
>  Issue Type: Bug
>  Components: camel-activemq
>Affects Versions: 2.17.0
> Environment: karaf
>Reporter: Alexandre Cartapanis
>
> On karaf 4.x plateform, with camel 2.17.0 and activemq 5.13.2 features, 
> installs feature activemq-camel and then installs activemq-broker-noweb. The 
> broker fails to start with error java.lang.ClassNotFoundException: 
> org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by 
> org.apache.activemq.activemq-osgi.
> This is not happening with camel 2.16.3
> This is not happening either if activemq-camel is not installed.



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

[jira] [Reopened] (CAMEL-9921) Dozer variable mapping doesn't work on karaf

[Claus Ibsen (JIRA)]

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

Claus Ibsen reopened CAMEL-9921:


Tomohisa, will work on an unit test we can include in camel-dozer as test. And 
then a smaller example (separated from fuseide) that we can use to track down 
the osgi issue.

Mind that dozer is not OSGi friendly so it may be that this functionailty is 
not supported/working on OSGi.

> Dozer variable mapping doesn't work on karaf
> 
>
> Key: CAMEL-9921
> URL: https://issues.apache.org/jira/browse/CAMEL-9921
> Project: Camel
>  Issue Type: Bug
>  Components: camel-dozer
>Affects Versions: 2.15.6, 2.17.0
>Reporter: Tomohisa Igarashi
>Assignee: Claus Ibsen
>Priority: Minor
>
> The configuration variables defined in transformation.xml is not resolved to 
> the value on karaf. It just works in unit test and JBoss EAP via SwitchYard. 
> I also tried to run with camel-2.18-SNAPSHOT, but it requires 
> (&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))
>  while karaf-2.4.4 bundles felix gogo 0.12.1.
> h4. Steps to reproduce
> # Checkout xml-to-json example from here - 
> https://github.com/fusesource/fuseide/tree/master/examples/transformation/xml-to-json
> # Change camel version to 2.17.0 in its pom.xml
> # Run mvn install
> # Start a karaf instance
> # Add URLs
> {code}
> karaf@root> features:addurl 
> mvn:org.apache.camel.karaf/apache-camel/2.17.0/xml/features
> karaf@root> features:addurl 
> mvn:org.jboss.tools.fuse.examples.transformation/xml-to-json/1.0.0-SNAPSHOT/xml/features
> {code}
> # Install the application
> {code}
> karaf@root> features:install xml-to-json
> {code}
> # Copy input file
> {code}
> # cp src/data/abc-order.xml /tmp/inbox/
> {code}
> # Check the output file '/tmp/outbox/xyz-order.json'. You would see  
> "origin":"$\{ORIGIN}" while $\{ORIGIN} should have been resolved to 'Web'.



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9916:


I logged a ticket about keeping the custom added components: CAMEL-9924

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Updated] (CAMEL-9822) Upgrade to DeltaSpike 1.6.1

[Antonin Stefanutti (JIRA)]

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

Antonin Stefanutti updated CAMEL-9822:
--
Summary: Upgrade to DeltaSpike 1.6.1  (was: Upgrade to deltaspike 1.6.1)

> Upgrade to DeltaSpike 1.6.1
> ---
>
> Key: CAMEL-9822
> URL: https://issues.apache.org/jira/browse/CAMEL-9822
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cdi
>Reporter: Claus Ibsen
>Assignee: Antonin Stefanutti
> Fix For: 2.18.0
>
>
> Wonder if we should upgrade to 1.6 for the upcoming Camel 2.18 release.



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

[jira] [Created] (CAMEL-9924) Consider keeping custom add components in camelcontext when stopped so people can start again

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-9924:
--

 Summary: Consider keeping custom add components in camelcontext 
when stopped so people can start again
 Key: CAMEL-9924
 URL: https://issues.apache.org/jira/browse/CAMEL-9924
 Project: Camel
  Issue Type: Improvement
  Components: camel-core
Reporter: Claus Ibsen


See CAMEL-9916

If people restart manually using stop/start then Camel does not guarantee it 
can startup again. The stop is for a hard shutdown. Ideally you should use 
suspend/resume. Or if in some app server then restart there, eg where its a 
full restart of the deployed unit.

But we could consider keeping custom added components in stop so when you call 
start again they are still there.

For components that has been default created then Camel can create them again.



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

[jira] [Resolved] (CAMEL-9822) Upgrade to DeltaSpike 1.6.1

[Antonin Stefanutti (JIRA)]

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

Antonin Stefanutti resolved CAMEL-9822.
---
Resolution: Fixed

> Upgrade to DeltaSpike 1.6.1
> ---
>
> Key: CAMEL-9822
> URL: https://issues.apache.org/jira/browse/CAMEL-9822
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cdi
>Reporter: Claus Ibsen
>Assignee: Antonin Stefanutti
> Fix For: 2.18.0
>
>
> Wonder if we should upgrade to 1.6 for the upcoming Camel 2.18 release.



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

[jira] [Updated] (CAMEL-9822) Upgrade to deltaspike 1.6.1

[Antonin Stefanutti (JIRA)]

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

Antonin Stefanutti updated CAMEL-9822:
--
Summary: Upgrade to deltaspike 1.6.1  (was: Upgrade to deltaspike 1.6)

> Upgrade to deltaspike 1.6.1
> ---
>
> Key: CAMEL-9822
> URL: https://issues.apache.org/jira/browse/CAMEL-9822
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cdi
>Reporter: Claus Ibsen
>Assignee: Antonin Stefanutti
> Fix For: 2.18.0
>
>
> Wonder if we should upgrade to 1.6 for the upcoming Camel 2.18 release.



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9916:


Ah okay so when you restart then the custom component you added manually has 
been cleared, and therefore you need to add it back again.

{code}
// restart
context.stop();

// must add our custom component back again
context.addComponent("sjms", sjmsComponent);

context.start();
{code}


> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Commented] (CAMEL-9921) Dozer variable mapping doesn't work on karaf

[Tomohisa Igarashi (JIRA)]

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

Tomohisa Igarashi commented on CAMEL-9921:
--

camel-2.17.0, karaf-4.0.5 and the xml-to-json example are all opensource. And 
it doesn't reproduce in unit test.

> Dozer variable mapping doesn't work on karaf
> 
>
> Key: CAMEL-9921
> URL: https://issues.apache.org/jira/browse/CAMEL-9921
> Project: Camel
>  Issue Type: Bug
>  Components: camel-dozer
>Affects Versions: 2.15.6, 2.17.0
>Reporter: Tomohisa Igarashi
>Assignee: Claus Ibsen
>Priority: Minor
>
> The configuration variables defined in transformation.xml is not resolved to 
> the value on karaf. It just works in unit test and JBoss EAP via SwitchYard. 
> I also tried to run with camel-2.18-SNAPSHOT, but it requires 
> (&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))
>  while karaf-2.4.4 bundles felix gogo 0.12.1.
> h4. Steps to reproduce
> # Checkout xml-to-json example from here - 
> https://github.com/fusesource/fuseide/tree/master/examples/transformation/xml-to-json
> # Change camel version to 2.17.0 in its pom.xml
> # Run mvn install
> # Start a karaf instance
> # Add URLs
> {code}
> karaf@root> features:addurl 
> mvn:org.apache.camel.karaf/apache-camel/2.17.0/xml/features
> karaf@root> features:addurl 
> mvn:org.jboss.tools.fuse.examples.transformation/xml-to-json/1.0.0-SNAPSHOT/xml/features
> {code}
> # Install the application
> {code}
> karaf@root> features:install xml-to-json
> {code}
> # Copy input file
> {code}
> # cp src/data/abc-order.xml /tmp/inbox/
> {code}
> # Check the output file '/tmp/outbox/xyz-order.json'. You would see  
> "origin":"$\{ORIGIN}" while $\{ORIGIN} should have been resolved to 'Web'.



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

[jira] [Commented] (CAMEL-9923) camel-blueprint - Should not use online xsd for parsing

[Grzegorz Grzybek (JIRA)]

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

Grzegorz Grzybek commented on CAMEL-9923:
-

[~davsclaus] we should either stay with blueprint-core:1.4.4 or upgrade to 
1.6.1 (see ARIES-1503)

> camel-blueprint - Should not use online xsd for parsing
> ---
>
> Key: CAMEL-9923
> URL: https://issues.apache.org/jira/browse/CAMEL-9923
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-blueprint
>Affects Versions: 2.18.0
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
> Fix For: Future
>
>
> The parser should resolve the xsd from the camel-blueprint JAR bundle instead 
> of online access.
> You can see WARNs like these on Camel 2.17.0 installation on karaf 4.0.4
> {code}
> 2016-04-28 11:38:40,935 | ERROR | FelixStartLevel  | BlueprintContainerImpl   
> | 13 - org.apache.aries.blueprint.core - 1.5.0 | Unable to start 
> blueprint container for bundle mycamel.xml/0.0.0
> org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
> validate xml
>   at 
> org.apache.aries.blueprint.parser.Parser.validate(Parser.java:349)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.parser.Parser.validate(Parser.java:336)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:336)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:273)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:294)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:263)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:253)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[22:org.apache.aries.util:1.1.1]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[22:org.apache.aries.util:1.1.1]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[22:org.apache.aries.util:1.1.1]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[22:org.apache.aries.util:1.1.1]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[22:org.apache.aries.util:1.1.1]
>   at 
> org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:731)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:486)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4541)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.Felix.startBundle(Felix.java:2172)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)[org.apache.felix.framework-5.4.0.jar:]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]
> Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid 
> content was found starting with element 'hystrix'. One of 
> '{"http://camel.apache.org/schema/blueprint":from, 
> "http://camel.apache.org/schema/blueprint":onException, 
> "http://camel.apache.org/schema/blueprint":when, 
> "http://camel.apache.org/schema/blueprint":onCompletion, 
> "http://camel.apache.org/schema/blueprint":intercept, 
> "http://camel.apache.org/schema/blueprint":interceptFrom, 
> "http://camel.apache.org/schema/blueprint":interceptSendToEndpoint, 
> "http://camel.apache.org/schema/blueprint":to, 
> "http://camel.apache.org/schema/blueprint":toD, 
> "http://camel.apache.org/schema/blueprint":route, 
> "http://camel.apache.org/schema/blueprint":aop, 
> "http://camel.apache.org/schema/blueprint":aggregate, 
> "http://camel.apache.org/schema/blueprint":bean, 
> 

[jira] [Resolved] (CAMEL-9923) camel-blueprint - Should not use online xsd for parsing

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9923.

Resolution: Not A Problem

Doh it was a dodgy mycamel.xml leftover in the deploy folder that was testing 
hystrix from Camel 2.18. 

Darn you karaf, I want a clean way to "reset" you ;)

> camel-blueprint - Should not use online xsd for parsing
> ---
>
> Key: CAMEL-9923
> URL: https://issues.apache.org/jira/browse/CAMEL-9923
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-blueprint
>Affects Versions: 2.18.0
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
> Fix For: Future
>
>
> The parser should resolve the xsd from the camel-blueprint JAR bundle instead 
> of online access.
> You can see WARNs like these on Camel 2.17.0 installation on karaf 4.0.4
> {code}
> 2016-04-28 11:38:40,935 | ERROR | FelixStartLevel  | BlueprintContainerImpl   
> | 13 - org.apache.aries.blueprint.core - 1.5.0 | Unable to start 
> blueprint container for bundle mycamel.xml/0.0.0
> org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
> validate xml
>   at 
> org.apache.aries.blueprint.parser.Parser.validate(Parser.java:349)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.parser.Parser.validate(Parser.java:336)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:336)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:273)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:294)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:263)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:253)[13:org.apache.aries.blueprint.core:1.5.0]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[22:org.apache.aries.util:1.1.1]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[22:org.apache.aries.util:1.1.1]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[22:org.apache.aries.util:1.1.1]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[22:org.apache.aries.util:1.1.1]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[22:org.apache.aries.util:1.1.1]
>   at 
> org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:731)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:486)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4541)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.Felix.startBundle(Felix.java:2172)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)[org.apache.felix.framework-5.4.0.jar:]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]
> Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid 
> content was found starting with element 'hystrix'. One of 
> '{"http://camel.apache.org/schema/blueprint":from, 
> "http://camel.apache.org/schema/blueprint":onException, 
> "http://camel.apache.org/schema/blueprint":when, 
> "http://camel.apache.org/schema/blueprint":onCompletion, 
> "http://camel.apache.org/schema/blueprint":intercept, 
> "http://camel.apache.org/schema/blueprint":interceptFrom, 
> "http://camel.apache.org/schema/blueprint":interceptSendToEndpoint, 
> "http://camel.apache.org/schema/blueprint":to, 
> "http://camel.apache.org/schema/blueprint":toD, 
> "http://camel.apache.org/schema/blueprint":route, 
> "http://camel.apache.org/schema/blueprint":aop, 
> "http://camel.apache.org/schema/blueprint":aggregate, 
> 

[jira] [Created] (CAMEL-9923) camel-blueprint - Should not use online xsd for parsing

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-9923:
--

 Summary: camel-blueprint - Should not use online xsd for parsing
 Key: CAMEL-9923
 URL: https://issues.apache.org/jira/browse/CAMEL-9923
 Project: Camel
  Issue Type: Improvement
  Components: camel-blueprint
Affects Versions: 2.18.0
Reporter: Claus Ibsen
Assignee: Grzegorz Grzybek
 Fix For: Future


The parser should resolve the xsd from the camel-blueprint JAR bundle instead 
of online access.

You can see WARNs like these on Camel 2.17.0 installation on karaf 4.0.4
{code}
2016-04-28 11:38:40,935 | ERROR | FelixStartLevel  | BlueprintContainerImpl 
  | 13 - org.apache.aries.blueprint.core - 1.5.0 | Unable to start 
blueprint container for bundle mycamel.xml/0.0.0
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
validate xml
at 
org.apache.aries.blueprint.parser.Parser.validate(Parser.java:349)[13:org.apache.aries.blueprint.core:1.5.0]
at 
org.apache.aries.blueprint.parser.Parser.validate(Parser.java:336)[13:org.apache.aries.blueprint.core:1.5.0]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:336)[13:org.apache.aries.blueprint.core:1.5.0]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:273)[13:org.apache.aries.blueprint.core:1.5.0]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:294)[13:org.apache.aries.blueprint.core:1.5.0]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:263)[13:org.apache.aries.blueprint.core:1.5.0]
at 
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:253)[13:org.apache.aries.blueprint.core:1.5.0]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[22:org.apache.aries.util:1.1.1]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[22:org.apache.aries.util:1.1.1]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[22:org.apache.aries.util:1.1.1]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[22:org.apache.aries.util:1.1.1]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[22:org.apache.aries.util:1.1.1]
at 
org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:731)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:486)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4541)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.Felix.startBundle(Felix.java:2172)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)[org.apache.felix.framework-5.4.0.jar:]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'hystrix'. One of 
'{"http://camel.apache.org/schema/blueprint":from, 
"http://camel.apache.org/schema/blueprint":onException, 
"http://camel.apache.org/schema/blueprint":when, 
"http://camel.apache.org/schema/blueprint":onCompletion, 
"http://camel.apache.org/schema/blueprint":intercept, 
"http://camel.apache.org/schema/blueprint":interceptFrom, 
"http://camel.apache.org/schema/blueprint":interceptSendToEndpoint, 
"http://camel.apache.org/schema/blueprint":to, 
"http://camel.apache.org/schema/blueprint":toD, 
"http://camel.apache.org/schema/blueprint":route, 
"http://camel.apache.org/schema/blueprint":aop, 
"http://camel.apache.org/schema/blueprint":aggregate, 
"http://camel.apache.org/schema/blueprint":bean, 
"http://camel.apache.org/schema/blueprint":doCatch, 
"http://camel.apache.org/schema/blueprint":choice, 
"http://camel.apache.org/schema/blueprint":otherwise, 
"http://camel.apache.org/schema/blueprint":convertBodyTo, 
"http://camel.apache.org/schema/blueprint":delay, 
"http://camel.apache.org/schema/blueprint":dynamicRouter, 
"http://camel.apache.org/schema/blueprint":enrich, 

[jira] [Commented] (CAMEL-9921) Dozer variable mapping doesn't work on karaf

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9921:


You report a problem with feature install that works fine. Make an unit test 
with current code that tests the variable stuff. Then we can use that to 
reproduce the issue on Apache Camel source code.

> Dozer variable mapping doesn't work on karaf
> 
>
> Key: CAMEL-9921
> URL: https://issues.apache.org/jira/browse/CAMEL-9921
> Project: Camel
>  Issue Type: Bug
>  Components: camel-dozer
>Affects Versions: 2.15.6, 2.17.0
>Reporter: Tomohisa Igarashi
>Assignee: Claus Ibsen
>Priority: Minor
>
> The configuration variables defined in transformation.xml is not resolved to 
> the value on karaf. It just works in unit test and JBoss EAP via SwitchYard. 
> I also tried to run with camel-2.18-SNAPSHOT, but it requires 
> (&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))
>  while karaf-2.4.4 bundles felix gogo 0.12.1.
> h4. Steps to reproduce
> # Checkout xml-to-json example from here - 
> https://github.com/fusesource/fuseide/tree/master/examples/transformation/xml-to-json
> # Change camel version to 2.17.0 in its pom.xml
> # Run mvn install
> # Start a karaf instance
> # Add URLs
> {code}
> karaf@root> features:addurl 
> mvn:org.apache.camel.karaf/apache-camel/2.17.0/xml/features
> karaf@root> features:addurl 
> mvn:org.jboss.tools.fuse.examples.transformation/xml-to-json/1.0.0-SNAPSHOT/xml/features
> {code}
> # Install the application
> {code}
> karaf@root> features:install xml-to-json
> {code}
> # Copy input file
> {code}
> # cp src/data/abc-order.xml /tmp/inbox/
> {code}
> # Check the output file '/tmp/outbox/xyz-order.json'. You would see  
> "origin":"$\{ORIGIN}" while $\{ORIGIN} should have been resolved to 'Web'.



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

[jira] [Commented] (CAMEL-9921) Dozer variable mapping doesn't work on karaf

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9921:


Create a small unit test on current community code that reproduces the issue.
Do not report commercial companies software problems here.

> Dozer variable mapping doesn't work on karaf
> 
>
> Key: CAMEL-9921
> URL: https://issues.apache.org/jira/browse/CAMEL-9921
> Project: Camel
>  Issue Type: Bug
>  Components: camel-dozer
>Affects Versions: 2.15.6, 2.17.0
>Reporter: Tomohisa Igarashi
>Assignee: Claus Ibsen
>Priority: Minor
>
> The configuration variables defined in transformation.xml is not resolved to 
> the value on karaf. It just works in unit test and JBoss EAP via SwitchYard. 
> I also tried to run with camel-2.18-SNAPSHOT, but it requires 
> (&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))
>  while karaf-2.4.4 bundles felix gogo 0.12.1.
> h4. Steps to reproduce
> # Checkout xml-to-json example from here - 
> https://github.com/fusesource/fuseide/tree/master/examples/transformation/xml-to-json
> # Change camel version to 2.17.0 in its pom.xml
> # Run mvn install
> # Start a karaf instance
> # Add URLs
> {code}
> karaf@root> features:addurl 
> mvn:org.apache.camel.karaf/apache-camel/2.17.0/xml/features
> karaf@root> features:addurl 
> mvn:org.jboss.tools.fuse.examples.transformation/xml-to-json/1.0.0-SNAPSHOT/xml/features
> {code}
> # Install the application
> {code}
> karaf@root> features:install xml-to-json
> {code}
> # Copy input file
> {code}
> # cp src/data/abc-order.xml /tmp/inbox/
> {code}
> # Check the output file '/tmp/outbox/xyz-order.json'. You would see  
> "origin":"$\{ORIGIN}" while $\{ORIGIN} should have been resolved to 'Web'.



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Catalina-Alina Dobrica (JIRA)]

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

Catalina-Alina Dobrica commented on CAMEL-9916:
---

I don't set up the connection pool - it is currently handled in SJMS, in the 
component's doStart and doStop methods. What I propose is doing it in the 
endpoint's doStart and doStop, as I suggest the ConnectionFactory should belong 
to the endpoint instead of the component. Keeping, of course, the backward 
compatibility.
Here's a simple use-case of the restart issue (which is not restricted to XML 
usage):
{code}
/**
Using a basic use-case of SJMS component + ActiveMQConnectionFactory, context 
cannot be restarted
**/
@Test
public void useCase() throws Exception {
SimpleRegistry registry = new SimpleRegistry();
ActiveMQConnectionFactory connectionFactory = new 
ActiveMQConnectionFactory("vm://broker?broker.persistent=false=false");
registry.put("activemq", connectionFactory);
DefaultCamelContext context = new DefaultCamelContext(registry);
//adding a connection factory to a SJMS component instance, as per the current 
usage of this component
SjmsComponent sjmsComponent = new SjmsComponent();
sjmsComponent.setConnectionFactory(connectionFactory);
context.addComponent("sjms", sjmsComponent);
//with no added complexity in the route
RouteBuilder routeBuilder = new RouteBuilder(context) {
@Override
public void configure() throws Exception {
from("sjms:queue:test").log("$
{body}
");
}
};
context.addRoutes(routeBuilder);
//when the context starts, SjmsComponent.doStart creates a 
ConnectionFactoryResource with an underlying GenericObjectPool, 
even if the pool size is 1 (default = this use-case) and fills the pool
context.start();
//when the context starts, SjmsComponent.doStop drains the pool
context.stop();
//FAIL - the context cannot start again because of an NPE in SjmsConsumer when 
trying to borrowConnection from the ConnectionFactoryResource
context.start();
context.stop();
}{code}

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Commented] (CAMEL-9922) activemq broker cannot start

[Alexandre Cartapanis (JIRA)]

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

Alexandre Cartapanis commented on CAMEL-9922:
-

https://issues.apache.org/jira/browse/AMQ-6268

> activemq broker cannot start
> 
>
> Key: CAMEL-9922
> URL: https://issues.apache.org/jira/browse/CAMEL-9922
> Project: Camel
>  Issue Type: Bug
>  Components: camel-activemq
>Affects Versions: 2.17.0
> Environment: karaf
>Reporter: Alexandre Cartapanis
>
> On karaf 4.x plateform, with camel 2.17.0 and activemq 5.13.2 features, 
> installs feature activemq-camel and then installs activemq-broker-noweb. The 
> broker fails to start with error java.lang.ClassNotFoundException: 
> org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by 
> org.apache.activemq.activemq-osgi.
> This is not happening with camel 2.16.3
> This is not happening either if activemq-camel is not installed.



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

[jira] [Commented] (CAMEL-9921) Dozer variable mapping doesn't work on karaf

[Tomohisa Igarashi (JIRA)]

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

Tomohisa Igarashi commented on CAMEL-9921:
--

That's weird, did you really see "origin":"Web" in the 
/tmp/outbox/xyz-order.json?

> Dozer variable mapping doesn't work on karaf
> 
>
> Key: CAMEL-9921
> URL: https://issues.apache.org/jira/browse/CAMEL-9921
> Project: Camel
>  Issue Type: Bug
>  Components: camel-dozer
>Affects Versions: 2.15.6, 2.17.0
>Reporter: Tomohisa Igarashi
>Assignee: Claus Ibsen
>Priority: Minor
>
> The configuration variables defined in transformation.xml is not resolved to 
> the value on karaf. It just works in unit test and JBoss EAP via SwitchYard. 
> I also tried to run with camel-2.18-SNAPSHOT, but it requires 
> (&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))
>  while karaf-2.4.4 bundles felix gogo 0.12.1.
> h4. Steps to reproduce
> # Checkout xml-to-json example from here - 
> https://github.com/fusesource/fuseide/tree/master/examples/transformation/xml-to-json
> # Change camel version to 2.17.0 in its pom.xml
> # Run mvn install
> # Start a karaf instance
> # Add URLs
> {code}
> karaf@root> features:addurl 
> mvn:org.apache.camel.karaf/apache-camel/2.17.0/xml/features
> karaf@root> features:addurl 
> mvn:org.jboss.tools.fuse.examples.transformation/xml-to-json/1.0.0-SNAPSHOT/xml/features
> {code}
> # Install the application
> {code}
> karaf@root> features:install xml-to-json
> {code}
> # Copy input file
> {code}
> # cp src/data/abc-order.xml /tmp/inbox/
> {code}
> # Check the output file '/tmp/outbox/xyz-order.json'. You would see  
> "origin":"$\{ORIGIN}" while $\{ORIGIN} should have been resolved to 'Web'.



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9916:


This is not correct way to restart Camel. Doing a stop shutdown Camel and you 
are not guaranteed that it can start again. See the javadoc.
You can suspend/resume a context if you want to not let it do routing anymore.

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Issue Comment Deleted] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Catalina-Alina Dobrica (JIRA)]

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

Catalina-Alina Dobrica updated CAMEL-9916:
--
Comment: was deleted

(was: I don't set up the connection pool - it is currently handled in SJMS, in 
the component's doStart and doStop methods. What I propose is doing it in the 
endpoint's doStart and doStop, as I suggest the ConnectionFactory should belong 
to the endpoint instead of the component. Keeping, of course, the backward 
compatibility.
Here's a simple use-case of the restart issue (which is not restricted to XML 
usage):
/**
 * Using a basic use-case of SJMS component + ActiveMQConnectionFactory, 
context cannot be restarted
 **/
@Test
public void useCase() throws Exception {
SimpleRegistry registry = new SimpleRegistry();
ActiveMQConnectionFactory connectionFactory = new 
ActiveMQConnectionFactory("vm://broker?broker.persistent=false=false");
registry.put("activemq", connectionFactory);

DefaultCamelContext context = new DefaultCamelContext(registry);
//adding a connection factory to a SJMS component instance, as per the 
current usage of this component
SjmsComponent sjmsComponent = new SjmsComponent();
sjmsComponent.setConnectionFactory(connectionFactory);
context.addComponent("sjms", sjmsComponent);

//with no added complexity in the route
RouteBuilder routeBuilder = new RouteBuilder(context) {
@Override
public void configure() throws Exception {
from("sjms:queue:test").log("${body}");
}
};
context.addRoutes(routeBuilder);

//when the context starts, SjmsComponent.doStart creates a 
ConnectionFactoryResource with an underlying GenericObjectPool, 
even if the pool size is 1 (default = this use-case) and fills the pool
context.start();
//when the context starts, SjmsComponent.doStop drains the pool
context.stop();
//FAIL - the context cannot start again because of an NPE in 
SjmsConsumer when trying to borrowConnection from the ConnectionFactoryResource
context.start();
context.stop();
})

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Catalina-Alina Dobrica (JIRA)]

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

Catalina-Alina Dobrica commented on CAMEL-9916:
---

I don't set up the connection pool - it is currently handled in SJMS, in the 
component's doStart and doStop methods. What I propose is doing it in the 
endpoint's doStart and doStop, as I suggest the ConnectionFactory should belong 
to the endpoint instead of the component. Keeping, of course, the backward 
compatibility.
Here's a simple use-case of the restart issue (which is not restricted to XML 
usage):
/**
 * Using a basic use-case of SJMS component + ActiveMQConnectionFactory, 
context cannot be restarted
 **/
@Test
public void useCase() throws Exception {
SimpleRegistry registry = new SimpleRegistry();
ActiveMQConnectionFactory connectionFactory = new 
ActiveMQConnectionFactory("vm://broker?broker.persistent=false=false");
registry.put("activemq", connectionFactory);

DefaultCamelContext context = new DefaultCamelContext(registry);
//adding a connection factory to a SJMS component instance, as per the 
current usage of this component
SjmsComponent sjmsComponent = new SjmsComponent();
sjmsComponent.setConnectionFactory(connectionFactory);
context.addComponent("sjms", sjmsComponent);

//with no added complexity in the route
RouteBuilder routeBuilder = new RouteBuilder(context) {
@Override
public void configure() throws Exception {
from("sjms:queue:test").log("${body}");
}
};
context.addRoutes(routeBuilder);

//when the context starts, SjmsComponent.doStart creates a 
ConnectionFactoryResource with an underlying GenericObjectPool, 
even if the pool size is 1 (default = this use-case) and fills the pool
context.start();
//when the context starts, SjmsComponent.doStop drains the pool
context.stop();
//FAIL - the context cannot start again because of an NPE in 
SjmsConsumer when trying to borrowConnection from the ConnectionFactoryResource
context.start();
context.stop();
}

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Commented] (CAMEL-9921) Dozer variable mapping doesn't work on karaf

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9921:


Works fine with karaf 4.0.4 and camel 2.17.0
{code}
karaf@root()> camel:route-list
 ContextRoute  Status  Total #   Failed # 
Inflight #   Uptime
 ----  --  ---    
--   --
 camel-1route1 Started   0  0   
   0   51.470 seconds
karaf@root()> camel:route-show route1

http://camel.apache.org/schema/spring;>


AUTO




{code}

karaf@root()> info
Karaf
  Karaf version   4.0.4

> Dozer variable mapping doesn't work on karaf
> 
>
> Key: CAMEL-9921
> URL: https://issues.apache.org/jira/browse/CAMEL-9921
> Project: Camel
>  Issue Type: Bug
>  Components: camel-dozer
>Affects Versions: 2.15.6, 2.17.0
>Reporter: Tomohisa Igarashi
>Priority: Minor
>
> The configuration variables defined in transformation.xml is not resolved to 
> the value on karaf. It just works in unit test and JBoss EAP via SwitchYard. 
> I also tried to run with camel-2.18-SNAPSHOT, but it requires 
> (&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))
>  while karaf-2.4.4 bundles felix gogo 0.12.1.
> h4. Steps to reproduce
> # Checkout xml-to-json example from here - 
> https://github.com/fusesource/fuseide/tree/master/examples/transformation/xml-to-json
> # Change camel version to 2.17.0 in its pom.xml
> # Run mvn install
> # Start a karaf instance
> # Add URLs
> {code}
> karaf@root> features:addurl 
> mvn:org.apache.camel.karaf/apache-camel/2.17.0/xml/features
> karaf@root> features:addurl 
> mvn:org.jboss.tools.fuse.examples.transformation/xml-to-json/1.0.0-SNAPSHOT/xml/features
> {code}
> # Install the application
> {code}
> karaf@root> features:install xml-to-json
> {code}
> # Copy input file
> {code}
> # cp src/data/abc-order.xml /tmp/inbox/
> {code}
> # Check the output file '/tmp/outbox/xyz-order.json'. You would see  
> "origin":"$\{ORIGIN}" while $\{ORIGIN} should have been resolved to 'Web'.



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

[jira] [Resolved] (CAMEL-9921) Dozer variable mapping doesn't work on karaf

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9921.

Resolution: Cannot Reproduce
  Assignee: Claus Ibsen

> Dozer variable mapping doesn't work on karaf
> 
>
> Key: CAMEL-9921
> URL: https://issues.apache.org/jira/browse/CAMEL-9921
> Project: Camel
>  Issue Type: Bug
>  Components: camel-dozer
>Affects Versions: 2.15.6, 2.17.0
>Reporter: Tomohisa Igarashi
>Assignee: Claus Ibsen
>Priority: Minor
>
> The configuration variables defined in transformation.xml is not resolved to 
> the value on karaf. It just works in unit test and JBoss EAP via SwitchYard. 
> I also tried to run with camel-2.18-SNAPSHOT, but it requires 
> (&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))
>  while karaf-2.4.4 bundles felix gogo 0.12.1.
> h4. Steps to reproduce
> # Checkout xml-to-json example from here - 
> https://github.com/fusesource/fuseide/tree/master/examples/transformation/xml-to-json
> # Change camel version to 2.17.0 in its pom.xml
> # Run mvn install
> # Start a karaf instance
> # Add URLs
> {code}
> karaf@root> features:addurl 
> mvn:org.apache.camel.karaf/apache-camel/2.17.0/xml/features
> karaf@root> features:addurl 
> mvn:org.jboss.tools.fuse.examples.transformation/xml-to-json/1.0.0-SNAPSHOT/xml/features
> {code}
> # Install the application
> {code}
> karaf@root> features:install xml-to-json
> {code}
> # Copy input file
> {code}
> # cp src/data/abc-order.xml /tmp/inbox/
> {code}
> # Check the output file '/tmp/outbox/xyz-order.json'. You would see  
> "origin":"$\{ORIGIN}" while $\{ORIGIN} should have been resolved to 'Web'.



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

[jira] [Commented] (CAMEL-9922) activemq broker cannot start

[Alexandre Cartapanis (JIRA)]

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

Alexandre Cartapanis commented on CAMEL-9922:
-

This is not happening with camel 2.16.3, is it not a dependency problem with 
camel 2.17.0 ?

> activemq broker cannot start
> 
>
> Key: CAMEL-9922
> URL: https://issues.apache.org/jira/browse/CAMEL-9922
> Project: Camel
>  Issue Type: Bug
>  Components: camel-activemq
>Affects Versions: 2.17.0
> Environment: karaf
>Reporter: Alexandre Cartapanis
>
> On karaf 4.x plateform, with camel 2.17.0 and activemq 5.13.2 features, 
> installs feature activemq-camel and then installs activemq-broker-noweb. The 
> broker fails to start with error java.lang.ClassNotFoundException: 
> org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by 
> org.apache.activemq.activemq-osgi.
> This is not happening with camel 2.16.3
> This is not happening either if activemq-camel is not installed.



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

[jira] [Resolved] (CAMEL-9922) activemq broker cannot start

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9922.

Resolution: Invalid

Report this at Apache ActiveMQ

> activemq broker cannot start
> 
>
> Key: CAMEL-9922
> URL: https://issues.apache.org/jira/browse/CAMEL-9922
> Project: Camel
>  Issue Type: Bug
>  Components: camel-activemq
>Affects Versions: 2.17.0
> Environment: karaf
>Reporter: Alexandre Cartapanis
>
> On karaf 4.x plateform, with camel 2.17.0 and activemq 5.13.2 features, 
> installs feature activemq-camel and then installs activemq-broker-noweb. The 
> broker fails to start with error java.lang.ClassNotFoundException: 
> org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by 
> org.apache.activemq.activemq-osgi.
> This is not happening with camel 2.16.3
> This is not happening either if activemq-camel is not installed.



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

[jira] [Updated] (CAMEL-9922) activemq broker cannot start

[Alexandre Cartapanis (JIRA)]

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

Alexandre Cartapanis updated CAMEL-9922:

Description: 
On karaf 4.x plateform, with camel 2.17.0 and activemq 5.13.2 features, 
installs feature activemq-camel and then installs activemq-broker-noweb. The 
broker fails to start with error java.lang.ClassNotFoundException: 
org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by 
org.apache.activemq.activemq-osgi.
This is not happening with camel 2.16.3
This is not happening either if activemq-camel is not installed.

  was:
On karaf 4.x plateform, with camel 2.17.0 and activemq 5.13.2 features, 
installs feature activemq-camel and then installs activemq-broker-noweb. The 
broker fails to start with error java.lang.ClassNotFoundException: 
org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by 
org.apache.activemq.activemq-osgi.
This is not happening with camel 2.16.3


> activemq broker cannot start
> 
>
> Key: CAMEL-9922
> URL: https://issues.apache.org/jira/browse/CAMEL-9922
> Project: Camel
>  Issue Type: Bug
>  Components: camel-activemq
>Affects Versions: 2.17.0
> Environment: karaf
>Reporter: Alexandre Cartapanis
>
> On karaf 4.x plateform, with camel 2.17.0 and activemq 5.13.2 features, 
> installs feature activemq-camel and then installs activemq-broker-noweb. The 
> broker fails to start with error java.lang.ClassNotFoundException: 
> org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by 
> org.apache.activemq.activemq-osgi.
> This is not happening with camel 2.16.3
> This is not happening either if activemq-camel is not installed.



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

[jira] [Commented] (CAMEL-9922) activemq broker cannot start

[Alexandre Cartapanis (JIRA)]

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

Alexandre Cartapanis commented on CAMEL-9922:
-

The complete stack :

{noformat}
2016-04-28 11:13:48,457 | ERROR | ctivemq.server]) | configadmin
  | 7 - org.apache.felix.configadmin - 1.8.8 | 
[org.osgi.service.cm.ManagedServiceFactory, id=170, 
bundle=96/mvn:org.apache.activemq/activemq-osgi/5.13.2]: Updating configuration 
org.apache.activemq.server.45b6e092-14bf-4c6a-bb0e-0574f812ac52 caused a 
problem: Cannot start the broker
org.osgi.service.cm.ConfigurationException: null : Cannot start the broker
at 
org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:120)[96:org.apache.activemq.activemq-osgi:5.13.2]
at 
org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)[7:org.apache.felix.configadmin:1.8.8]
at 
org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)[7:org.apache.felix.configadmin:1.8.8]
at 
org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1602)[7:org.apache.felix.configadmin:1.8.8]
at 
org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.run(ConfigurationManager.java:1545)[7:org.apache.felix.configadmin:1.8.8]
at 
org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:143)[7:org.apache.felix.configadmin:1.8.8]
at 
org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:110)[7:org.apache.felix.configadmin:1.8.8]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_92]
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: 
Unexpected exception parsing XML document from OSGi 
resource[file:/home/acs/softs/apache-karaf-4.0.5/etc/activemq.xml|bnd.id=96|bnd.sym=org.apache.activemq.activemq-osgi];
 nested exception is org.springframework.beans.FatalBeanException: 
NamespaceHandler class 
[org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] for namespace 
[http://activemq.apache.org/schema/core] not found; nested exception is 
java.lang.ClassNotFoundException: 
org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found from bundle 
[org.apache.activemq.activemq-osgi]
at 
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:413)[117:org.apache.servicemix.bundles.spring-beans:3.2.14.RELEASE_1]
at 
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:335)[117:org.apache.servicemix.bundles.spring-beans:3.2.14.RELEASE_1]
at 
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303)[117:org.apache.servicemix.bundles.spring-beans:3.2.14.RELEASE_1]
at 
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174)[117:org.apache.servicemix.bundles.spring-beans:3.2.14.RELEASE_1]
at 
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:209)[117:org.apache.servicemix.bundles.spring-beans:3.2.14.RELEASE_1]
at 
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:180)[117:org.apache.servicemix.bundles.spring-beans:3.2.14.RELEASE_1]
at 
org.springframework.osgi.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:164)[145:org.springframework.osgi.core:1.2.1]
at 
org.springframework.osgi.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:136)[145:org.springframework.osgi.core:1.2.1]
at 
org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)[120:org.apache.servicemix.bundles.spring-context:3.2.14.RELEASE_1]
at 
org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:539)[120:org.apache.servicemix.bundles.spring-context:3.2.14.RELEASE_1]
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:451)[120:org.apache.servicemix.bundles.spring-context:3.2.14.RELEASE_1]
at 
org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.access$301(AbstractDelegatedExecutionApplicationContext.java:69)[145:org.springframework.osgi.core:1.2.1]
at 

[jira] [Created] (CAMEL-9922) activemq broker cannot start

[Alexandre Cartapanis (JIRA)]

Alexandre Cartapanis created CAMEL-9922:
---

 Summary: activemq broker cannot start
 Key: CAMEL-9922
 URL: https://issues.apache.org/jira/browse/CAMEL-9922
 Project: Camel
  Issue Type: Bug
  Components: camel-activemq
Affects Versions: 2.17.0
 Environment: karaf
Reporter: Alexandre Cartapanis


On karaf 4.x plateform, with camel 2.17.0 and activemq 5.13.2 features, 
installs feature activemq-camel and then installs activemq-broker-noweb. The 
broker fails to start with error java.lang.ClassNotFoundException: 
org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by 
org.apache.activemq.activemq-osgi.
This is not happening with camel 2.16.3



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9916:


How do you setup the connection pool? Ideally you need to setup an init/destroy 
method so its lifecycle is properly handled

There is a little example how for ActiveMQ
http://camel.apache.org/activemq

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

[Catalina-Alina Dobrica (JIRA)]

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

Catalina-Alina Dobrica commented on CAMEL-9916:
---

What I actually should have said is "on context restart".
If you stop only the routes and restart them, the pool is not closed, but in 
the use-case where I needed the feature, the entire context is restarted (by 
stop then start) when you want to restart a route, which causes the component 
to restart and it's pool to be closed.

> SJMS component is not currently nodev/XML route compatible
> --
>
> Key: CAMEL-9916
> URL: https://issues.apache.org/jira/browse/CAMEL-9916
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sjms
>Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a 
> connection factory set.
> * On route restart, the component cannot be reused because the underlying 
> pool is closed and not recreated



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

[jira] [Resolved] (CAMEL-9874) Camel Jetty consumer endpoint incorrectly handles multipart/form-data

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9874.

Resolution: Fixed

> Camel Jetty consumer endpoint incorrectly handles multipart/form-data
> -
>
> Key: CAMEL-9874
> URL: https://issues.apache.org/jira/browse/CAMEL-9874
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jetty
>Affects Versions: 2.17.0
>Reporter: Robert Požarickij
>Assignee: Claus Ibsen
> Fix For: 2.17.1, 2.18.0
>
>
> The problem lies in the way Camel Jetty (camel-jetty9 to be precise) handles 
> multipart/form-data requets.
> The issue consists of two parts:
> * NPE is thrown if no Content-Type is specified in a part;
> * Only application/octet-stream part Content-Type is supported (not sure 
> whether it actually should be relevant)
> Location in code:
> https://github.com/apache/camel/blob/c134e5a6e104c60ddcd198341718a37f0a4401ba/components/camel-jetty9/src/main/java/org/apache/camel/component/jetty9/AttachmentHttpBinding.java#L53
> To reproduce:
> {code}
> from("jetty:http://0.0.0.0:8028;).process((e) -> {});
> {code}
> The call (generated from postman)
> {code}
> OkHttpClient client = new OkHttpClient();
> MediaType mediaType = MediaType.parse("multipart/form-data; 
> boundary=---0111011101101001");
> RequestBody body = RequestBody.create(mediaType, 
> "-0111011101101001\r\nContent-Disposition: form-data; 
> name=\"test\"\r\n\r\ntest\r\n-0111011101101001--");
> Request request = new Request.Builder()
>   .url("http://localhost:8028/;)
>   .post(body)
>   .addHeader("content-type", "multipart/form-data; 
> boundary=---0111011101101001")
>   .addHeader("cache-control", "no-cache")
>   .addHeader("postman-token", "a9fd95b6-04b9-ea7a-687e-ff828ea00774")
>   .build();
> Response response = client.newCall(request).execute();
> {code}
> Exception:
> {code}
> org.apache.camel.RuntimeCamelException: Cannot populate attachments
> at 
> org.apache.camel.component.jetty9.AttachmentHttpBinding.populateAttachments(AttachmentHttpBinding.java:56)
>  ~[camel-jetty-2.17.0.jar!/:2.17.0]
> at 
> org.apache.camel.http.common.DefaultHttpBinding.readRequest(DefaultHttpBinding.java:176)
>  ~[camel-http-common-2.17.0.jar!/:2.17.0]
> at 
> org.apache.camel.http.common.HttpMessage.(HttpMessage.java:52) 
> ~[camel-http-common-2.17.0.jar!/:2.17.0]
> at 
> org.apache.camel.component.jetty.CamelContinuationServlet.service(CamelContinuationServlet.java:161)
>  ~[camel-jetty-common-2.17.0.jar!/:2.17.0]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) 
> ~[javax.servlet-api-3.1.0.jar!/:3.1.0]
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) 
> ~[jetty-servlet-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
>  ~[jetty-servlet-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at 
> org.eclipse.jetty.servlets.MultiPartFilter.doFilter(MultiPartFilter.java:200) 
> ~[jetty-servlets-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at 
> org.apache.camel.component.jetty.CamelFilterWrapper.doFilter(CamelFilterWrapper.java:43)
>  ~[camel-jetty-common-2.17.0.jar!/:2.17.0]
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>  ~[jetty-servlet-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) 
> [jetty-servlet-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
>  [jetty-server-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) 
> [jetty-servlet-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
>  [jetty-server-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
> [jetty-server-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
>  [jetty-server-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at org.eclipse.jetty.server.Server.handle(Server.java:499) 
> [jetty-server-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311) 
> [jetty-server-9.2.15.v20160210.jar!/:9.2.15.v20160210]
> at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) 
> 

[jira] [Resolved] (CAMEL-9805) camel-sql - body not copied from in to out when useing outputHeader and outputType=SelectOne when sql doesn't return a result

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino resolved CAMEL-9805.
-
Resolution: Fixed

Resolved.

[~thomas.ben...@flatironssolutions.com], sorry for the delay. Thanks for 
spotting this and for the test case too.

> camel-sql - body not copied from in to out when useing outputHeader and 
> outputType=SelectOne when sql doesn't return a result
> -
>
> Key: CAMEL-9805
> URL: https://issues.apache.org/jira/browse/CAMEL-9805
> Project: Camel
>  Issue Type: Bug
>  Components: camel-sql
>Affects Versions: 2.17.0
>Reporter: Thomas Bender
>Assignee: Andrea Cosentino
> Fix For: 2.16.4, 2.17.1, 2.18.0
>
> Attachments: CamelSqlComponentTest.java, db-camel-data.sql, 
> db-camel-schema.sql
>
>
> When using the options outputHeader and outputType=SelectOne the body of the 
> Exchange is not copied from in to out when the select returns no data..
> Probably root is line 175-185 of SqlProducer.java that is missing an else for 
> the above mentioned case.
> {code}
> if (data != null) { // <--- Missing the else
> // for noop=true we still want to enrich with the row count header
>   if (getEndpoint().isNoop()) {
> exchange.getOut().setBody(exchange.getIn().getBody());
>   } else if (getEndpoint().getOutputHeader() != null) {
> exchange.getOut().setBody(exchange.getIn().getBody());
> exchange.getOut().setHeader(getEndpoint().getOutputHeader(), data);
>   } else {
> exchange.getOut().setBody(data); 
>   }
>   exchange.getOut().setHeader(SqlConstants.SQL_ROW_COUNT, 1);
> }
> {code}
> following could be added (untested)
> {code}
> else { // if data == null
> if (getEndpoint().isNoop()) {
> 
> exchange.getOut().setBody(exchange.getIn().getBody());
> } else if 
> (getEndpoint().getOutputHeader() != null) {
> 
> exchange.getOut().setBody(exchange.getIn().getBody());
> }
>  exchange.getOut().setHeader(SqlConstants.SQL_ROW_COUNT, 0);
> }
> {code}



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

[jira] [Updated] (CAMEL-9805) camel-sql - body not copied from in to out when useing outputHeader and outputType=SelectOne when sql doesn't return a result

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino updated CAMEL-9805:

Fix Version/s: 2.16.4

> camel-sql - body not copied from in to out when useing outputHeader and 
> outputType=SelectOne when sql doesn't return a result
> -
>
> Key: CAMEL-9805
> URL: https://issues.apache.org/jira/browse/CAMEL-9805
> Project: Camel
>  Issue Type: Bug
>  Components: camel-sql
>Affects Versions: 2.17.0
>Reporter: Thomas Bender
>Assignee: Andrea Cosentino
> Fix For: 2.16.4, 2.17.1, 2.18.0
>
> Attachments: CamelSqlComponentTest.java, db-camel-data.sql, 
> db-camel-schema.sql
>
>
> When using the options outputHeader and outputType=SelectOne the body of the 
> Exchange is not copied from in to out when the select returns no data..
> Probably root is line 175-185 of SqlProducer.java that is missing an else for 
> the above mentioned case.
> {code}
> if (data != null) { // <--- Missing the else
> // for noop=true we still want to enrich with the row count header
>   if (getEndpoint().isNoop()) {
> exchange.getOut().setBody(exchange.getIn().getBody());
>   } else if (getEndpoint().getOutputHeader() != null) {
> exchange.getOut().setBody(exchange.getIn().getBody());
> exchange.getOut().setHeader(getEndpoint().getOutputHeader(), data);
>   } else {
> exchange.getOut().setBody(data); 
>   }
>   exchange.getOut().setHeader(SqlConstants.SQL_ROW_COUNT, 1);
> }
> {code}
> following could be added (untested)
> {code}
> else { // if data == null
> if (getEndpoint().isNoop()) {
> 
> exchange.getOut().setBody(exchange.getIn().getBody());
> } else if 
> (getEndpoint().getOutputHeader() != null) {
> 
> exchange.getOut().setBody(exchange.getIn().getBody());
> }
>  exchange.getOut().setHeader(SqlConstants.SQL_ROW_COUNT, 0);
> }
> {code}



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

[jira] [Commented] (CAMEL-9733) enable dynamic job name in component spring-batch

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9733:


Same story as just commented on that other ticket

> enable dynamic job name in component spring-batch
> -
>
> Key: CAMEL-9733
> URL: https://issues.apache.org/jira/browse/CAMEL-9733
> Project: Camel
>  Issue Type: Wish
>  Components: camel-spring-batch
>Affects Versions: 2.16.2, 2.17.0
> Environment: any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>   Original Estimate: 16m
>  Remaining Estimate: 16m
>
> Hi
> Currently springBatch accepts a parameter jobName in the url, which is 
> evaluated during the creation of the endpoint.
> This makes impossible to launch different jobs dinamically.The requested 
> feature would be to make it message context based, in the headers with a 
> parameter 
> "jobNameHeader", which would be evaluated per message. In a similar way as 
> SQL and the columns value parameters.
> If the project is interested and willing to incorporate it into the sources, 
> I could offer me to code it.



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

[jira] [Commented] (CAMEL-9836) Add file id of the gridfs file created in the header of the exchange

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9836:


Yeah sure, if you can do a PR later today so the source is ready for 
tomorrow/weekend that would be lovely.

> Add file id of the gridfs file created in the header of the exchange
> 
>
> Key: CAMEL-9836
> URL: https://issues.apache.org/jira/browse/CAMEL-9836
> Project: Camel
>  Issue Type: Wish
>  Components: camel-mongodb
>Affects Versions: 2.17.0
> Environment: Any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>
> Currently the camel-mongodb-gridfs component (which is not available in this 
> Jira) when a file is cretated does not return back the Id (_id) of the file 
> created, it only returns  the filename
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> {code}
> mongodb api has the method getid: 
> http://api.mongodb.org/java/current/com/mongodb/gridfs/GridFSFile.html#getId--
> So i'd like to ask to:
> a) create a header field (maybe GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED)
> b) Add the header after the creation
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> 
> exchange.getIn().setHeader(GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED, 
> gfsFile.getId());
> {code}
> Of course I can create a PR myself, but I think the administrative work would 
> be more? Up to you guys.



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

[jira] [Commented] (CAMEL-9733) enable dynamic job name in component spring-batch

[Jose Luis Pedrosa (JIRA)]

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

Jose Luis Pedrosa commented on CAMEL-9733:
--

[~cib...@e-ma.net]  is there any chance I can summit this on time so it's ready 
for 2.17.1? can you give me a deadline?

Rgds

JL

> enable dynamic job name in component spring-batch
> -
>
> Key: CAMEL-9733
> URL: https://issues.apache.org/jira/browse/CAMEL-9733
> Project: Camel
>  Issue Type: Wish
>  Components: camel-spring-batch
>Affects Versions: 2.16.2, 2.17.0
> Environment: any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>   Original Estimate: 16m
>  Remaining Estimate: 16m
>
> Hi
> Currently springBatch accepts a parameter jobName in the url, which is 
> evaluated during the creation of the endpoint.
> This makes impossible to launch different jobs dinamically.The requested 
> feature would be to make it message context based, in the headers with a 
> parameter 
> "jobNameHeader", which would be evaluated per message. In a similar way as 
> SQL and the columns value parameters.
> If the project is interested and willing to incorporate it into the sources, 
> I could offer me to code it.



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

[jira] [Commented] (CAMEL-9836) Add file id of the gridfs file created in the header of the exchange

[Jose Luis Pedrosa (JIRA)]

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

Jose Luis Pedrosa commented on CAMEL-9836:
--

[~cib...@e-ma.net]  is there any chance I can summit this on time so it's ready 
for 2.17.1? It should not take me a long time.. it's very simple, 2 lines of 
code with no risk..

> Add file id of the gridfs file created in the header of the exchange
> 
>
> Key: CAMEL-9836
> URL: https://issues.apache.org/jira/browse/CAMEL-9836
> Project: Camel
>  Issue Type: Wish
>  Components: camel-mongodb
>Affects Versions: 2.17.0
> Environment: Any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.2, 2.18.0
>
>
> Currently the camel-mongodb-gridfs component (which is not available in this 
> Jira) when a file is cretated does not return back the Id (_id) of the file 
> created, it only returns  the filename
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> {code}
> mongodb api has the method getid: 
> http://api.mongodb.org/java/current/com/mongodb/gridfs/GridFSFile.html#getId--
> So i'd like to ask to:
> a) create a header field (maybe GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED)
> b) Add the header after the creation
> {code}
> String metaData = exchange.getIn().getHeader(GridFsEndpoint.GRIDFS_METADATA, 
> String.class);
> DBObject dbObject = (DBObject) JSON.parse(metaData);
> gfsFile.setMetaData(dbObject);
> gfsFile.save();
> exchange.getIn().setHeader(Exchange.FILE_NAME_PRODUCED, 
> gfsFile.getFilename());
> 
> exchange.getIn().setHeader(GridFsEndpoint.GRIDFS_FILE_ID_PRODUCED, 
> gfsFile.getId());
> {code}
> Of course I can create a PR myself, but I think the administrative work would 
> be more? Up to you guys.



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