[jira] [Updated] (CAMEL-6671) FTP consumer - Add option to not use LIST command
[ https://issues.apache.org/jira/browse/CAMEL-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-6671: --- Priority: Major (was: Minor) Affects Version/s: 2.12.0 Fix Version/s: (was: Future) 2.13.0 2.12.1 Issue Type: Improvement (was: New Feature) This would allow people to download a named file where the user does not have permission on the FTP server to execute the LIST command. > FTP consumer - Add option to not use LIST command > - > > Key: CAMEL-6671 > URL: https://issues.apache.org/jira/browse/CAMEL-6671 > Project: Camel > Issue Type: Improvement > Components: camel-ftp >Affects Versions: 2.12.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.12.1, 2.13.0 > > > If you want to download a single file, and you know the absolute name of the > file, then you should be able to download the file, without using any LIST > commands. As some use-cases have permissions disabled for this, so you can > only download that file only. > The ftp/sftp consumers should have an option to ?useList=false, so they do > not use the list command. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6689) ResourceHelper do not work with encoded file pathes
[ https://issues.apache.org/jira/browse/CAMEL-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-6689: --- Fix Version/s: 2.12.1 2.11.2 > ResourceHelper do not work with encoded file pathes > --- > > Key: CAMEL-6689 > URL: https://issues.apache.org/jira/browse/CAMEL-6689 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Vitalii Tymchyshyn >Priority: Minor > Fix For: 2.11.2, 2.12.1 > > > ResourceHelper in both resolveMandatoryResourceAsInputStream and > resolveMandatoryResourceAsUrl do not decode file path. > This produces problem with file URIs like file:aaa%20bbb.txt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6689) ResourceHelper do not work with encoded file pathes
[ https://issues.apache.org/jira/browse/CAMEL-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-6689: --- Estimated Complexity: Novice (was: Unknown) > ResourceHelper do not work with encoded file pathes > --- > > Key: CAMEL-6689 > URL: https://issues.apache.org/jira/browse/CAMEL-6689 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Vitalii Tymchyshyn >Priority: Minor > Fix For: 2.11.2, 2.12.1 > > > ResourceHelper in both resolveMandatoryResourceAsInputStream and > resolveMandatoryResourceAsUrl do not decode file path. > This produces problem with file URIs like file:aaa%20bbb.txt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-6707) Asynchronous Mode In camel-servlet, Servlet 3.0 AsyncContext
Jörg Schubert created CAMEL-6707: Summary: Asynchronous Mode In camel-servlet, Servlet 3.0 AsyncContext Key: CAMEL-6707 URL: https://issues.apache.org/jira/browse/CAMEL-6707 Project: Camel Issue Type: Improvement Components: camel-http, camel-servlet Affects Versions: 2.13.0 Reporter: Jörg Schubert Priority: Minor My Goal is routing larger amounts of HTTP-Traffic CamelServlet is blocking the HTTP-thread while message is being processed. I'm currently preparing a patch which uses AsyncContext and starts processor in async mode. Hope that will improve throughput. The async feature is switchable by parameter. I will attach a patch as soon as it works. There is one point: To avoid conflicts geronimo-servlet_2.5_spec must be replaced by geronimo-servlet_3.0_spec in parent pom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6671) FTP consumer - Add option to not use LIST command
[ https://issues.apache.org/jira/browse/CAMEL-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6671. Resolution: Fixed > FTP consumer - Add option to not use LIST command > - > > Key: CAMEL-6671 > URL: https://issues.apache.org/jira/browse/CAMEL-6671 > Project: Camel > Issue Type: Improvement > Components: camel-ftp >Affects Versions: 2.12.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.12.1, 2.13.0 > > > If you want to download a single file, and you know the absolute name of the > file, then you should be able to download the file, without using any LIST > commands. As some use-cases have permissions disabled for this, so you can > only download that file only. > The ftp/sftp consumers should have an option to ?useList=false, so they do > not use the list command. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6693) Camel-5676 introduced a regression for JMX with spring/blueprint
[ https://issues.apache.org/jira/browse/CAMEL-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cranton updated CAMEL-6693: - Attachment: CAMEL-6693.diff I've pulled the Unit Test from https://github.com/CamelCookbook/camel-cookbook-examples/blob/master/camel-cookbook-monitoring/src/test/java/org/camelcookbook/monitoring/managed/ManagedSpringTest.java that originally caught the regression, but now that its part of the normal camel build it does not react to the addition or removal of those two lines. I'm guessing I need to run a test with jmx disabled, and then run a spring test with it enabled to catch this case. Feel free to add these test cases as it does exercise ManagedResource. > Camel-5676 introduced a regression for JMX with spring/blueprint > > > Key: CAMEL-6693 > URL: https://issues.apache.org/jira/browse/CAMEL-6693 > Project: Camel > Issue Type: Bug > Components: camel-blueprint, camel-spring, jmx >Affects Versions: 2.12.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.12.0 > > Attachments: CAMEL-6693.diff > > > See > http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-0-tp5738140.html > Scott found a regressions, and pointed out the fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6466) Log component URI parameters should be able to override custom formatter properties
[
https://issues.apache.org/jira/browse/CAMEL-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759018#comment-13759018
]
Raul Kripalani commented on CAMEL-6466:
---
Hi,
Making the log formatter mutable is okay if you use the "convention over
configuration path", i.e. you define the logFormatter in the Spring registry
and mark it with scope=prototype – as Spring hands out a new instance every
time it's requested.
But take into account that the logFormatter can also be injected into the
LogComponent as a standard bean property, and in this case it needs to be
immutable as it will be shared across all log endpoints...
So perhaps we should (a) clone the LogFormatter when creating a new endpoint or
(b) remove the exchangeFormatter from the component level and push it down to
the endpoint level...
Regards,
Raúl.
> Log component URI parameters should be able to override custom formatter
> properties
> ---
>
> Key: CAMEL-6466
> URL: https://issues.apache.org/jira/browse/CAMEL-6466
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.11.0
>Reporter: Nathan Jensen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.11.2, 2.12.0
>
>
> Our project uses a custom log formatter of type
> org.apache.camel.component.log.LogFormatter, the only difference is we have
> changed the defaults from camel's standard defaults. Unfortunately, by
> registering a custom formatter we can no longer have a route specifically
> diverge from the system wide formatter for special cases.
> For example, the following works when we don't have a custom formatter but
> fails when do have a custom formatter:
>
> It fails with a FailedToCreateRouteException with the message "There are 3
> parameters that couldn't be set on the endpoint. Check the uri if the
> parameters are spelt correctly and that they are properties of the endpoint.
> Unknown parameters=[{showBody=false, showCaughtException=true,
> showStackTrace=true}]".
> The root of the problem is that the logic in LogComponent.createEndpoint()
> only sets the URI parameters on the localFormatter if there is no custom
> formatter already registered, otherwise it tries to set the parameters on the
> endpoint itself and not the formatter.
> It would be nice if the log route URIs were able to override parameters on
> the custom formatter for routes that need special cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-6708) camel-rabbitmq component RabbitMQConsumer.RabbitConsumer#handleDelivery does not handle AMQP.BasicProperties
Daniel Williams created CAMEL-6708: -- Summary: camel-rabbitmq component RabbitMQConsumer.RabbitConsumer#handleDelivery does not handle AMQP.BasicProperties Key: CAMEL-6708 URL: https://issues.apache.org/jira/browse/CAMEL-6708 Project: Camel Issue Type: Bug Affects Versions: 2.12.1 Environment: All Reporter: Daniel Williams RabbitMQConsumer.RabbitConsumer#handleDelivery currently does not handle AMQP.BasicProperties as sent from the RabbitMQ client library and passed onto the consumer. This poses a problem for downstream functionality. e.g. post a message to a queueA configure camel as from(queueA).to(queueB).end(); pull a message from queueB deserialize If the message was pushed with header information such as Type it will be stripped off as the RabbitMQConsumer.RabbitConsume#handleDelivery is invoked cause the RabbitMQProducer to transmit to queueB without the header information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6708) camel-rabbitmq component RabbitMQConsumer.RabbitConsumer#handleDelivery does not handle AMQP.BasicProperties
[ https://issues.apache.org/jira/browse/CAMEL-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Williams updated CAMEL-6708: --- Attachment: patch.txt Introduction of a new method that will copy properties from the AMQP.BasicProperties using a meta-map of method to header name to copy values using reflection. Could be optimized to cache Method[] > camel-rabbitmq component RabbitMQConsumer.RabbitConsumer#handleDelivery does > not handle AMQP.BasicProperties > > > Key: CAMEL-6708 > URL: https://issues.apache.org/jira/browse/CAMEL-6708 > Project: Camel > Issue Type: Bug >Affects Versions: 2.12.1 > Environment: All >Reporter: Daniel Williams > Attachments: patch.txt > > > RabbitMQConsumer.RabbitConsumer#handleDelivery currently does not handle > AMQP.BasicProperties as sent from the RabbitMQ client library and passed onto > the consumer. This poses a problem for downstream functionality. > e.g. > post a message to a queueA > configure camel as from(queueA).to(queueB).end(); > pull a message from queueB > deserialize > If the message was pushed with header information such as Type it will be > stripped off as the RabbitMQConsumer.RabbitConsume#handleDelivery is invoked > cause the RabbitMQProducer to transmit to queueB without the header > information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-6709) camel-yammer - Endpoint yammer:current throwns JsonMappingException exception camel-yammer - Endpoint yammer:current throwns JsonMappingException exception
Jonathan Anstey created CAMEL-6709: -- Summary: camel-yammer - Endpoint yammer:current throwns JsonMappingException exception camel-yammer - Endpoint yammer:current throwns JsonMappingException exception Key: CAMEL-6709 URL: https://issues.apache.org/jira/browse/CAMEL-6709 Project: Camel Issue Type: Bug Affects Versions: 2.12.0 Reporter: Jonathan Anstey Assignee: Jonathan Anstey Fix For: 2.12.1 Getting org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance of java.util.ArrayList out of START_OBJECT token when trying to return the current user using yammer:current. Workaround is to just add ?useJson=true and do marshaling manually. Fixing on master shortly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6709) camel-yammer - Endpoint yammer:current throwns JsonMappingException exception
[ https://issues.apache.org/jira/browse/CAMEL-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey updated CAMEL-6709: --- Summary: camel-yammer - Endpoint yammer:current throwns JsonMappingException exception (was: camel-yammer - Endpoint yammer:current throwns JsonMappingException exception camel-yammer - Endpoint yammer:current throwns JsonMappingException exception ) > camel-yammer - Endpoint yammer:current throwns JsonMappingException exception > -- > > Key: CAMEL-6709 > URL: https://issues.apache.org/jira/browse/CAMEL-6709 > Project: Camel > Issue Type: Bug >Affects Versions: 2.12.0 >Reporter: Jonathan Anstey >Assignee: Jonathan Anstey > Fix For: 2.12.1 > > > Getting > org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance > of java.util.ArrayList out of START_OBJECT token > when trying to return the current user using yammer:current. Workaround is to > just add ?useJson=true and do marshaling manually. Fixing on master shortly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6709) camel-yammer - Endpoint yammer:current throwns JsonMappingException exception
[ https://issues.apache.org/jira/browse/CAMEL-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey resolved CAMEL-6709. Resolution: Fixed > camel-yammer - Endpoint yammer:current throwns JsonMappingException exception > -- > > Key: CAMEL-6709 > URL: https://issues.apache.org/jira/browse/CAMEL-6709 > Project: Camel > Issue Type: Bug >Affects Versions: 2.12.0 >Reporter: Jonathan Anstey >Assignee: Jonathan Anstey > Fix For: 2.12.1 > > > Getting > org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance > of java.util.ArrayList out of START_OBJECT token > when trying to return the current user using yammer:current. Workaround is to > just add ?useJson=true and do marshaling manually. Fixing on master shortly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6709) camel-yammer - Endpoint yammer:current throwns JsonMappingException exception
[ https://issues.apache.org/jira/browse/CAMEL-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759090#comment-13759090 ] Jonathan Anstey commented on CAMEL-6709: Fixed with https://git-wip-us.apache.org/repos/asf?p=camel.git;a=commit;h=420ab5d2 No need to hold up 2.12 release for this as you can still get the raw info of the current user via useJson=true. > camel-yammer - Endpoint yammer:current throwns JsonMappingException exception > -- > > Key: CAMEL-6709 > URL: https://issues.apache.org/jira/browse/CAMEL-6709 > Project: Camel > Issue Type: Bug >Affects Versions: 2.12.0 >Reporter: Jonathan Anstey >Assignee: Jonathan Anstey > Fix For: 2.12.1 > > > Getting > org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance > of java.util.ArrayList out of START_OBJECT token > when trying to return the current user using yammer:current. Workaround is to > just add ?useJson=true and do marshaling manually. Fixing on master shortly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6693) Camel-5676 introduced a regression for JMX with spring/blueprint
[ https://issues.apache.org/jira/browse/CAMEL-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759095#comment-13759095 ] Claus Ibsen commented on CAMEL-6693: Thanks for the tests I will add them. > Camel-5676 introduced a regression for JMX with spring/blueprint > > > Key: CAMEL-6693 > URL: https://issues.apache.org/jira/browse/CAMEL-6693 > Project: Camel > Issue Type: Bug > Components: camel-blueprint, camel-spring, jmx >Affects Versions: 2.12.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.12.0 > > Attachments: CAMEL-6693.diff > > > See > http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-0-tp5738140.html > Scott found a regressions, and pointed out the fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-6710) Add endpoint to consume received messages in camel-yammer
Jonathan Anstey created CAMEL-6710: -- Summary: Add endpoint to consume received messages in camel-yammer Key: CAMEL-6710 URL: https://issues.apache.org/jira/browse/CAMEL-6710 Project: Camel Issue Type: Improvement Reporter: Jonathan Anstey Assignee: Jonathan Anstey Fix For: 2.12.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6710) Add endpoint to consume received messages in camel-yammer
[ https://issues.apache.org/jira/browse/CAMEL-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey resolved CAMEL-6710. Resolution: Fixed http://git-wip-us.apache.org/repos/asf/camel/commit/d197e4ef > Add endpoint to consume received messages in camel-yammer > -- > > Key: CAMEL-6710 > URL: https://issues.apache.org/jira/browse/CAMEL-6710 > Project: Camel > Issue Type: Improvement >Reporter: Jonathan Anstey >Assignee: Jonathan Anstey > Fix For: 2.12.1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6708) camel-rabbitmq component RabbitMQConsumer.RabbitConsumer#handleDelivery does not handle AMQP.BasicProperties
[ https://issues.apache.org/jira/browse/CAMEL-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Williams updated CAMEL-6708: --- Attachment: patch.txt > camel-rabbitmq component RabbitMQConsumer.RabbitConsumer#handleDelivery does > not handle AMQP.BasicProperties > > > Key: CAMEL-6708 > URL: https://issues.apache.org/jira/browse/CAMEL-6708 > Project: Camel > Issue Type: Bug >Affects Versions: 2.12.1 > Environment: All >Reporter: Daniel Williams > Attachments: patch.txt > > > RabbitMQConsumer.RabbitConsumer#handleDelivery currently does not handle > AMQP.BasicProperties as sent from the RabbitMQ client library and passed onto > the consumer. This poses a problem for downstream functionality. > e.g. > post a message to a queueA > configure camel as from(queueA).to(queueB).end(); > pull a message from queueB > deserialize > If the message was pushed with header information such as Type it will be > stripped off as the RabbitMQConsumer.RabbitConsume#handleDelivery is invoked > cause the RabbitMQProducer to transmit to queueB without the header > information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6708) camel-rabbitmq component RabbitMQConsumer.RabbitConsumer#handleDelivery does not handle AMQP.BasicProperties
[ https://issues.apache.org/jira/browse/CAMEL-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Williams updated CAMEL-6708: --- Attachment: (was: patch.txt) > camel-rabbitmq component RabbitMQConsumer.RabbitConsumer#handleDelivery does > not handle AMQP.BasicProperties > > > Key: CAMEL-6708 > URL: https://issues.apache.org/jira/browse/CAMEL-6708 > Project: Camel > Issue Type: Bug >Affects Versions: 2.12.1 > Environment: All >Reporter: Daniel Williams > Attachments: patch.txt > > > RabbitMQConsumer.RabbitConsumer#handleDelivery currently does not handle > AMQP.BasicProperties as sent from the RabbitMQ client library and passed onto > the consumer. This poses a problem for downstream functionality. > e.g. > post a message to a queueA > configure camel as from(queueA).to(queueB).end(); > pull a message from queueB > deserialize > If the message was pushed with header information such as Type it will be > stripped off as the RabbitMQConsumer.RabbitConsume#handleDelivery is invoked > cause the RabbitMQProducer to transmit to queueB without the header > information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6677) Allow customization of the JAXB underlying XMLStreamWriter
[ https://issues.apache.org/jira/browse/CAMEL-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Posta updated CAMEL-6677: --- Attachment: CAMEL-6677-2.patch Claus, looking for feedback here. data formats don't have good access to the camel context (unless in the data format itself, which not all have), so looking up beans can be hit or miss depending on the data format used. For jaxb it works fine. See revised patch and give suggestions. Check the changes I made for DataFormatDefinition. It correctly resolves refNames that start with '#' but not very pretty :) All tests pass... > Allow customization of the JAXB underlying XMLStreamWriter > -- > > Key: CAMEL-6677 > URL: https://issues.apache.org/jira/browse/CAMEL-6677 > Project: Camel > Issue Type: Improvement > Components: camel-jaxb >Affects Versions: 2.11.1 >Reporter: Christian Posta >Priority: Minor > Fix For: 2.11.2, 2.12.1 > > Attachments: CAMEL-6677-2.patch, CAMEL-6677.patch > > > Right now the jaxb component allows you to filter out non-xml characters. But > there might be use cases where you'd want to do something other than just > filter (maybe escape? > http://blog.lesc.se/2009/03/escape-illegal-characters-with-jaxb-xml.html or > replace with something else?) the non-xml characters. JAXB has a mechanism to > allow pre-processing of the output of its marshaling and we should expose a > way to customize that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
