[jira] [Updated] (CAMEL-8008) SubmitMulti and DataSm not checking CamelSmppAlphabet header
[ https://issues.apache.org/jira/browse/CAMEL-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8008: --- Fix Version/s: 2.15.0 2.14.1 > SubmitMulti and DataSm not checking CamelSmppAlphabet header > > > Key: CAMEL-8008 > URL: https://issues.apache.org/jira/browse/CAMEL-8008 > Project: Camel > Issue Type: Bug > Components: camel-smpp >Affects Versions: 2.14.0 > Environment: n/a >Reporter: Daniel Pocock >Priority: Minor > Fix For: 2.14.1, 2.15.0 > > > According to the documentation, the CamelSmppAlphabet header is used for > SubmitSm, SubmitMulti and DataSm message types > Looking at the code, I noticed it was only used for SubmitSm and not the > other two. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8055) Camel component for atmos integration
[ https://issues.apache.org/jira/browse/CAMEL-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8055: --- Fix Version/s: 2.15.0 > Camel component for atmos integration > - > > Key: CAMEL-8055 > URL: https://issues.apache.org/jira/browse/CAMEL-8055 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.14.0 >Reporter: Alessio C >Assignee: Willem Jiang >Priority: Minor > Labels: atmos, camel > Fix For: 2.15.0 > > > Create a camel component (producers and consumers ) for atmos integration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8055) Camel component for atmos integration
[ https://issues.apache.org/jira/browse/CAMEL-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232700#comment-14232700 ] Claus Ibsen commented on CAMEL-8055: Alessio do you continue to work on this, as we would need the component to be complete before we can include it out of the box. > Camel component for atmos integration > - > > Key: CAMEL-8055 > URL: https://issues.apache.org/jira/browse/CAMEL-8055 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.14.0 >Reporter: Alessio C >Assignee: Willem Jiang >Priority: Minor > Labels: atmos, camel > Fix For: 2.15.0 > > > Create a camel component (producers and consumers ) for atmos integration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8001) SmppUtils.isGsm0338Encodeable() called with arbitrary data
[ https://issues.apache.org/jira/browse/CAMEL-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8001: --- Fix Version/s: 2.13.4 2.15.0 2.14.1 > SmppUtils.isGsm0338Encodeable() called with arbitrary data > -- > > Key: CAMEL-8001 > URL: https://issues.apache.org/jira/browse/CAMEL-8001 > Project: Camel > Issue Type: Bug > Components: camel-smpp >Affects Versions: 2.12.2 > Environment: n/a >Reporter: Daniel Pocock >Assignee: Willem Jiang > Labels: patch > Fix For: 2.14.1, 2.15.0, 2.13.4 > > Attachments: determineAlphabet_fix.patch > > > The method SmppUtils.isGsm0338Encodeable(byte[]) expects the input data to be > Latin1 encoded (or a subset of Latin1, such as ASCII) > The method SmppSmCommand.determineAlphabet(Message) prepares an argument by > calling String.getBytes(charset) without checking the charset is Latin1 or > compatible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8083) Add an option of enable CORS in camel-jetty endpoint
[ https://issues.apache.org/jira/browse/CAMEL-8083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232695#comment-14232695 ] Claus Ibsen commented on CAMEL-8083: We need to update the documentation with the new option http://camel.apache.org/jetty > Add an option of enable CORS in camel-jetty endpoint > > > Key: CAMEL-8083 > URL: https://issues.apache.org/jira/browse/CAMEL-8083 > Project: Camel > Issue Type: New Feature > Components: camel-jetty >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.15.0 > > > While connecting to a jetty endpoint from a development web server running on > a different port, AJAX calls, fail due to CORS restrictions. > It could be more easy for people to use just by set an boolean option from > the endpoint. > Here is a [PR|https://github.com/apache/camel/pull/341] for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8085) Add handling of offset in case of auto commit is disabled to prevent data loss
[ https://issues.apache.org/jira/browse/CAMEL-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8085. Resolution: Fixed > Add handling of offset in case of auto commit is disabled to prevent data loss > -- > > Key: CAMEL-8085 > URL: https://issues.apache.org/jira/browse/CAMEL-8085 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Affects Versions: 2.14.0 >Reporter: Ivan Vasyliev >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.15.0 > > > In order to prevent data loss kafka client allows to manually handle consumer > offset. > According to this lady: > http://ingest.tips/2014/10/12/kafka-high-level-consumer-frequently-missing-pieces/ > Kafka consumer "commitOffset" is committing offset for each consumer and for > all streams of this consumer. > I've made changes in camel-kafka in order to support handling of offset in > case of auto-commit option is disabled. > https://github.com/apache/camel/pull/342 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8085) Add handling of offset in case of auto commit is disabled to prevent data loss
[ https://issues.apache.org/jira/browse/CAMEL-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8085: --- Priority: Minor (was: Critical) > Add handling of offset in case of auto commit is disabled to prevent data loss > -- > > Key: CAMEL-8085 > URL: https://issues.apache.org/jira/browse/CAMEL-8085 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Affects Versions: 2.14.0 >Reporter: Ivan Vasyliev >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.15.0 > > > In order to prevent data loss kafka client allows to manually handle consumer > offset. > According to this lady: > http://ingest.tips/2014/10/12/kafka-high-level-consumer-frequently-missing-pieces/ > Kafka consumer "commitOffset" is committing offset for each consumer and for > all streams of this consumer. > I've made changes in camel-kafka in order to support handling of offset in > case of auto-commit option is disabled. > https://github.com/apache/camel/pull/342 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8113) Look into optimize Camels type converter registry lookup
Claus Ibsen created CAMEL-8113: -- Summary: Look into optimize Camels type converter registry lookup Key: CAMEL-8113 URL: https://issues.apache.org/jira/browse/CAMEL-8113 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 2.15.0, Future See this blog http://tech.ticketmaster.com/2014/12/01/getting-over-the-performance-hump-with-apache-camel/ There is some findings about how Camel's TC may produce GC overhead, and also the CXF MessageContextList. Yeah unfortuntalte camel-cxf had that MessageContextList from the beginning which has been a cause of pain ever since. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8112) upgrade joda-time version to 2.5
[ https://issues.apache.org/jira/browse/CAMEL-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232614#comment-14232614 ] Freeman Fang commented on CAMEL-8112: - I saw on trunk it's already upgraded to joda-time 2.5, should be good also backport to the latest release branch 2.14.x > upgrade joda-time version to 2.5 > > > Key: CAMEL-8112 > URL: https://issues.apache.org/jira/browse/CAMEL-8112 > Project: Camel > Issue Type: Task >Reporter: Freeman Fang >Assignee: Freeman Fang > > this will affect > camel-aws > camel-jibx > camel-salesforce > camel-splunk > components -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (CAMEL-8112) upgrade joda-time version to 2.5
[ https://issues.apache.org/jira/browse/CAMEL-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-8112 started by Freeman Fang. --- > upgrade joda-time version to 2.5 > > > Key: CAMEL-8112 > URL: https://issues.apache.org/jira/browse/CAMEL-8112 > Project: Camel > Issue Type: Task >Reporter: Freeman Fang >Assignee: Freeman Fang > > this will affect > camel-aws > camel-jibx > camel-salesforce > camel-splunk > components -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8112) upgrade joda-time version to 2.5
[ https://issues.apache.org/jira/browse/CAMEL-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-8112: --- Assignee: Freeman Fang > upgrade joda-time version to 2.5 > > > Key: CAMEL-8112 > URL: https://issues.apache.org/jira/browse/CAMEL-8112 > Project: Camel > Issue Type: Task >Reporter: Freeman Fang >Assignee: Freeman Fang > > this will affect > camel-aws > camel-jibx > camel-salesforce > camel-splunk > components -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8112) upgrade joda-time version to 2.5
Freeman Fang created CAMEL-8112: --- Summary: upgrade joda-time version to 2.5 Key: CAMEL-8112 URL: https://issues.apache.org/jira/browse/CAMEL-8112 Project: Camel Issue Type: Task Reporter: Freeman Fang this will affect camel-aws camel-jibx camel-salesforce camel-splunk components -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8111) Upgrade to Pax Exam 4.3
[
https://issues.apache.org/jira/browse/CAMEL-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat resolved CAMEL-8111.
-
Resolution: Fixed
Verified the upgrade both with/without the profile {{karaf3}}.
> Upgrade to Pax Exam 4.3
> ---
>
> Key: CAMEL-8111
> URL: https://issues.apache.org/jira/browse/CAMEL-8111
> Project: Camel
> Issue Type: Task
> Components: osgi, tests
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 2.15.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8110) Google Mail Component
[ https://issues.apache.org/jira/browse/CAMEL-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232125#comment-14232125 ] Jonathan Anstey commented on CAMEL-8110: Added here: http://git-wip-us.apache.org/repos/asf/camel/commit/3c6769db Still need to do up some docs. > Google Mail Component > - > > Key: CAMEL-8110 > URL: https://issues.apache.org/jira/browse/CAMEL-8110 > Project: Camel > Issue Type: New Feature >Reporter: Jonathan Anstey >Assignee: Jonathan Anstey > Fix For: 2.15.0 > > > Looking at creating a component for accessing Google's mail API > https://developers.google.com/gmail/api/v1/reference/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8111) Upgrade to Pax Exam 4.3
Babak Vahdat created CAMEL-8111: --- Summary: Upgrade to Pax Exam 4.3 Key: CAMEL-8111 URL: https://issues.apache.org/jira/browse/CAMEL-8111 Project: Camel Issue Type: Task Components: osgi, tests Reporter: Babak Vahdat Assignee: Babak Vahdat Priority: Minor Fix For: 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8110) Google Mail Component
Jonathan Anstey created CAMEL-8110: -- Summary: Google Mail Component Key: CAMEL-8110 URL: https://issues.apache.org/jira/browse/CAMEL-8110 Project: Camel Issue Type: New Feature Reporter: Jonathan Anstey Assignee: Jonathan Anstey Fix For: 2.15.0 Looking at creating a component for accessing Google's mail API https://developers.google.com/gmail/api/v1/reference/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8050) Google Calendar component
[ https://issues.apache.org/jira/browse/CAMEL-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232096#comment-14232096 ] Jonathan Anstey commented on CAMEL-8050: Committed here: http://git-wip-us.apache.org/repos/asf/camel/commit/d3589e83 Still need to do up some docs. > Google Calendar component > - > > Key: CAMEL-8050 > URL: https://issues.apache.org/jira/browse/CAMEL-8050 > Project: Camel > Issue Type: New Feature >Reporter: Jonathan Anstey >Assignee: Jonathan Anstey > Fix For: 2.15.0 > > > Looking at creating a component for accessing Google's calendar API > https://developers.google.com/google-apps/calendar/v3/reference/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8109) Allow to plugin custom functions to property placeholder
Claus Ibsen created CAMEL-8109:
--
Summary: Allow to plugin custom functions to property placeholder
Key: CAMEL-8109
URL: https://issues.apache.org/jira/browse/CAMEL-8109
Project: Camel
Issue Type: Improvement
Components: camel-core
Affects Versions: 2.14.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.14.1, 2.15.0
To make it more DRY / easy to use
We should allow to plugin custom functions that the properties component (aka
property placeholder) can leverage during resolution.
A function has a name, which is used as prefix:remainder in the {{ }} syntax.
Then people can plugin custom functions that can do any kind of resolution they
want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8108) Type converters should not check for null values
Claus Ibsen created CAMEL-8108: -- Summary: Type converters should not check for null values Key: CAMEL-8108 URL: https://issues.apache.org/jira/browse/CAMEL-8108 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 2.15.0 There is a number of type converters that due to old time behavior, are still doing a != null check for the passed in value. As Camel always passes in a value, then this check should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8099) Add support for default values in Camel properties
[
https://issues.apache.org/jira/browse/CAMEL-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8099.
Resolution: Fixed
> Add support for default values in Camel properties
> --
>
> Key: CAMEL-8099
> URL: https://issues.apache.org/jira/browse/CAMEL-8099
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.14.0
>Reporter: Aaron Whiteside
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.14.1, 2.15.0
>
>
> Add support for default values in Camel properties
> For example:
> {code}
> {{key:default-value}}
> {code}
> Just like Spring's {code}${key:default-value} {code} syntax.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8107) Allow to use property placeholder with default values without having to setup the properties component
Claus Ibsen created CAMEL-8107: -- Summary: Allow to use property placeholder with default values without having to setup the properties component Key: CAMEL-8107 URL: https://issues.apache.org/jira/browse/CAMEL-8107 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.14.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.14.1, 2.15.0 In combination with CAMEL-8099, we should make it easy to use property placeholders with default values, so end users do not have to specify a properties component if we have default values for all needed keys. This allows DRY and keep it minimal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8099) Add support for default values in Camel properties
[
https://issues.apache.org/jira/browse/CAMEL-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8099:
---
Fix Version/s: 2.15.0
2.14.1
> Add support for default values in Camel properties
> --
>
> Key: CAMEL-8099
> URL: https://issues.apache.org/jira/browse/CAMEL-8099
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.14.0
>Reporter: Aaron Whiteside
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.14.1, 2.15.0
>
>
> Add support for default values in Camel properties
> For example:
> {code}
> {{key:default-value}}
> {code}
> Just like Spring's {code}${key:default-value} {code} syntax.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-8099) Add support for default values in Camel properties
[
https://issues.apache.org/jira/browse/CAMEL-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-8099:
--
Assignee: Claus Ibsen
> Add support for default values in Camel properties
> --
>
> Key: CAMEL-8099
> URL: https://issues.apache.org/jira/browse/CAMEL-8099
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.14.0
>Reporter: Aaron Whiteside
>Assignee: Claus Ibsen
>Priority: Minor
>
> Add support for default values in Camel properties
> For example:
> {code}
> {{key:default-value}}
> {code}
> Just like Spring's {code}${key:default-value} {code} syntax.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-8106) XML parsing error is ignored by xtoknize XML tokenizer
[ https://issues.apache.org/jira/browse/CAMEL-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CAMEL-8106. - Resolution: Fixed Fix Version/s: 2.15.0 > XML parsing error is ignored by xtoknize XML tokenizer > -- > > Key: CAMEL-8106 > URL: https://issues.apache.org/jira/browse/CAMEL-8106 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.14.0 >Reporter: Akitoshi Yoshida >Assignee: Akitoshi Yoshida > Fix For: 2.14.1, 2.15.0 > > > XML parsing exceptions are ignored by xtokenize XML tokenizer and this is > leading to the same token extracted repeated times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8106) XML parsing error is ignored by xtoknize XML tokenizer
Akitoshi Yoshida created CAMEL-8106: --- Summary: XML parsing error is ignored by xtoknize XML tokenizer Key: CAMEL-8106 URL: https://issues.apache.org/jira/browse/CAMEL-8106 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.14.0 Reporter: Akitoshi Yoshida Assignee: Akitoshi Yoshida Fix For: 2.14.1 XML parsing exceptions are ignored by xtokenize XML tokenizer and this is leading to the same token extracted repeated times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8101) Add runCommand to MongoDB Camel component operations list
[ https://issues.apache.org/jira/browse/CAMEL-8101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231539#comment-14231539 ] Willem Jiang commented on CAMEL-8101: - Applied the patch into camel master branch with thanks to Pierre. > Add runCommand to MongoDB Camel component operations list > - > > Key: CAMEL-8101 > URL: https://issues.apache.org/jira/browse/CAMEL-8101 > Project: Camel > Issue Type: Improvement > Components: camel-mongodb >Reporter: Pierre-Alban DEWITTE >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.15.0 > > > Add runCommand to MongoDB Camel component operations list > Javadoc of MongoDB driver is there > https://api.mongodb.org/java/2.12/com/mongodb/DB.html#command(com.mongodb.DBObject) > I should update wiki right after the PR is merge. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8100) Collection should be optional for getDbStats
[ https://issues.apache.org/jira/browse/CAMEL-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231540#comment-14231540 ] Willem Jiang commented on CAMEL-8100: - Applied the patch into camel master branch with thanks to Pierre. > Collection should be optional for getDbStats > > > Key: CAMEL-8100 > URL: https://issues.apache.org/jira/browse/CAMEL-8100 > Project: Camel > Issue Type: Bug > Components: camel-mongodb >Affects Versions: 2.13.0, 2.13.2, 2.14.0 >Reporter: Pierre-Alban DEWITTE >Assignee: Willem Jiang >Priority: Trivial > Labels: easyfix > Fix For: 2.15.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > Collection should be optional for getDbStats on route description -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8100) Collection should be optional for getDbStats
[ https://issues.apache.org/jira/browse/CAMEL-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-8100. - Resolution: Fixed > Collection should be optional for getDbStats > > > Key: CAMEL-8100 > URL: https://issues.apache.org/jira/browse/CAMEL-8100 > Project: Camel > Issue Type: Bug > Components: camel-mongodb >Affects Versions: 2.13.0, 2.13.2, 2.14.0 >Reporter: Pierre-Alban DEWITTE >Assignee: Willem Jiang >Priority: Trivial > Labels: easyfix > Fix For: 2.15.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > Collection should be optional for getDbStats on route description -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8102) Add support to ObjectHelper to create Iterable's
[ https://issues.apache.org/jira/browse/CAMEL-8102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-8102. - Resolution: Fixed Fix Version/s: 2.15.0 Applied the patch into camel master branch with thanks to Aaron. > Add support to ObjectHelper to create Iterable's > > > Key: CAMEL-8102 > URL: https://issues.apache.org/jira/browse/CAMEL-8102 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.14.0 >Reporter: Aaron Whiteside >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.15.0 > > Attachments: iterables.patch > > > Add support to ObjectHelper to create Iterable's > Patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-8105) AWS-SQS - support for redrivePolicy inside SQSEndpoint
[ https://issues.apache.org/jira/browse/CAMEL-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231525#comment-14231525 ] Rufus Nash edited comment on CAMEL-8105 at 12/2/14 2:14 PM: Attaching patch for Camel AWS RedrivePolicy for camel version 2.15-SNAPSHOT. was (Author: rufus.nash): Camel AWS RedrivePolicy Patch for version 2.15-SNAPSHOT of camel. > AWS-SQS - support for redrivePolicy inside SQSEndpoint > -- > > Key: CAMEL-8105 > URL: https://issues.apache.org/jira/browse/CAMEL-8105 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Rufus Nash >Priority: Minor > Labels: easyfix, patch > Fix For: 2.15.0 > > Attachments: camel-aws-redrivePolicyPatch.patch > > > Support currently doesn't exist for setting the redrivePolicy through the > endpoint URI inside SQSEndpoint. > This means it is not possible to setup any dead letter queue logic in AWS SQS > without doing so by hand through the front end. > I'll attach a patch which adds the field to the SqsConfiguration and the > handling of that logic inside the SqsEndpoint. As well as extended the basic > tests on proving they get set correctly by the SqsComponentConfigurationTest > Regards > Rufus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8105) AWS-SQS - support for redrivePolicy inside SQSEndpoint
[ https://issues.apache.org/jira/browse/CAMEL-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rufus Nash updated CAMEL-8105: -- Attachment: camel-aws-redrivePolicyPatch.patch Camel AWS RedrivePolicy Patch for version 2.15-SNAPSHOT of camel. > AWS-SQS - support for redrivePolicy inside SQSEndpoint > -- > > Key: CAMEL-8105 > URL: https://issues.apache.org/jira/browse/CAMEL-8105 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Rufus Nash >Priority: Minor > Labels: easyfix, patch > Fix For: 2.15.0 > > Attachments: camel-aws-redrivePolicyPatch.patch > > > Support currently doesn't exist for setting the redrivePolicy through the > endpoint URI inside SQSEndpoint. > This means it is not possible to setup any dead letter queue logic in AWS SQS > without doing so by hand through the front end. > I'll attach a patch which adds the field to the SqsConfiguration and the > handling of that logic inside the SqsEndpoint. As well as extended the basic > tests on proving they get set correctly by the SqsComponentConfigurationTest > Regards > Rufus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-4921) Code Clean-Up (continued 2)
[
https://issues.apache.org/jira/browse/CAMEL-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231319#comment-14231319
]
Babak Vahdat edited comment on CAMEL-4921 at 12/2/14 2:09 PM:
--
Some further work for this ticket:
https://github.com/apache/camel/commit/c8ae4cac990afd79704d318de8fbecea8f684a0d
https://github.com/apache/camel/commit/c7f775ffc179e7c87efc1d41d05116e1c1813659
https://github.com/apache/camel/commit/0e195428ee04531be27a0b659005e3aa8d159d23
https://github.com/apache/camel/commit/cc5c00f54365fda65cfb823ba984ce2b1af5bce5
https://github.com/apache/camel/commit/c778bbcd680ce0b405e2cefb8e0d3b0c20a1efd3
https://github.com/apache/camel/commit/da1813bbf36080c5ed976fc5f6a1665ed067ff75
was (Author: bvahdat):
Some further work on this ticket:
https://github.com/apache/camel/commit/c8ae4cac990afd79704d318de8fbecea8f684a0d
https://github.com/apache/camel/commit/c7f775ffc179e7c87efc1d41d05116e1c1813659
https://github.com/apache/camel/commit/0e195428ee04531be27a0b659005e3aa8d159d23
https://github.com/apache/camel/commit/cc5c00f54365fda65cfb823ba984ce2b1af5bce5
https://github.com/apache/camel/commit/c778bbcd680ce0b405e2cefb8e0d3b0c20a1efd3
> Code Clean-Up (continued 2)
> ---
>
> Key: CAMEL-4921
> URL: https://issues.apache.org/jira/browse/CAMEL-4921
> Project: Camel
> Issue Type: Task
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.0.0
>
>
> The following tasks are in the scope of this ticket:
> - Usage of the {{@Deprecated}} & {{@Override}} annotations where required
> - Reapply the Clean-ups by CAMEL-4796 and CAMEL-4899 as in the meanwhile this
> is, *again*, required
> - Remove the trailing whitespaces on all lines, even on the empty ones
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8105) AWS-SQS - support for redrivePolicy inside SQSEndpoint
Rufus Nash created CAMEL-8105: - Summary: AWS-SQS - support for redrivePolicy inside SQSEndpoint Key: CAMEL-8105 URL: https://issues.apache.org/jira/browse/CAMEL-8105 Project: Camel Issue Type: Improvement Components: camel-aws Reporter: Rufus Nash Priority: Minor Fix For: 2.15.0 Support currently doesn't exist for setting the redrivePolicy through the endpoint URI inside SQSEndpoint. This means it is not possible to setup any dead letter queue logic in AWS SQS without doing so by hand through the front end. I'll attach a patch which adds the field to the SqsConfiguration and the handling of that logic inside the SqsEndpoint. As well as extended the basic tests on proving they get set correctly by the SqsComponentConfigurationTest Regards Rufus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8103) Make CxfEndpoint Camel Context aware
[ https://issues.apache.org/jira/browse/CAMEL-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231465#comment-14231465 ] Willem Jiang commented on CAMEL-8103: - I just added a simple test of cxfRsEndpoint for it. > Make CxfEndpoint Camel Context aware > > > Key: CAMEL-8103 > URL: https://issues.apache.org/jira/browse/CAMEL-8103 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Affects Versions: 2.14.0 >Reporter: Jochen Cordes >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.15.0 > > > Right now the CxfEndpoint is not Camel Context aware. This implies that the > context needs to be "manually" set on the CxfEndpoint when added to the > context. > To make the use of CxfEndpoint a bit easier it would be good if the > CxfEndpoint would be made Camel Context aware so that the context can take of > setting a reference to it on the endpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (CAMEL-7884) camel-netty4-http does not work for HTTP POST requests on routingSlip
[
https://issues.apache.org/jira/browse/CAMEL-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yaron A updated CAMEL-7884:
---
Comment: was deleted
(was: I suggest to remove the "tomcat server" from the comment as it is not
related and the zip you sent them does not contain it either
--
This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this on behalf of the
addressee you must not use, copy, disclose or take action based on this
message or any information herein.
If you have received this message in error, please advise the sender
immediately by reply email and delete this message. Thank you.
)
> camel-netty4-http does not work for HTTP POST requests on routingSlip
> -
>
> Key: CAMEL-7884
> URL: https://issues.apache.org/jira/browse/CAMEL-7884
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4-http
>Affects Versions: 2.14.0
>Reporter: Yaron A
>Assignee: Willem Jiang
> Fix For: 2.14.1, 2.15.0
>
> Attachments: Reproduce2.zip.001, Reproduce2.zip.002, bug-reproduce.zip
>
>
> I tried to add the camel-netty4-http component to a proper working project
> that uses camel-netty-http.
> HTTP GET requests are working properly but POST requests are not working.
> It might be an issue in Netty but I could not find a solution to get it to
> work.
> Here is the exception I see:
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault removed 0 from heap
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault added 0 on disk
> 2014-10-01 09:12:18,012 TRACE [pool-1-thread-1 ]
> [o.a.c.i.c.DefaultTypeConverter] Converting
> io.netty.util.IllegalReferenceCountException -> java.lang.Throwable with
> value: {}
> io.netty.util.IllegalReferenceCountException: refCnt: 0
> at
> io.netty.buffer.AbstractByteBuf.ensureAccessible(AbstractByteBuf.java:1187)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1170)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:676)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:1461)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:40)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> org.apache.camel.component.netty4.http.NettyChannelBufferStreamCache.read(NettyChannelBufferStreamCache.java:69)
> ~[camel-netty4-http-2.14.0.jar:2.14.0]
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) ~[na:1.8.0]
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> ~[na:1.8.0]
> at java.io.BufferedReader.fill(BufferedReader.java:161) ~[na:1.8.0]
> at java.io.BufferedReader.read1(BufferedReader.java:212) ~[na:1.8.0]
> at java.io.BufferedReader.read(BufferedReader.java:286) ~[na:1.8.0]
> at java.io.Reader.read(Reader.java:140) ~[na:1.8.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:304)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:290)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:351)
> ~[camel-core-2.14.0.jar:2.14.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0]
> at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0]
> at
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1002)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:276)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:165)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.MessageSupport.getMandatoryBody(MessageSupport.java:99)
[jira] [Commented] (CAMEL-7884) camel-netty4-http does not work for HTTP POST requests on routingSlip
[
https://issues.apache.org/jira/browse/CAMEL-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231437#comment-14231437
]
Yaron A commented on CAMEL-7884:
I suggest to remove the "tomcat server" from the comment as it is not
related and the zip you sent them does not contain it either
--
This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this on behalf of the
addressee you must not use, copy, disclose or take action based on this
message or any information herein.
If you have received this message in error, please advise the sender
immediately by reply email and delete this message. Thank you.
> camel-netty4-http does not work for HTTP POST requests on routingSlip
> -
>
> Key: CAMEL-7884
> URL: https://issues.apache.org/jira/browse/CAMEL-7884
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4-http
>Affects Versions: 2.14.0
>Reporter: Yaron A
>Assignee: Willem Jiang
> Fix For: 2.14.1, 2.15.0
>
> Attachments: Reproduce2.zip.001, Reproduce2.zip.002, bug-reproduce.zip
>
>
> I tried to add the camel-netty4-http component to a proper working project
> that uses camel-netty-http.
> HTTP GET requests are working properly but POST requests are not working.
> It might be an issue in Netty but I could not find a solution to get it to
> work.
> Here is the exception I see:
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault removed 0 from heap
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault added 0 on disk
> 2014-10-01 09:12:18,012 TRACE [pool-1-thread-1 ]
> [o.a.c.i.c.DefaultTypeConverter] Converting
> io.netty.util.IllegalReferenceCountException -> java.lang.Throwable with
> value: {}
> io.netty.util.IllegalReferenceCountException: refCnt: 0
> at
> io.netty.buffer.AbstractByteBuf.ensureAccessible(AbstractByteBuf.java:1187)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1170)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:676)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:1461)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:40)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> org.apache.camel.component.netty4.http.NettyChannelBufferStreamCache.read(NettyChannelBufferStreamCache.java:69)
> ~[camel-netty4-http-2.14.0.jar:2.14.0]
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) ~[na:1.8.0]
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> ~[na:1.8.0]
> at java.io.BufferedReader.fill(BufferedReader.java:161) ~[na:1.8.0]
> at java.io.BufferedReader.read1(BufferedReader.java:212) ~[na:1.8.0]
> at java.io.BufferedReader.read(BufferedReader.java:286) ~[na:1.8.0]
> at java.io.Reader.read(Reader.java:140) ~[na:1.8.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:304)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:290)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:351)
> ~[camel-core-2.14.0.jar:2.14.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0]
> at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0]
> at
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1002)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:276)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:165)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.MessageSupport.getMandatoryBod
[jira] [Commented] (CAMEL-7884) camel-netty4-http does not work for HTTP POST requests on routingSlip
[
https://issues.apache.org/jira/browse/CAMEL-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231431#comment-14231431
]
Amit Rokach commented on CAMEL-7884:
Hi,
As previously reported - the problem was indeed resolved when running the unit
test with spring 4.0.7-RELEASE - but unfortunately when trying to run it "live"
with tomcat server I still got the same exception.
I'm attaching a zip ("Reproduce2.zip") that includes a jar that can be executed
from command-line, and contains another zip with the sources.
When running the jar it will load the camel route using spring boot.
in order to simulate the issue you need to send any POST message to
http://localhost:8080 on your machine after executing command line.
Thx,
Amit.
> camel-netty4-http does not work for HTTP POST requests on routingSlip
> -
>
> Key: CAMEL-7884
> URL: https://issues.apache.org/jira/browse/CAMEL-7884
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4-http
>Affects Versions: 2.14.0
>Reporter: Yaron A
>Assignee: Willem Jiang
> Fix For: 2.14.1, 2.15.0
>
> Attachments: Reproduce2.zip.001, Reproduce2.zip.002, bug-reproduce.zip
>
>
> I tried to add the camel-netty4-http component to a proper working project
> that uses camel-netty-http.
> HTTP GET requests are working properly but POST requests are not working.
> It might be an issue in Netty but I could not find a solution to get it to
> work.
> Here is the exception I see:
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault removed 0 from heap
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault added 0 on disk
> 2014-10-01 09:12:18,012 TRACE [pool-1-thread-1 ]
> [o.a.c.i.c.DefaultTypeConverter] Converting
> io.netty.util.IllegalReferenceCountException -> java.lang.Throwable with
> value: {}
> io.netty.util.IllegalReferenceCountException: refCnt: 0
> at
> io.netty.buffer.AbstractByteBuf.ensureAccessible(AbstractByteBuf.java:1187)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1170)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:676)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:1461)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:40)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> org.apache.camel.component.netty4.http.NettyChannelBufferStreamCache.read(NettyChannelBufferStreamCache.java:69)
> ~[camel-netty4-http-2.14.0.jar:2.14.0]
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) ~[na:1.8.0]
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> ~[na:1.8.0]
> at java.io.BufferedReader.fill(BufferedReader.java:161) ~[na:1.8.0]
> at java.io.BufferedReader.read1(BufferedReader.java:212) ~[na:1.8.0]
> at java.io.BufferedReader.read(BufferedReader.java:286) ~[na:1.8.0]
> at java.io.Reader.read(Reader.java:140) ~[na:1.8.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:304)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:290)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:351)
> ~[camel-core-2.14.0.jar:2.14.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0]
> at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0]
> at
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1002)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:276)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:165)
> ~[camel-core-2.14.0.jar:2.14.0]
>
[jira] [Updated] (CAMEL-7884) camel-netty4-http does not work for HTTP POST requests on routingSlip
[
https://issues.apache.org/jira/browse/CAMEL-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Rokach updated CAMEL-7884:
---
Attachment: Reproduce2.zip.002
Reproduce2.zip.001
> camel-netty4-http does not work for HTTP POST requests on routingSlip
> -
>
> Key: CAMEL-7884
> URL: https://issues.apache.org/jira/browse/CAMEL-7884
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4-http
>Affects Versions: 2.14.0
>Reporter: Yaron A
>Assignee: Willem Jiang
> Fix For: 2.14.1, 2.15.0
>
> Attachments: Reproduce2.zip.001, Reproduce2.zip.002, bug-reproduce.zip
>
>
> I tried to add the camel-netty4-http component to a proper working project
> that uses camel-netty-http.
> HTTP GET requests are working properly but POST requests are not working.
> It might be an issue in Netty but I could not find a solution to get it to
> work.
> Here is the exception I see:
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault removed 0 from heap
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault added 0 on disk
> 2014-10-01 09:12:18,012 TRACE [pool-1-thread-1 ]
> [o.a.c.i.c.DefaultTypeConverter] Converting
> io.netty.util.IllegalReferenceCountException -> java.lang.Throwable with
> value: {}
> io.netty.util.IllegalReferenceCountException: refCnt: 0
> at
> io.netty.buffer.AbstractByteBuf.ensureAccessible(AbstractByteBuf.java:1187)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1170)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:676)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:1461)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:40)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> org.apache.camel.component.netty4.http.NettyChannelBufferStreamCache.read(NettyChannelBufferStreamCache.java:69)
> ~[camel-netty4-http-2.14.0.jar:2.14.0]
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) ~[na:1.8.0]
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> ~[na:1.8.0]
> at java.io.BufferedReader.fill(BufferedReader.java:161) ~[na:1.8.0]
> at java.io.BufferedReader.read1(BufferedReader.java:212) ~[na:1.8.0]
> at java.io.BufferedReader.read(BufferedReader.java:286) ~[na:1.8.0]
> at java.io.Reader.read(Reader.java:140) ~[na:1.8.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:304)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:290)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:351)
> ~[camel-core-2.14.0.jar:2.14.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0]
> at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0]
> at
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1002)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:276)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:165)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.MessageSupport.getMandatoryBody(MessageSupport.java:99)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.builder.ExpressionBuilder$41.evaluate(ExpressionBuilder.java:1011)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:36)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.component.bean.MethodInfo$2.evaluateParameterBinding(MethodInfo.java:595)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.component.bean.
[jira] [Reopened] (CAMEL-7884) camel-netty4-http does not work for HTTP POST requests on routingSlip
[
https://issues.apache.org/jira/browse/CAMEL-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yaron A reopened CAMEL-7884:
please see the following Amit's comment
> camel-netty4-http does not work for HTTP POST requests on routingSlip
> -
>
> Key: CAMEL-7884
> URL: https://issues.apache.org/jira/browse/CAMEL-7884
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4-http
>Affects Versions: 2.14.0
>Reporter: Yaron A
>Assignee: Willem Jiang
> Fix For: 2.14.1, 2.15.0
>
> Attachments: bug-reproduce.zip
>
>
> I tried to add the camel-netty4-http component to a proper working project
> that uses camel-netty-http.
> HTTP GET requests are working properly but POST requests are not working.
> It might be an issue in Netty but I could not find a solution to get it to
> work.
> Here is the exception I see:
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault removed 0 from heap
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault added 0 on disk
> 2014-10-01 09:12:18,012 TRACE [pool-1-thread-1 ]
> [o.a.c.i.c.DefaultTypeConverter] Converting
> io.netty.util.IllegalReferenceCountException -> java.lang.Throwable with
> value: {}
> io.netty.util.IllegalReferenceCountException: refCnt: 0
> at
> io.netty.buffer.AbstractByteBuf.ensureAccessible(AbstractByteBuf.java:1187)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1170)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:676)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:1461)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:40)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> org.apache.camel.component.netty4.http.NettyChannelBufferStreamCache.read(NettyChannelBufferStreamCache.java:69)
> ~[camel-netty4-http-2.14.0.jar:2.14.0]
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) ~[na:1.8.0]
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> ~[na:1.8.0]
> at java.io.BufferedReader.fill(BufferedReader.java:161) ~[na:1.8.0]
> at java.io.BufferedReader.read1(BufferedReader.java:212) ~[na:1.8.0]
> at java.io.BufferedReader.read(BufferedReader.java:286) ~[na:1.8.0]
> at java.io.Reader.read(Reader.java:140) ~[na:1.8.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:304)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:290)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:351)
> ~[camel-core-2.14.0.jar:2.14.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0]
> at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0]
> at
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1002)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:276)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:165)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.MessageSupport.getMandatoryBody(MessageSupport.java:99)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.builder.ExpressionBuilder$41.evaluate(ExpressionBuilder.java:1011)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:36)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.component.bean.MethodInfo$2.evaluateParameterBinding(MethodInfo.java:595)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.component.bean.MethodInfo$2.evaluate(MethodInfo.java:485)
> ~[camel-core-2.14.0.jar:2.14.
[jira] [Updated] (CAMEL-8086) Possible memoryleak when convertBodyTo is used in a dynamicRouter
[ https://issues.apache.org/jira/browse/CAMEL-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjørn Hilstad updated CAMEL-8086: - Attachment: SomeProcessor.java applicationContext.xml Spring context and Processor > Possible memoryleak when convertBodyTo is used in a dynamicRouter > - > > Key: CAMEL-8086 > URL: https://issues.apache.org/jira/browse/CAMEL-8086 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.13.2 >Reporter: Bjørn Hilstad >Priority: Minor > Attachments: SomeProcessor.java, applicationContext.xml > > > We have implemented a while loop using a dynamicRouter. > The dynamicRouter looks like this: > > someheadername > > where someheadername refers to another route using direct:routename > The route that handles direct:routename looks like this: > > > The someref-bean just puts some data in the body and header and would also be > responsible to set the value of someheadername=null to exit the dynamicRouter. > During execution of these routes we see that heapusage increases until OOM if > the dynamicRouter does not exit before OOM. The number of instances of > DefaultMessage also keeps increasing. > If we remove the from the route we do not get OOM and the > number of instances of DefaultMessage is stable and low. > The same also happens if we replace with a . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CAMEL-8086) Possible memoryleak when convertBodyTo is used in a dynamicRouter
[ https://issues.apache.org/jira/browse/CAMEL-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjørn Hilstad reopened CAMEL-8086: -- I have tried implementing it the way you suggested but the issue is the same. As long as the convertBodyTo is in the route we get the OOM, if I remove it the while loop can run indefinitely without OOM. I am attaching a route (in a spring context) and a simple processor implementation to illustrate this. I can also upload a working application (or maven projects you can build yourself) if required. > Possible memoryleak when convertBodyTo is used in a dynamicRouter > - > > Key: CAMEL-8086 > URL: https://issues.apache.org/jira/browse/CAMEL-8086 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.13.2 >Reporter: Bjørn Hilstad >Priority: Minor > > We have implemented a while loop using a dynamicRouter. > The dynamicRouter looks like this: > > someheadername > > where someheadername refers to another route using direct:routename > The route that handles direct:routename looks like this: > > > The someref-bean just puts some data in the body and header and would also be > responsible to set the value of someheadername=null to exit the dynamicRouter. > During execution of these routes we see that heapusage increases until OOM if > the dynamicRouter does not exit before OOM. The number of instances of > DefaultMessage also keeps increasing. > If we remove the from the route we do not get OOM and the > number of instances of DefaultMessage is stable and low. > The same also happens if we replace with a . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8104) rest-dsl - Allow custom error responses as-is without invoking the output binding
[ https://issues.apache.org/jira/browse/CAMEL-8104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8104. Resolution: Fixed > rest-dsl - Allow custom error responses as-is without invoking the output > binding > - > > Key: CAMEL-8104 > URL: https://issues.apache.org/jira/browse/CAMEL-8104 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.14.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.14.1, 2.15.0 > > > See > http://camel.465427.n5.nabble.com/Rest-DSL-OutType-in-case-of-error-message-problem-tp5759864.html > We should allow end users to define custom error messages as-is to be used as > response. > We add a flag that enables this out of the box. Then the end user just set a > custom body and set the HTTP_RESPONSE_CODE header to >= 300 value to indicate > an error. Then rest-dsl does not attempt to bind output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8104) rest-dsl - Allow custom error responses as-is without invoking the output binding
Claus Ibsen created CAMEL-8104: -- Summary: rest-dsl - Allow custom error responses as-is without invoking the output binding Key: CAMEL-8104 URL: https://issues.apache.org/jira/browse/CAMEL-8104 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.14.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.14.1, 2.15.0 See http://camel.465427.n5.nabble.com/Rest-DSL-OutType-in-case-of-error-message-problem-tp5759864.html We should allow end users to define custom error messages as-is to be used as response. We add a flag that enables this out of the box. Then the end user just set a custom body and set the HTTP_RESPONSE_CODE header to >= 300 value to indicate an error. Then rest-dsl does not attempt to bind output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-4921) Code Clean-Up (continued 2)
[
https://issues.apache.org/jira/browse/CAMEL-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231319#comment-14231319
]
Babak Vahdat commented on CAMEL-4921:
-
Some further work on this ticket:
https://github.com/apache/camel/commit/c8ae4cac990afd79704d318de8fbecea8f684a0d
https://github.com/apache/camel/commit/c7f775ffc179e7c87efc1d41d05116e1c1813659
https://github.com/apache/camel/commit/0e195428ee04531be27a0b659005e3aa8d159d23
https://github.com/apache/camel/commit/cc5c00f54365fda65cfb823ba984ce2b1af5bce5
https://github.com/apache/camel/commit/c778bbcd680ce0b405e2cefb8e0d3b0c20a1efd3
> Code Clean-Up (continued 2)
> ---
>
> Key: CAMEL-4921
> URL: https://issues.apache.org/jira/browse/CAMEL-4921
> Project: Camel
> Issue Type: Task
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.0.0
>
>
> The following tasks are in the scope of this ticket:
> - Usage of the {{@Deprecated}} & {{@Override}} annotations where required
> - Reapply the Clean-ups by CAMEL-4796 and CAMEL-4899 as in the meanwhile this
> is, *again*, required
> - Remove the trailing whitespaces on all lines, even on the empty ones
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8103) Make CxfEndpoint Camel Context aware
[ https://issues.apache.org/jira/browse/CAMEL-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231314#comment-14231314 ] ASF GitHub Bot commented on CAMEL-8103: --- Github user jcordes73 closed the pull request at: https://github.com/apache/camel/pull/347 > Make CxfEndpoint Camel Context aware > > > Key: CAMEL-8103 > URL: https://issues.apache.org/jira/browse/CAMEL-8103 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Affects Versions: 2.14.0 >Reporter: Jochen Cordes >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.15.0 > > > Right now the CxfEndpoint is not Camel Context aware. This implies that the > context needs to be "manually" set on the CxfEndpoint when added to the > context. > To make the use of CxfEndpoint a bit easier it would be good if the > CxfEndpoint would be made Camel Context aware so that the context can take of > setting a reference to it on the endpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8090) Camel-chunk component
[ https://issues.apache.org/jira/browse/CAMEL-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231303#comment-14231303 ] ASF GitHub Bot commented on CAMEL-8090: --- Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/345 > Camel-chunk component > - > > Key: CAMEL-8090 > URL: https://issues.apache.org/jira/browse/CAMEL-8090 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Claus Ibsen >Priority: Minor > Labels: components > Fix For: 2.15.0 > > > Hi all, > I'm currently working on this new Camel component: > https://github.com/oscerd/camel-chunk > This component allows for processing a message using a Chunk template. Chunk > is a templating Java library released under Apache License 2.0. You can find > more information here: http://www.x5software.com/chunk/examples/ChunkExample > Looking at the results of some tests Chunk seems to be very fast and I think > it might be another solution to be added to existing components (Mustache, > Velocity, FreeMarker etc.). > I'd like to have some feedbacks from the developers community and from the > Committers before submitting a pull request on the Camel master branch. > Thanks in advance and let me know your opinion. > *Edit:* _I've submitted a PR with the new component._ > Bye, > Andrea -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7781) Create new PostgreSQL async notifications component
[ https://issues.apache.org/jira/browse/CAMEL-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231278#comment-14231278 ] Claus Ibsen commented on CAMEL-7781: Also do you have documentation included in a readme.md file? eg we would need to include documentation and add it to the Camel components list > Create new PostgreSQL async notifications component > --- > > Key: CAMEL-7781 > URL: https://issues.apache.org/jira/browse/CAMEL-7781 > Project: Camel > Issue Type: New Feature >Reporter: Deven Phillips >Priority: Minor > Labels: features > Fix For: 2.15.0 > > Original Estimate: 80h > Remaining Estimate: 80h > > Create a new component which allows for sending and receiving PostgreSQL's > async notifications using the pgjdbc-ng driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7781) Create new PostgreSQL async notifications component
[ https://issues.apache.org/jira/browse/CAMEL-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231277#comment-14231277 ] Claus Ibsen commented on CAMEL-7781: Deven, is there more work needed on this? > Create new PostgreSQL async notifications component > --- > > Key: CAMEL-7781 > URL: https://issues.apache.org/jira/browse/CAMEL-7781 > Project: Camel > Issue Type: New Feature >Reporter: Deven Phillips >Priority: Minor > Labels: features > Fix For: 2.15.0 > > Original Estimate: 80h > Remaining Estimate: 80h > > Create a new component which allows for sending and receiving PostgreSQL's > async notifications using the pgjdbc-ng driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7781) Create new PostgreSQL async notifications component
[ https://issues.apache.org/jira/browse/CAMEL-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-7781: --- Fix Version/s: 2.15.0 > Create new PostgreSQL async notifications component > --- > > Key: CAMEL-7781 > URL: https://issues.apache.org/jira/browse/CAMEL-7781 > Project: Camel > Issue Type: New Feature >Reporter: Deven Phillips >Priority: Minor > Labels: features > Fix For: 2.15.0 > > Original Estimate: 80h > Remaining Estimate: 80h > > Create a new component which allows for sending and receiving PostgreSQL's > async notifications using the pgjdbc-ng driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8090) Camel-chunk component
[ https://issues.apache.org/jira/browse/CAMEL-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231261#comment-14231261 ] Andrea Cosentino commented on CAMEL-8090: - Sure, Claus. I'll work on the documentation in the next days. I think I'll take example from Camel-mustache documentation. I will update this ticket. Thank you, bye. Andrea > Camel-chunk component > - > > Key: CAMEL-8090 > URL: https://issues.apache.org/jira/browse/CAMEL-8090 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Claus Ibsen >Priority: Minor > Labels: components > Fix For: 2.15.0 > > > Hi all, > I'm currently working on this new Camel component: > https://github.com/oscerd/camel-chunk > This component allows for processing a message using a Chunk template. Chunk > is a templating Java library released under Apache License 2.0. You can find > more information here: http://www.x5software.com/chunk/examples/ChunkExample > Looking at the results of some tests Chunk seems to be very fast and I think > it might be another solution to be added to existing components (Mustache, > Velocity, FreeMarker etc.). > I'd like to have some feedbacks from the developers community and from the > Committers before submitting a pull request on the Camel master branch. > Thanks in advance and let me know your opinion. > *Edit:* _I've submitted a PR with the new component._ > Bye, > Andrea -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8090) Camel-chunk component
[ https://issues.apache.org/jira/browse/CAMEL-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-8090: -- Assignee: Claus Ibsen > Camel-chunk component > - > > Key: CAMEL-8090 > URL: https://issues.apache.org/jira/browse/CAMEL-8090 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Claus Ibsen >Priority: Minor > Labels: components > Fix For: 2.15.0 > > > Hi all, > I'm currently working on this new Camel component: > https://github.com/oscerd/camel-chunk > This component allows for processing a message using a Chunk template. Chunk > is a templating Java library released under Apache License 2.0. You can find > more information here: http://www.x5software.com/chunk/examples/ChunkExample > Looking at the results of some tests Chunk seems to be very fast and I think > it might be another solution to be added to existing components (Mustache, > Velocity, FreeMarker etc.). > I'd like to have some feedbacks from the developers community and from the > Committers before submitting a pull request on the Camel master branch. > Thanks in advance and let me know your opinion. > *Edit:* _I've submitted a PR with the new component._ > Bye, > Andrea -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8090) Camel-chunk component
[ https://issues.apache.org/jira/browse/CAMEL-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8090: --- Fix Version/s: 2.15.0 > Camel-chunk component > - > > Key: CAMEL-8090 > URL: https://issues.apache.org/jira/browse/CAMEL-8090 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Priority: Minor > Labels: components > Fix For: 2.15.0 > > > Hi all, > I'm currently working on this new Camel component: > https://github.com/oscerd/camel-chunk > This component allows for processing a message using a Chunk template. Chunk > is a templating Java library released under Apache License 2.0. You can find > more information here: http://www.x5software.com/chunk/examples/ChunkExample > Looking at the results of some tests Chunk seems to be very fast and I think > it might be another solution to be added to existing components (Mustache, > Velocity, FreeMarker etc.). > I'd like to have some feedbacks from the developers community and from the > Committers before submitting a pull request on the Camel master branch. > Thanks in advance and let me know your opinion. > *Edit:* _I've submitted a PR with the new component._ > Bye, > Andrea -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8090) Camel-chunk component
[ https://issues.apache.org/jira/browse/CAMEL-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231257#comment-14231257 ] Claus Ibsen commented on CAMEL-8090: Thanks do you mind helping with the wiki documentation? http://camel.apache.org/how-do-i-edit-the-website.html > Camel-chunk component > - > > Key: CAMEL-8090 > URL: https://issues.apache.org/jira/browse/CAMEL-8090 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Priority: Minor > Labels: components > Fix For: 2.15.0 > > > Hi all, > I'm currently working on this new Camel component: > https://github.com/oscerd/camel-chunk > This component allows for processing a message using a Chunk template. Chunk > is a templating Java library released under Apache License 2.0. You can find > more information here: http://www.x5software.com/chunk/examples/ChunkExample > Looking at the results of some tests Chunk seems to be very fast and I think > it might be another solution to be added to existing components (Mustache, > Velocity, FreeMarker etc.). > I'd like to have some feedbacks from the developers community and from the > Committers before submitting a pull request on the Camel master branch. > Thanks in advance and let me know your opinion. > *Edit:* _I've submitted a PR with the new component._ > Bye, > Andrea -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8090) Camel-chunk component
[ https://issues.apache.org/jira/browse/CAMEL-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8090: --- Affects Version/s: (was: 2.15.0) > Camel-chunk component > - > > Key: CAMEL-8090 > URL: https://issues.apache.org/jira/browse/CAMEL-8090 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Priority: Minor > Labels: components > > Hi all, > I'm currently working on this new Camel component: > https://github.com/oscerd/camel-chunk > This component allows for processing a message using a Chunk template. Chunk > is a templating Java library released under Apache License 2.0. You can find > more information here: http://www.x5software.com/chunk/examples/ChunkExample > Looking at the results of some tests Chunk seems to be very fast and I think > it might be another solution to be added to existing components (Mustache, > Velocity, FreeMarker etc.). > I'd like to have some feedbacks from the developers community and from the > Committers before submitting a pull request on the Camel master branch. > Thanks in advance and let me know your opinion. > *Edit:* _I've submitted a PR with the new component._ > Bye, > Andrea -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8101) Add runCommand to MongoDB Camel component operations list
[ https://issues.apache.org/jira/browse/CAMEL-8101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8101: --- Fix Version/s: 2.15.0 > Add runCommand to MongoDB Camel component operations list > - > > Key: CAMEL-8101 > URL: https://issues.apache.org/jira/browse/CAMEL-8101 > Project: Camel > Issue Type: Improvement > Components: camel-mongodb >Reporter: Pierre-Alban DEWITTE >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.15.0 > > > Add runCommand to MongoDB Camel component operations list > Javadoc of MongoDB driver is there > https://api.mongodb.org/java/2.12/com/mongodb/DB.html#command(com.mongodb.DBObject) > I should update wiki right after the PR is merge. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8100) Collection should be optional for getDbStats
[ https://issues.apache.org/jira/browse/CAMEL-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8100: --- Fix Version/s: 2.15.0 > Collection should be optional for getDbStats > > > Key: CAMEL-8100 > URL: https://issues.apache.org/jira/browse/CAMEL-8100 > Project: Camel > Issue Type: Bug > Components: camel-mongodb >Affects Versions: 2.13.0, 2.13.2, 2.14.0 >Reporter: Pierre-Alban DEWITTE >Assignee: Willem Jiang >Priority: Trivial > Labels: easyfix > Fix For: 2.15.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > Collection should be optional for getDbStats on route description -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8103) Make CxfEndpoint Camel Context aware
[ https://issues.apache.org/jira/browse/CAMEL-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8103. Resolution: Fixed Fix Version/s: 2.15.0 Assignee: Claus Ibsen Thanks for the PR > Make CxfEndpoint Camel Context aware > > > Key: CAMEL-8103 > URL: https://issues.apache.org/jira/browse/CAMEL-8103 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Affects Versions: 2.14.0 >Reporter: Jochen Cordes >Assignee: Claus Ibsen > Fix For: 2.15.0 > > > Right now the CxfEndpoint is not Camel Context aware. This implies that the > context needs to be "manually" set on the CxfEndpoint when added to the > context. > To make the use of CxfEndpoint a bit easier it would be good if the > CxfEndpoint would be made Camel Context aware so that the context can take of > setting a reference to it on the endpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8103) Make CxfEndpoint Camel Context aware
[ https://issues.apache.org/jira/browse/CAMEL-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231245#comment-14231245 ] Claus Ibsen commented on CAMEL-8103: btw maybe camel-cxf RS has the same problem ? > Make CxfEndpoint Camel Context aware > > > Key: CAMEL-8103 > URL: https://issues.apache.org/jira/browse/CAMEL-8103 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Affects Versions: 2.14.0 >Reporter: Jochen Cordes >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.15.0 > > > Right now the CxfEndpoint is not Camel Context aware. This implies that the > context needs to be "manually" set on the CxfEndpoint when added to the > context. > To make the use of CxfEndpoint a bit easier it would be good if the > CxfEndpoint would be made Camel Context aware so that the context can take of > setting a reference to it on the endpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8103) Make CxfEndpoint Camel Context aware
[ https://issues.apache.org/jira/browse/CAMEL-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8103: --- Priority: Minor (was: Major) > Make CxfEndpoint Camel Context aware > > > Key: CAMEL-8103 > URL: https://issues.apache.org/jira/browse/CAMEL-8103 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Affects Versions: 2.14.0 >Reporter: Jochen Cordes >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.15.0 > > > Right now the CxfEndpoint is not Camel Context aware. This implies that the > context needs to be "manually" set on the CxfEndpoint when added to the > context. > To make the use of CxfEndpoint a bit easier it would be good if the > CxfEndpoint would be made Camel Context aware so that the context can take of > setting a reference to it on the endpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8103) Make CxfEndpoint Camel Context aware
Jochen Cordes created CAMEL-8103: Summary: Make CxfEndpoint Camel Context aware Key: CAMEL-8103 URL: https://issues.apache.org/jira/browse/CAMEL-8103 Project: Camel Issue Type: Improvement Components: camel-cxf Affects Versions: 2.14.0 Reporter: Jochen Cordes Right now the CxfEndpoint is not Camel Context aware. This implies that the context needs to be "manually" set on the CxfEndpoint when added to the context. To make the use of CxfEndpoint a bit easier it would be good if the CxfEndpoint would be made Camel Context aware so that the context can take of setting a reference to it on the endpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8085) Add handling of offset in case of auto commit is disabled to prevent data loss
[ https://issues.apache.org/jira/browse/CAMEL-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231152#comment-14231152 ] Willem Jiang commented on CAMEL-8085: - Applied the patch into camel master branch with thanks to Ivan. > Add handling of offset in case of auto commit is disabled to prevent data loss > -- > > Key: CAMEL-8085 > URL: https://issues.apache.org/jira/browse/CAMEL-8085 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Affects Versions: 2.14.0 >Reporter: Ivan Vasyliev >Assignee: Willem Jiang >Priority: Critical > Fix For: 2.15.0 > > > In order to prevent data loss kafka client allows to manually handle consumer > offset. > According to this lady: > http://ingest.tips/2014/10/12/kafka-high-level-consumer-frequently-missing-pieces/ > Kafka consumer "commitOffset" is committing offset for each consumer and for > all streams of this consumer. > I've made changes in camel-kafka in order to support handling of offset in > case of auto-commit option is disabled. > https://github.com/apache/camel/pull/342 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8038) Fix components to include @UriPath
[ https://issues.apache.org/jira/browse/CAMEL-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8038. Resolution: Fixed > Fix components to include @UriPath > -- > > Key: CAMEL-8038 > URL: https://issues.apache.org/jira/browse/CAMEL-8038 > Project: Camel > Issue Type: Sub-task > Components: camel-core, jmx, tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.15.0 > > > The components that are uri annotation documented need to define one @UriPath > to map to the uri context path. > This is now mistakenly mapped to a @UriParam. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
