[jira] [Work logged] (CAMEL-13071) Elasticsearch rest component should support scroll api
[
https://issues.apache.org/jira/browse/CAMEL-13071?focusedWorklogId=186199=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-186199
]
ASF GitHub Bot logged work on CAMEL-13071:
--
Author: ASF GitHub Bot
Created on: 17/Jan/19 07:35
Start Date: 17/Jan/19 07:35
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #2710: CAMEL-13071:
camel-elasticsearch-rest - Add scroll api support
URL: https://github.com/apache/camel/pull/2710
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 186199)
Time Spent: 20m (was: 10m)
> Elasticsearch rest component should support scroll api
> --
>
> Key: CAMEL-13071
> URL: https://issues.apache.org/jira/browse/CAMEL-13071
> Project: Camel
> Issue Type: New Feature
> Components: camel-elasticsearch-rest
>Affects Versions: 2.23.0
>Reporter: Ludovic Boutros
>Assignee: Andrea Cosentino
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> On some projects we need to fetch all results from Elasticsearch.
> This is currently quite difficult.
> Here is an example of usage that could be implemented:
> {code:java|title=ElasticsearchRouter.java|borderStyle=solid}
> from("direct:search")
>
> .to("elasticsearch-rest://elasticsearch?operation=Search=twitter=tweet=true=3")
> .split()
> .body()
> .streaming()
> .to("mock:output")
> .end();
> {code}
> Two new parameters could be used:
> * useScroll: enable scroll usage
> * scrollKeepAliveMs: time in ms during which elasticsearch will keep search
> context alive
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12982) Add support for alternative RAW() syntax
[
https://issues.apache.org/jira/browse/CAMEL-12982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744700#comment-16744700
]
Tadayoshi Sato edited comment on CAMEL-12982 at 1/17/19 5:49 AM:
-
I understand that diverging ideas without clear needs isn't good at this
moment. Meanwhile, at least there is a need that a user occasionally wants to
use RAW values like {{foo)&+bar}} in the URI, so let's go back and stick to
this original request and support RAW{} syntax to solve it. A pull req will
follow soon.
While working on the fix, I learned the current limitations (including my fix)
of RAW syntax handling in Camel. Let me write them down here:
Currently Camel supports RAW() syntax in two parts of the endpoint URI: 1)
query part and 2) host/path part.
# Query part: e.g. {{?password=RAW(p+?%w0rd)=scott}}
** In this part almost every character is allowed, including ')' and '}'. If
you want to use ')&' or '}&' inside RAW then use the other brackets, i.e. RAW
\{..}for ')&' and RAW(..) for '}&'.
** RAW can be used only in the value of a query. A key cannot be notated with
RAW. If you use RAW in value, use it entirely. Partial usage such as
{{password=RAW(%%%)bar&...}} is not allowed.
** Implementation details: The query scanner detects the occurrence of ')&' or
'}&' as the closing of each RAW token.
# Host/path part: e.g. {{mock:RAW(se+ret)+language:xpath:/order/@uri}}
** I don't know when it's useful but for some components usages of RAW syntax
in the URI are allowed (e.g. mock component).
** However, unlike the query part, it's not possible to use RAW(foo)bar) or
RAW\{foo}bar} in this part. It's still possible to use RAW(foo}bar) and
RAW\{foo)bar} though.
** Implementation details: This is because the scanner cannot rely on ')&' or
'}&' for the closing mark in host/path part and thus picks up the first
occurrence of the closing bracket as the closing.
** {{toD}} DSL falls into this category. If you use {{toD}} you need to follow
the same limitations of the host/path part.
was (Author: tadayosi):
I understand that diverging ideas without clear needs isn't good at this
moment. Meanwhile, at least there is a need that a user occasionally wants to
use RAW values like {{foo)&+bar}} in the URI, so let's go back and stick to
this original request and support RAW{} syntax to solve it. A pull req will
follow soon.
While working on the fix, I learned the current limitations (including my fix)
of RAW syntax handling in Camel. Let me write them down here:
Currently Camel supports RAW() syntax in two parts of the endpoint URI: 1)
query part and 2) host/path part.
# Query part: e.g. {{?password=RAW(p+?%w0rd)=scott}}
** In this part almost every character is allowed, including ')' and '}'. If
you want to use ')&' or '}&' inside RAW then use the other brackets, i.e.
RAW{..} for ')&' and RAW(..) for '}&'.
** RAW can be used only in the value of a query. A key cannot be notated with
RAW. If you use RAW in value, use it entirely. Partial usage such as
{{password=RAW(%%%)bar&...}} is not allowed.
** Implementation details: The query scanner detects the occurrence of ')&' or
'}&' as the closing of each RAW token.
# Host/path part: e.g. {{mock:RAW(se+ret)+language:xpath:/order/@uri}}
** I don't know when it's useful but for some components usages of RAW syntax
in the URI are allowed (e.g. mock component).
** However, unlike the query part, it's not possible to use RAW(foo)bar) or
RAW\{foo\}bar\} in this part. It's still possible to use RAW(foo\}bar) and
RAW\{foo)bar\} though.
** Implementation details: This is because the scanner cannot rely on ')&' or
'}&' for the closing mark in host/path part and thus picks up the first
occurrence of the closing bracket as the closing.
> Add support for alternative RAW() syntax
>
>
> Key: CAMEL-12982
> URL: https://issues.apache.org/jira/browse/CAMEL-12982
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Tadayoshi Sato
>Priority: Major
> Fix For: 3.0.0, 2.24.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In some edge case you may have a password=foo)+bar which you want to use
> as-is. The + sign gets escaped and therefore you need to use RAW syntax. But
> the closing paranthesis is used the first one. And the parser is not always
> smart enough. But this can be tricky to improve as you can use =v as will
> and the parser thinks its a new option etc.
> So instead we should add an alternative syntax such as RAW{} where we use
> curly brackets.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-12982) Add support for alternative RAW() syntax
[
https://issues.apache.org/jira/browse/CAMEL-12982?focusedWorklogId=186165=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-186165
]
ASF GitHub Bot logged work on CAMEL-12982:
--
Author: ASF GitHub Bot
Created on: 17/Jan/19 05:39
Start Date: 17/Jan/19 05:39
Worklog Time Spent: 10m
Work Description: tadayosi commented on pull request #2712: CAMEL-12982:
Support RAW{} syntax in URISupport
URL: https://github.com/apache/camel/pull/2712
https://issues.apache.org/jira/browse/CAMEL-12982
Hi guys, please review it before merging it. I refactored the RAW handling
part of the code a bit, so if we decide to support fancier syntax like
`RAW[[[...]]]` and `RAWaaa...aaa` in the future, it should still serve such
enhancements.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 186165)
Time Spent: 10m
Remaining Estimate: 0h
> Add support for alternative RAW() syntax
>
>
> Key: CAMEL-12982
> URL: https://issues.apache.org/jira/browse/CAMEL-12982
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Tadayoshi Sato
>Priority: Major
> Fix For: 3.0.0, 2.24.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In some edge case you may have a password=foo)+bar which you want to use
> as-is. The + sign gets escaped and therefore you need to use RAW syntax. But
> the closing paranthesis is used the first one. And the parser is not always
> smart enough. But this can be tricky to improve as you can use =v as will
> and the parser thinks its a new option etc.
> So instead we should add an alternative syntax such as RAW{} where we use
> curly brackets.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12982) Add support for alternative RAW() syntax
[
https://issues.apache.org/jira/browse/CAMEL-12982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744700#comment-16744700
]
Tadayoshi Sato commented on CAMEL-12982:
I understand that diverging ideas without clear needs isn't good at this
moment. Meanwhile, at least there is a need that a user occasionally wants to
use RAW values like {{foo)&+bar}} in the URI, so let's go back and stick to
this original request and support RAW{} syntax to solve it. A pull req will
follow soon.
While working on the fix, I learned the current limitations (including my fix)
of RAW syntax handling in Camel. Let me write them down here:
Currently Camel supports RAW() syntax in two parts of the endpoint URI: 1)
query part and 2) host/path part.
# Query part: e.g. {{?password=RAW(p+?%w0rd)=scott}}
** In this part almost every character is allowed, including ')' and '}'. If
you want to use ')&' or '}&' inside RAW then use the other brackets, i.e.
RAW{..} for ')&' and RAW(..) for '}&'.
** RAW can be used only in the value of a query. A key cannot be notated with
RAW. If you use RAW in value, use it entirely. Partial usage such as
{{password=RAW(%%%)bar&...}} is not allowed.
** Implementation details: The query scanner detects the occurrence of ')&' or
'}&' as the closing of each RAW token.
# Host/path part: e.g. {{mock:RAW(se+ret)+language:xpath:/order/@uri}}
** I don't know when it's useful but for some components usages of RAW syntax
in the URI are allowed (e.g. mock component).
** However, unlike the query part, it's not possible to use RAW(foo)bar) or
RAW{foo}bar} in this part. It's still possible to use RAW(foo}bar) and
RAW{foo)bar} though.
** Implementation details: This is because the scanner cannot rely on ')&' or
'}&' for the closing mark in host/path part and thus picks up the first
occurrence of the closing bracket as the closing.
> Add support for alternative RAW() syntax
>
>
> Key: CAMEL-12982
> URL: https://issues.apache.org/jira/browse/CAMEL-12982
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Tadayoshi Sato
>Priority: Major
> Fix For: 3.0.0, 2.24.0
>
>
> In some edge case you may have a password=foo)+bar which you want to use
> as-is. The + sign gets escaped and therefore you need to use RAW syntax. But
> the closing paranthesis is used the first one. And the parser is not always
> smart enough. But this can be tricky to improve as you can use =v as will
> and the parser thinks its a new option etc.
> So instead we should add an alternative syntax such as RAW{} where we use
> curly brackets.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12982) Add support for alternative RAW() syntax
[
https://issues.apache.org/jira/browse/CAMEL-12982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744700#comment-16744700
]
Tadayoshi Sato edited comment on CAMEL-12982 at 1/17/19 5:33 AM:
-
I understand that diverging ideas without clear needs isn't good at this
moment. Meanwhile, at least there is a need that a user occasionally wants to
use RAW values like {{foo)&+bar}} in the URI, so let's go back and stick to
this original request and support RAW{} syntax to solve it. A pull req will
follow soon.
While working on the fix, I learned the current limitations (including my fix)
of RAW syntax handling in Camel. Let me write them down here:
Currently Camel supports RAW() syntax in two parts of the endpoint URI: 1)
query part and 2) host/path part.
# Query part: e.g. {{?password=RAW(p+?%w0rd)=scott}}
** In this part almost every character is allowed, including ')' and '}'. If
you want to use ')&' or '}&' inside RAW then use the other brackets, i.e.
RAW{..} for ')&' and RAW(..) for '}&'.
** RAW can be used only in the value of a query. A key cannot be notated with
RAW. If you use RAW in value, use it entirely. Partial usage such as
{{password=RAW(%%%)bar&...}} is not allowed.
** Implementation details: The query scanner detects the occurrence of ')&' or
'}&' as the closing of each RAW token.
# Host/path part: e.g. {{mock:RAW(se+ret)+language:xpath:/order/@uri}}
** I don't know when it's useful but for some components usages of RAW syntax
in the URI are allowed (e.g. mock component).
** However, unlike the query part, it's not possible to use RAW(foo)bar) or
RAW\{foo\}bar\} in this part. It's still possible to use RAW(foo\}bar) and
RAW\{foo)bar\} though.
** Implementation details: This is because the scanner cannot rely on ')&' or
'}&' for the closing mark in host/path part and thus picks up the first
occurrence of the closing bracket as the closing.
was (Author: tadayosi):
I understand that diverging ideas without clear needs isn't good at this
moment. Meanwhile, at least there is a need that a user occasionally wants to
use RAW values like {{foo)&+bar}} in the URI, so let's go back and stick to
this original request and support RAW{} syntax to solve it. A pull req will
follow soon.
While working on the fix, I learned the current limitations (including my fix)
of RAW syntax handling in Camel. Let me write them down here:
Currently Camel supports RAW() syntax in two parts of the endpoint URI: 1)
query part and 2) host/path part.
# Query part: e.g. {{?password=RAW(p+?%w0rd)=scott}}
** In this part almost every character is allowed, including ')' and '}'. If
you want to use ')&' or '}&' inside RAW then use the other brackets, i.e.
RAW{..} for ')&' and RAW(..) for '}&'.
** RAW can be used only in the value of a query. A key cannot be notated with
RAW. If you use RAW in value, use it entirely. Partial usage such as
{{password=RAW(%%%)bar&...}} is not allowed.
** Implementation details: The query scanner detects the occurrence of ')&' or
'}&' as the closing of each RAW token.
# Host/path part: e.g. {{mock:RAW(se+ret)+language:xpath:/order/@uri}}
** I don't know when it's useful but for some components usages of RAW syntax
in the URI are allowed (e.g. mock component).
** However, unlike the query part, it's not possible to use RAW(foo)bar) or
RAW{foo}bar} in this part. It's still possible to use RAW(foo}bar) and
RAW{foo)bar} though.
** Implementation details: This is because the scanner cannot rely on ')&' or
'}&' for the closing mark in host/path part and thus picks up the first
occurrence of the closing bracket as the closing.
> Add support for alternative RAW() syntax
>
>
> Key: CAMEL-12982
> URL: https://issues.apache.org/jira/browse/CAMEL-12982
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Tadayoshi Sato
>Priority: Major
> Fix For: 3.0.0, 2.24.0
>
>
> In some edge case you may have a password=foo)+bar which you want to use
> as-is. The + sign gets escaped and therefore you need to use RAW syntax. But
> the closing paranthesis is used the first one. And the parser is not always
> smart enough. But this can be tricky to improve as you can use =v as will
> and the parser thinks its a new option etc.
> So instead we should add an alternative syntax such as RAW{} where we use
> curly brackets.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13073) Spring Web Services Security Vulnerability
Wildcat created CAMEL-13073: --- Summary: Spring Web Services Security Vulnerability Key: CAMEL-13073 URL: https://issues.apache.org/jira/browse/CAMEL-13073 Project: Camel Issue Type: Bug Components: camel-spring-ws Affects Versions: 2.23.0 Reporter: Wildcat Hi! Pivotal released a security advisory for spring-ws (1) which allows for XXE attacks. The current camel-master repository lists spring-ws with versions 2.4.2 and 3.0.4 which are both vulnerable. The vulnerability is rated critical. Is any timely update planned? 1) [https://pivotal.io/security/cve-2019-3773] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13073) Spring Web Services Security Vulnerability
[ https://issues.apache.org/jira/browse/CAMEL-13073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13073: Issue Type: Task (was: Bug) > Spring Web Services Security Vulnerability > -- > > Key: CAMEL-13073 > URL: https://issues.apache.org/jira/browse/CAMEL-13073 > Project: Camel > Issue Type: Task > Components: camel-spring-ws >Affects Versions: 2.23.0 >Reporter: Wildcat >Assignee: Andrea Cosentino >Priority: Major > > Hi! Pivotal released a security advisory for spring-ws (1) which allows for > XXE attacks. The current camel-master repository lists spring-ws with > versions 2.4.2 and 3.0.4 which are both vulnerable. > The vulnerability is rated critical. Is any timely update planned? > 1) [https://pivotal.io/security/cve-2019-3773] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13073) Spring Web Services Security Vulnerability
[ https://issues.apache.org/jira/browse/CAMEL-13073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744269#comment-16744269 ] Claus Ibsen commented on CAMEL-13073: - You can always yourself upgrade the spring JARs yourself and dont always have to wait for a new Camel release. > Spring Web Services Security Vulnerability > -- > > Key: CAMEL-13073 > URL: https://issues.apache.org/jira/browse/CAMEL-13073 > Project: Camel > Issue Type: Bug > Components: camel-spring-ws >Affects Versions: 2.23.0 >Reporter: Wildcat >Assignee: Andrea Cosentino >Priority: Major > > Hi! Pivotal released a security advisory for spring-ws (1) which allows for > XXE attacks. The current camel-master repository lists spring-ws with > versions 2.4.2 and 3.0.4 which are both vulnerable. > The vulnerability is rated critical. Is any timely update planned? > 1) [https://pivotal.io/security/cve-2019-3773] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13073) Spring Web Services Security Vulnerability
[ https://issues.apache.org/jira/browse/CAMEL-13073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13073: Assignee: Andrea Cosentino > Spring Web Services Security Vulnerability > -- > > Key: CAMEL-13073 > URL: https://issues.apache.org/jira/browse/CAMEL-13073 > Project: Camel > Issue Type: Bug > Components: camel-spring-ws >Affects Versions: 2.23.0 >Reporter: Wildcat >Assignee: Andrea Cosentino >Priority: Major > > Hi! Pivotal released a security advisory for spring-ws (1) which allows for > XXE attacks. The current camel-master repository lists spring-ws with > versions 2.4.2 and 3.0.4 which are both vulnerable. > The vulnerability is rated critical. Is any timely update planned? > 1) [https://pivotal.io/security/cve-2019-3773] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13072) In DefaultUnitOfWork:popRouteContext() avoid exception thrown
[
https://issues.apache.org/jira/browse/CAMEL-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13072:
Estimated Complexity: Novice (was: Unknown)
> In DefaultUnitOfWork:popRouteContext() avoid exception thrown
> --
>
> Key: CAMEL-13072
> URL: https://issues.apache.org/jira/browse/CAMEL-13072
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 2.21.4
>Reporter: Martin Lichtin
>Priority: Minor
>
> Instead of
> {noformat}
> public RouteContext popRouteContext() {
> try {
> return routeContextStack.pop();
> } catch (NoSuchElementException e) {
> // ignore and return null
> }
> return null;
> }
> {noformat}
> can just write
> {noformat}
> public RouteContext popRouteContext() {
> return routeContextStack.pollFirst();
> }
> {noformat}
> I understand the cost of an exception is low, but still it doesn't look nice
> to see zillions of exceptions in a flight recording caused by Camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13072) In DefaultUnitOfWork:popRouteContext() avoid exception thrown
[
https://issues.apache.org/jira/browse/CAMEL-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13072:
Component/s: camel-core
> In DefaultUnitOfWork:popRouteContext() avoid exception thrown
> --
>
> Key: CAMEL-13072
> URL: https://issues.apache.org/jira/browse/CAMEL-13072
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.21.4
>Reporter: Martin Lichtin
>Priority: Minor
> Fix For: 2.21.5, 2.22.3, 3.0.0, 2.23.2, 2.24.0
>
>
> Instead of
> {noformat}
> public RouteContext popRouteContext() {
> try {
> return routeContextStack.pop();
> } catch (NoSuchElementException e) {
> // ignore and return null
> }
> return null;
> }
> {noformat}
> can just write
> {noformat}
> public RouteContext popRouteContext() {
> return routeContextStack.pollFirst();
> }
> {noformat}
> I understand the cost of an exception is low, but still it doesn't look nice
> to see zillions of exceptions in a flight recording caused by Camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13072) In DefaultUnitOfWork:popRouteContext() avoid exception thrown
[
https://issues.apache.org/jira/browse/CAMEL-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744184#comment-16744184
]
Claus Ibsen commented on CAMEL-13072:
-
Yeah that would be better.
A github PR is welcome
> In DefaultUnitOfWork:popRouteContext() avoid exception thrown
> --
>
> Key: CAMEL-13072
> URL: https://issues.apache.org/jira/browse/CAMEL-13072
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 2.21.4
>Reporter: Martin Lichtin
>Priority: Minor
>
> Instead of
> {noformat}
> public RouteContext popRouteContext() {
> try {
> return routeContextStack.pop();
> } catch (NoSuchElementException e) {
> // ignore and return null
> }
> return null;
> }
> {noformat}
> can just write
> {noformat}
> public RouteContext popRouteContext() {
> return routeContextStack.pollFirst();
> }
> {noformat}
> I understand the cost of an exception is low, but still it doesn't look nice
> to see zillions of exceptions in a flight recording caused by Camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13072) In DefaultUnitOfWork:popRouteContext() avoid exception thrown
[
https://issues.apache.org/jira/browse/CAMEL-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13072:
Fix Version/s: 2.24.0
2.23.2
3.0.0
2.22.3
2.21.5
> In DefaultUnitOfWork:popRouteContext() avoid exception thrown
> --
>
> Key: CAMEL-13072
> URL: https://issues.apache.org/jira/browse/CAMEL-13072
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 2.21.4
>Reporter: Martin Lichtin
>Priority: Minor
> Fix For: 2.21.5, 2.22.3, 3.0.0, 2.23.2, 2.24.0
>
>
> Instead of
> {noformat}
> public RouteContext popRouteContext() {
> try {
> return routeContextStack.pop();
> } catch (NoSuchElementException e) {
> // ignore and return null
> }
> return null;
> }
> {noformat}
> can just write
> {noformat}
> public RouteContext popRouteContext() {
> return routeContextStack.pollFirst();
> }
> {noformat}
> I understand the cost of an exception is low, but still it doesn't look nice
> to see zillions of exceptions in a flight recording caused by Camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13072) In DefaultUnitOfWork:popRouteContext() avoid exception thrown
Martin Lichtin created CAMEL-13072:
--
Summary: In DefaultUnitOfWork:popRouteContext() avoid exception
thrown
Key: CAMEL-13072
URL: https://issues.apache.org/jira/browse/CAMEL-13072
Project: Camel
Issue Type: Improvement
Affects Versions: 2.21.4
Reporter: Martin Lichtin
Instead of
{noformat}
public RouteContext popRouteContext() {
try {
return routeContextStack.pop();
} catch (NoSuchElementException e) {
// ignore and return null
}
return null;
}
{noformat}
can just write
{noformat}
public RouteContext popRouteContext() {
return routeContextStack.pollFirst();
}
{noformat}
I understand the cost of an exception is low, but still it doesn't look nice to
see zillions of exceptions in a flight recording caused by Camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13066) camel-hystrix - Do not fallback on HystrixBadRequestException
[ https://issues.apache.org/jira/browse/CAMEL-13066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13066. - Resolution: Fixed Fix Version/s: 2.23.2 2.22.3 2.21.5 > camel-hystrix - Do not fallback on HystrixBadRequestException > - > > Key: CAMEL-13066 > URL: https://issues.apache.org/jira/browse/CAMEL-13066 > Project: Camel > Issue Type: Improvement > Components: camel-hystrix >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.21.5, 2.22.3, 3.0.0, 2.23.2, 2.24.0 > > > See SO > https://stackoverflow.com/questions/54151657/camel-hystrix-eip-ignoreexceptions-to-prevent-call-to-fallback > And the javadoc at > https://netflix.github.io/Hystrix/javadoc/com/netflix/hystrix/exception/HystrixBadRequestException.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13066) camel-hystrix - Do not fallback on HystrixBadRequestException
[ https://issues.apache.org/jira/browse/CAMEL-13066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-13066: --- Assignee: Claus Ibsen > camel-hystrix - Do not fallback on HystrixBadRequestException > - > > Key: CAMEL-13066 > URL: https://issues.apache.org/jira/browse/CAMEL-13066 > Project: Camel > Issue Type: Improvement > Components: camel-hystrix >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 2.24.0 > > > See SO > https://stackoverflow.com/questions/54151657/camel-hystrix-eip-ignoreexceptions-to-prevent-call-to-fallback > And the javadoc at > https://netflix.github.io/Hystrix/javadoc/com/netflix/hystrix/exception/HystrixBadRequestException.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13071) Elasticsearch rest component should support scroll api
[
https://issues.apache.org/jira/browse/CAMEL-13071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ludovic Boutros updated CAMEL-13071:
Description:
On some projects we need to fetch all results from Elasticsearch.
This is currently quite difficult.
Here is an example of usage that could be implemented:
{code:java|title=ElasticsearchRouter.java|borderStyle=solid}
from("direct:search")
.to("elasticsearch-rest://elasticsearch?operation=Search=twitter=tweet=true=3")
.split()
.body()
.streaming()
.to("mock:output")
.end();
{code}
Two new parameters could be used:
* useScroll: enable scroll usage
* scrollKeepAliveMs: time in ms during which elasticsearch will keep search
context alive
was:
On some project we need to fetch all results from Elasticsearch.
This is currently quite difficult.
Here is an example of usage that could be implemented:
{code:java|title=ElasticsearchRouter.java|borderStyle=solid}
from("direct:search")
.to("elasticsearch-rest://elasticsearch?operation=Search=twitter=tweet=true=3")
.split()
.body()
.streaming()
.to("mock:output")
.end();
{code}
Two new parameters could be used:
* useScroll: enable scroll usage
* scrollKeepAliveMs: time in ms during which elasticsearch will keep search
context alive
> Elasticsearch rest component should support scroll api
> --
>
> Key: CAMEL-13071
> URL: https://issues.apache.org/jira/browse/CAMEL-13071
> Project: Camel
> Issue Type: New Feature
> Components: camel-elasticsearch-rest
>Affects Versions: 2.23.0
>Reporter: Ludovic Boutros
>Assignee: Andrea Cosentino
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> On some projects we need to fetch all results from Elasticsearch.
> This is currently quite difficult.
> Here is an example of usage that could be implemented:
> {code:java|title=ElasticsearchRouter.java|borderStyle=solid}
> from("direct:search")
>
> .to("elasticsearch-rest://elasticsearch?operation=Search=twitter=tweet=true=3")
> .split()
> .body()
> .streaming()
> .to("mock:output")
> .end();
> {code}
> Two new parameters could be used:
> * useScroll: enable scroll usage
> * scrollKeepAliveMs: time in ms during which elasticsearch will keep search
> context alive
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13065) Add template support for MDN messages
[ https://issues.apache.org/jira/browse/CAMEL-13065?focusedWorklogId=185730=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-185730 ] ASF GitHub Bot logged work on CAMEL-13065: -- Author: ASF GitHub Bot Created on: 16/Jan/19 12:13 Start Date: 16/Jan/19 12:13 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #2709: CAMEL-13065 Added initial support for templating of MDN messages. URL: https://github.com/apache/camel/pull/2709 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 185730) Time Spent: 20m (was: 10m) > Add template support for MDN messages > - > > Key: CAMEL-13065 > URL: https://issues.apache.org/jira/browse/CAMEL-13065 > Project: Camel > Issue Type: Improvement > Components: camel-as2 >Reporter: William Collins >Assignee: William Collins >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The format of MDN messages are currently fixed and this improvement would > make them customizable via a user supplied velocity template. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13071) Elasticsearch rest component should support scroll api
[
https://issues.apache.org/jira/browse/CAMEL-13071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-13071:
Assignee: Andrea Cosentino
> Elasticsearch rest component should support scroll api
> --
>
> Key: CAMEL-13071
> URL: https://issues.apache.org/jira/browse/CAMEL-13071
> Project: Camel
> Issue Type: New Feature
> Components: camel-elasticsearch-rest
>Affects Versions: 2.23.0
>Reporter: Ludovic Boutros
>Assignee: Andrea Cosentino
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> On some project we need to fetch all results from Elasticsearch.
> This is currently quite difficult.
> Here is an example of usage that could be implemented:
> {code:java|title=ElasticsearchRouter.java|borderStyle=solid}
> from("direct:search")
>
> .to("elasticsearch-rest://elasticsearch?operation=Search=twitter=tweet=true=3")
> .split()
> .body()
> .streaming()
> .to("mock:output")
> .end();
> {code}
> Two new parameters could be used:
> * useScroll: enable scroll usage
> * scrollKeepAliveMs: time in ms during which elasticsearch will keep search
> context alive
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13071) Elasticsearch rest component should support scroll api
[
https://issues.apache.org/jira/browse/CAMEL-13071?focusedWorklogId=185696=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-185696
]
ASF GitHub Bot logged work on CAMEL-13071:
--
Author: ASF GitHub Bot
Created on: 16/Jan/19 11:28
Start Date: 16/Jan/19 11:28
Worklog Time Spent: 10m
Work Description: ludovic-boutros commented on pull request #2710:
CAMEL-13071: camel-elasticsearch-rest - Add scroll api support
URL: https://github.com/apache/camel/pull/2710
Hi all,
On some project we need to fetch all results from Elasticsearch.
This is currently quite difficult.
Here is an example of usage that could be implemented:
```java
from("direct:search")
.to("elasticsearch-rest://elasticsearch?operation=Search=twitter=tweet=true=3")
.split()
.body()
.streaming()
.to("mock:output")
.end();
```
Two new parameters could be used:
* useScroll: enable scroll usage
* scrollKeepAliveMs: time in ms during which elasticsearch will keep search
context alive
here is a proposal to implement Elasticsearch scroll API support.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 185696)
Time Spent: 10m
Remaining Estimate: 0h
> Elasticsearch rest component should support scroll api
> --
>
> Key: CAMEL-13071
> URL: https://issues.apache.org/jira/browse/CAMEL-13071
> Project: Camel
> Issue Type: New Feature
> Components: camel-elasticsearch-rest
>Affects Versions: 2.23.0
>Reporter: Ludovic Boutros
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> On some project we need to fetch all results from Elasticsearch.
> This is currently quite difficult.
> Here is an example of usage that could be implemented:
> {code:java|title=ElasticsearchRouter.java|borderStyle=solid}
> from("direct:search")
>
> .to("elasticsearch-rest://elasticsearch?operation=Search=twitter=tweet=true=3")
> .split()
> .body()
> .streaming()
> .to("mock:output")
> .end();
> {code}
> Two new parameters could be used:
> * useScroll: enable scroll usage
> * scrollKeepAliveMs: time in ms during which elasticsearch will keep search
> context alive
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13071) Elasticsearch rest component should support scroll api
Ludovic Boutros created CAMEL-13071:
---
Summary: Elasticsearch rest component should support scroll api
Key: CAMEL-13071
URL: https://issues.apache.org/jira/browse/CAMEL-13071
Project: Camel
Issue Type: New Feature
Components: camel-elasticsearch-rest
Affects Versions: 2.23.0
Reporter: Ludovic Boutros
On some project we need to fetch all results from Elasticsearch.
This is currently quite difficult.
Here is an example of usage that could be implemented:
{code:java|title=ElasticsearchRouter.java|borderStyle=solid}
from("direct:search")
.to("elasticsearch-rest://elasticsearch?operation=Search=twitter=tweet=true=3")
.split()
.body()
.streaming()
.to("mock:output")
.end();
{code}
Two new parameters could be used:
* useScroll: enable scroll usage
* scrollKeepAliveMs: time in ms during which elasticsearch will keep search
context alive
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13069) Display proper FTP reply message in case of transfer error
[
https://issues.apache.org/jira/browse/CAMEL-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743885#comment-16743885
]
Dmitry Volodin commented on CAMEL-13069:
[~Broser], you are welcome to submit PR on github. As idea, the exception
message can be current, but we can print detail message to the log with INFO
level.
> Display proper FTP reply message in case of transfer error
> --
>
> Key: CAMEL-13069
> URL: https://issues.apache.org/jira/browse/CAMEL-13069
> Project: Camel
> Issue Type: Improvement
> Components: camel-ftp
>Affects Versions: 2.23.0
> Environment: Any
>Reporter: Gerold Broser
>Priority: Major
> Labels: FTP, FTP-Reply
>
> When trying to transfer a file to an FTP server on an IBM mainframe that's
> too large for the allocated data set there I get the following log message:
> {code:java}
> ...
> 2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
> failed with: File operation failed: 125 Storing data set
> TEST.TRANSFER.FB80.TXT
> IOException caught while copying.. Code: 125
> ...{code}
> This is confusing since according to RFC 959 [reply codes {{1yz}} are
> {{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
> with:
> {quote}[{{125 Data connection already open; transfer
> starting.}}|https://tools.ietf.org/html/rfc959#page-41]
> {quote}
> being more informational than exceptional.
> Performing the same transfer manually with FileZilla and Windows 7's command
> line ftp client results in:
> FileZilla:
> {code:java}
> ...
> Command: STOR TRANSFER.FB80.TXT
> Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
> Response: 451-Error: Name=CkResults (Write) RC=-13
> Response: 451-System completion code and reason: B37-04
> Response: 451-Data set is out of space.
> Response: 451-Error (1013) closing the data set.
> Response: 451 Transfer aborted due to file error.
> ...{code}
> ftp:
> {code:java}
> ftp> send TRANSFER.FB80.TXT
> ---> PORT 10,100,113,251,254,235
> 200 Port request OK.
> ---> STOR TRANSFER.FB80.TXT
> 125 Storing data set TEST.TRANSFER.FB80.TXT
> 451-Error: Name=CkResults (Write) RC=-13
> 451-System completion code and reason: B37-04
> 451-Data set is out of space.
> 451-Error (1013) closing the data set.
> 451 Transfer aborted due to file error.
> ...{code}
> To get the real cause we can use Apache Commons Net's
> [{{FTP.getReply()}}|https://commons.apache.org/proper/commons-net/javadocs/api-3.6/org/apache/commons/net/ftp/FTP.html#getReply()]:
> {quote}Fetches a reply from the FTP server and returns the integer reply
> code. After calling this method, the actual reply text can be accessed from
> either calling getReplyString or getReplyStrings . Only use this method if
> you are implementing your own FTP client *or if you need to fetch a secondary
> response from the FTP server*.
> {quote}
> in the {{catch (IOException e)}} block in
> [{{FtpOperations.doStoreFile()}}|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L717]
> like:
> {code:java}
> ...
> catch (IOException e) {
> final IOException primary = new IOException(client.getReplyString());
> e = new IOException(e.getMessage(), primary);
> client.getReply(); // get secondary reply
> throw new GenericFileOperationFailedException(client.getReplyString(), e);
> }
> ...
> {code}
> which results in the following comprehensible stack trace in my test code:
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException:
> 451-Error: Name=CkResults (Write) RC=-13
> 451-System completion code and reason: B37-04
> 451-Data set is out of space.
> 451-Error (1013) closing the data set.
> 451 Transfer aborted due to file error.
> at my.FTPTransferTest.testMF_FTP((FTPTransferTest.java:74))
> ...
> Caused by: java.io.IOException: IOException caught while copying.
> at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:70)
> ... 24 more
> Caused by: java.io.IOException: 125 Storing data set TEST.TRANSFER.FB80.TXT
> at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:69)
> ... 24 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13070) sftp incorrectly catches files with filename in Windows-1251 encoding
Igor Piddubnyi created CAMEL-13070: -- Summary: sftp incorrectly catches files with filename in Windows-1251 encoding Key: CAMEL-13070 URL: https://issues.apache.org/jira/browse/CAMEL-13070 Project: Camel Issue Type: Improvement Components: camel-ftp Affects Versions: 2.21.4 Reporter: Igor Piddubnyi While processing files with Windows-1251 encoded filename I have not found ability to define filename encoding. sftp component does not support "ftpClientConfig.serverLanguageCode=de" option. Howevever underlying ChannelSftp has setFilenameEncoding method Could this be exposed as additional parameter? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13069) Display proper FTP reply message in case of transfer error
[
https://issues.apache.org/jira/browse/CAMEL-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerold Broser updated CAMEL-13069:
--
Description:
When trying to transfer a file to an FTP server on an IBM mainframe that's too
large for the allocated data set there I get the following log message:
{code:java}
...
2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
failed with: File operation failed: 125 Storing data set TEST.TRANSFER.FB80.TXT
IOException caught while copying.. Code: 125
...{code}
This is confusing since according to RFC 959 [reply codes {{1yz}} are
{{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
with:
{quote}[{{125 Data connection already open; transfer
starting.}}|https://tools.ietf.org/html/rfc959#page-41]
{quote}
being more informational than exceptional.
Performing the same transfer manually with FileZilla and Windows 7's command
line ftp client results in:
FileZilla:
{code:java}
...
Command:STOR TRANSFER.FB80.TXT
Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
Response: 451-Error: Name=CkResults (Write) RC=-13
Response: 451-System completion code and reason: B37-04
Response: 451-Data set is out of space.
Response: 451-Error (1013) closing the data set.
Response: 451 Transfer aborted due to file error.
...{code}
ftp:
{code:java}
ftp> send TRANSFER.FB80.TXT
---> PORT 10,100,113,251,254,235
200 Port request OK.
---> STOR TRANSFER.FB80.TXT
125 Storing data set TEST.TRANSFER.FB80.TXT
451-Error: Name=CkResults (Write) RC=-13
451-System completion code and reason: B37-04
451-Data set is out of space.
451-Error (1013) closing the data set.
451 Transfer aborted due to file error.
...{code}
To get the real cause we can use Apache Commons Net's
[{{FTP.getReply()}}|https://commons.apache.org/proper/commons-net/javadocs/api-3.6/org/apache/commons/net/ftp/FTP.html#getReply()]:
{quote}Fetches a reply from the FTP server and returns the integer reply code.
After calling this method, the actual reply text can be accessed from either
calling getReplyString or getReplyStrings . Only use this method if you are
implementing your own FTP client *or if you need to fetch a secondary response
from the FTP server*.
{quote}
in the {{catch (IOException e)}} block in
[{{FtpOperations.doStoreFile()}}|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L717]
like:
{code:java}
...
catch (IOException e) {
final IOException primary = new IOException(client.getReplyString());
e = new IOException(e.getMessage(), primary);
client.getReply(); // get secondary reply
throw new GenericFileOperationFailedException(client.getReplyString(), e);
}
...
{code}
which results in the following comprehensible stack trace in my test code:
{code:java}
org.apache.camel.component.file.GenericFileOperationFailedException: 451-Error:
Name=CkResults (Write) RC=-13
451-System completion code and reason: B37-04
451-Data set is out of space.
451-Error (1013) closing the data set.
451 Transfer aborted due to file error.
at my.FTPTransferTest.testMF_FTP((FTPTransferTest.java:74))
...
Caused by: java.io.IOException: IOException caught while copying.
at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:70)
... 24 more
Caused by: java.io.IOException: 125 Storing data set TEST.TRANSFER.FB80.TXT
at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:69)
... 24 more
{code}
was:
When trying to transfer a file to an FTP server on an IBM mainframe that's too
large for the allocated data set there I get the following log message:
{code:java}
...
2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
failed with: File operation failed: 125 Storing data set TEST.TRANSFER.FB80.TXT
IOException caught while copying.. Code: 125
...{code}
This is confusing since according to RFC 959 [reply codes {{1yz}} are
{{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
with:
{quote}[{{125 Data connection already open; transfer
starting.}}|https://tools.ietf.org/html/rfc959#page-41]
{quote}
being more informational than exceptional.
Performing the same transfer manually with FileZilla and Windows 7's command
line ftp client results in:
FileZilla:
{code:java}
...
Command:STOR TRANSFER.FB80.TXT
Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
Response: 451-Error: Name=CkResults (Write) RC=-13
Response: 451-System completion code and reason: B37-04
Response: 451-Data set is out of space.
Response: 451-Error (1013) closing the data set.
Response: 451 Transfer aborted due to file error.
...{code}
ftp:
{code:java}
ftp> send TRANSFER.FB80.TXT
---> PORT 10,100,113,251,254,235
200 Port request OK.
---> STOR TRANSFER.FB80.TXT
125 Storing data set TEST.TRANSFER.FB80.TXT
[jira] [Updated] (CAMEL-13069) Display proper FTP reply message in case of transfer error
[
https://issues.apache.org/jira/browse/CAMEL-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerold Broser updated CAMEL-13069:
--
Description:
When trying to transfer a file to an FTP server on an IBM mainframe that's too
large for the allocated data set there I get the following log message:
{code:java}
...
2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
failed with: File operation failed: 125 Storing data set TEST.TRANSFER.FB80.TXT
IOException caught while copying.. Code: 125
...{code}
This is confusing since according to RFC 959 [reply codes {{1yz}} are
{{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
with:
{quote}[{{125 Data connection already open; transfer
starting.}}|https://tools.ietf.org/html/rfc959#page-41]
{quote}
being more informational than exceptional.
Performing the same transfer manually with FileZilla and Windows 7's command
line ftp client results in:
FileZilla:
{code:java}
...
Command:STOR TRANSFER.FB80.TXT
Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
Response: 451-Error: Name=CkResults (Write) RC=-13
Response: 451-System completion code and reason: B37-04
Response: 451-Data set is out of space.
Response: 451-Error (1013) closing the data set.
Response: 451 Transfer aborted due to file error.
...{code}
ftp:
{code:java}
ftp> send TRANSFER.FB80.TXT
---> PORT 10,100,113,251,254,235
200 Port request OK.
---> STOR TRANSFER.FB80.TXT
125 Storing data set TEST.TRANSFER.FB80.TXT
451-Error: Name=CkResults (Write) RC=-13
451-System completion code and reason: B37-04
451-Data set is out of space.
451-Error (1013) closing the data set.
451 Transfer aborted due to file error.
...{code}
To get the real cause we can use Apache Commons Net's
[{{FTP.getReply()}}|https://commons.apache.org/proper/commons-net/javadocs/api-3.6/org/apache/commons/net/ftp/FTP.html#getReply()]:
{quote}Fetches a reply from the FTP server and returns the integer reply code.
After calling this method, the actual reply text can be accessed from either
calling getReplyString or getReplyStrings . Only use this method if you are
implementing your own FTP client *or if you need to fetch a secondary response
from the FTP server*.
{quote}
in the {{catch (IOException e)}} block in
[{{FtpOperations.doStoreFile()}}|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L717]
like:
{code:java}
...
catch (IOException e) {
final IOException primary = new IOException(ftp.getReplyString());
e = new IOException(e.getMessage(), primary);
ftp.getReply(); // get secondary reply
throw new GenericFileOperationFailedException(ftp.getReplyString(), e);
}
...
{code}
which results in the following comprehensible stack trace in my test code:
{code:java}
org.apache.camel.component.file.GenericFileOperationFailedException: 451-Error:
Name=CkResults (Write) RC=-13
451-System completion code and reason: B37-04
451-Data set is out of space.
451-Error (1013) closing the data set.
451 Transfer aborted due to file error.
at my.FTPTransferTest.testMF_FTP((FTPTransferTest.java:74))
...
Caused by: java.io.IOException: IOException caught while copying.
at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:70)
... 24 more
Caused by: java.io.IOException: 125 Storing data set TEST.TRANSFER.FB80.TXT
at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:69)
... 24 more
{code}
was:
When trying to transfer a file to an FTP server on an IBM mainframe that's too
large for the allocated data set there I get the following log message:
{code:java}
...
2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
failed with: File operation failed: 125 Storing data set TEST.TRANSFER.FB80.TXT
IOException caught while copying.. Code: 125
...{code}
This is confusing since according to RFC 959 [reply codes {{1yz}} are
{{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
with:
{quote}[{{125 Data connection already open; transfer
starting.}}|https://tools.ietf.org/html/rfc959#page-41]
{quote}
being more informational than exceptional.
Performing the same transfer manually with FileZilla and Windows 7's command
line ftp client results in:
FileZilla:
{code:java}
...
Command:STOR TRANSFER.FB80.TXT
Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
Response: 451-Error: Name=CkResults (Write) RC=-13
Response: 451-System completion code and reason: B37-04
Response: 451-Data set is out of space.
Response: 451-Error (1013) closing the data set.
Response: 451 Transfer aborted due to file error.
...{code}
ftp:
{code:java}
ftp> send TRANSFER.FB80.TXT
---> PORT 10,100,113,251,254,235
200 Port request OK.
---> STOR TRANSFER.FB80.TXT
125 Storing data set TEST.TRANSFER.FB80.TXT
451-Error:
[jira] [Commented] (CAMEL-13068) Remove dependency on ActiveMQ SNAPSHOT
[ https://issues.apache.org/jira/browse/CAMEL-13068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743827#comment-16743827 ] Andrea Cosentino commented on CAMEL-13068: -- We are now using 5.15.8 > Remove dependency on ActiveMQ SNAPSHOT > -- > > Key: CAMEL-13068 > URL: https://issues.apache.org/jira/browse/CAMEL-13068 > Project: Camel > Issue Type: Bug > Components: camel-activemq >Reporter: Thomas Diesler >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0 > > > Currently we have a reference to > [ActiveMQ-5.16.0-SNAPSHOT|https://github.com/apache/camel/blob/master/parent/pom.xml#L42] > in Camel-3.0.x, which prevents the WildFly-Camel build that is based on > Camel-3.0.x. We integrate the activemq component like > [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/camel-modules.xml#L60], > which has a dependency on the activemq module like > [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/activemq-modules.xml#L23]. > > Perhaps that 5.16.x snapshot can be released to some public repository. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13068) Remove dependency on ActiveMQ SNAPSHOT
[ https://issues.apache.org/jira/browse/CAMEL-13068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13068. -- Resolution: Fixed > Remove dependency on ActiveMQ SNAPSHOT > -- > > Key: CAMEL-13068 > URL: https://issues.apache.org/jira/browse/CAMEL-13068 > Project: Camel > Issue Type: Bug > Components: camel-activemq >Reporter: Thomas Diesler >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0 > > > Currently we have a reference to > [ActiveMQ-5.16.0-SNAPSHOT|https://github.com/apache/camel/blob/master/parent/pom.xml#L42] > in Camel-3.0.x, which prevents the WildFly-Camel build that is based on > Camel-3.0.x. We integrate the activemq component like > [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/camel-modules.xml#L60], > which has a dependency on the activemq module like > [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/activemq-modules.xml#L23]. > > Perhaps that 5.16.x snapshot can be released to some public repository. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13069) Display proper FTP reply message in case of transfer error
[
https://issues.apache.org/jira/browse/CAMEL-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerold Broser updated CAMEL-13069:
--
Description:
When trying to transfer a file to an FTP server on an IBM mainframe that's too
large for the allocated data set there I get the following log message:
{code:java}
...
2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
failed with: File operation failed: 125 Storing data set TEST.TRANSFER.FB80.TXT
IOException caught while copying.. Code: 125
...{code}
This is confusing since according to RFC 959 [reply codes {{1yz}} are
{{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
with:
{quote}[{{125 Data connection already open; transfer
starting.}}|https://tools.ietf.org/html/rfc959#page-41]
{quote}
being more informational than exceptional.
Performing the same transfer manually with FileZilla and Windows 7's command
line ftp client results in:
FileZilla:
{code:java}
...
Command:STOR TRANSFER.FB80.TXT
Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
Response: 451-Error: Name=CkResults (Write) RC=-13
Response: 451-System completion code and reason: B37-04
Response: 451-Data set is out of space.
Response: 451-Error (1013) closing the data set.
Response: 451 Transfer aborted due to file error.
...{code}
ftp:
{code:java}
ftp> send TRANSFER.FB80.TXT
---> PORT 10,100,113,251,254,235
200 Port request OK.
---> STOR TRANSFER.FB80.TXT
125 Storing data set TEST.TRANSFER.FB80.TXT
451-Error: Name=CkResults (Write) RC=-13
451-System completion code and reason: B37-04
451-Data set is out of space.
451-Error (1013) closing the data set.
451 Transfer aborted due to file error.
...{code}
To get the real cause we can use Apache Commons Net's
[{{FTP.getReply()}}|https://commons.apache.org/proper/commons-net/javadocs/api-3.6/org/apache/commons/net/ftp/FTP.html#getReply()]:
{quote}Fetches a reply from the FTP server and returns the integer reply code.
After calling this method, the actual reply text can be accessed from either
calling getReplyString or getReplyStrings . Only use this method if you are
implementing your own FTP client or if you need to fetch a secondary response
from the FTP server.
{quote}
in the {{catch (IOException e)}} block in
[{{FtpOperations.doStoreFile()}}|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L717]
like:
{code:java}
...
catch (IOException e) {
final IOException primary = new IOException(ftp.getReplyString());
e = new IOException(e.getMessage(), primary);
ftp.getReply(); // get secondary reply
throw new GenericFileOperationFailedException(ftp.getReplyString(), e);
}
...
{code}
which results in the following comprehensible stack trace in my test code:
{code:java}
org.apache.camel.component.file.GenericFileOperationFailedException: 451-Error:
Name=CkResults (Write) RC=-13
451-System completion code and reason: B37-04
451-Data set is out of space.
451-Error (1013) closing the data set.
451 Transfer aborted due to file error.
at my.FTPTransferTest.testMF_FTP((FTPTransferTest.java:74))
...
Caused by: java.io.IOException: IOException caught while copying.
at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:70)
... 24 more
Caused by: java.io.IOException: 125 Storing data set TEST.TRANSFER.FB80.TXT
at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:69)
... 24 more
{code}
was:
When trying to transfer a file to an FTP server on an IBM mainframe that's too
large for the allocated data set there I get the following log message:
{code}...
2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
failed with: File operation failed: 125 Storing data set TEST.TRANSFER.FB80.TXT
IOException caught while copying.. Code: 125
...{code}
This is confusing since according to RFC 959 [reply codes {{1yz}} are
{{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
with:
{quote}[{{125 Data connection already open; transfer
starting.}}|https://tools.ietf.org/html/rfc959#page-41]
{quote}
being more informational than exceptional.
Performing the same transfer manually with FileZilla and Windows 7's command
line ftp client results in:
FileZilla:
{code:java}
...
Command:STOR TRANSFER.FB80.TXT
Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
Response: 451-Error: Name=CkResults (Write) RC=-13
Response: 451-System completion code and reason: B37-04
Response: 451-Data set is out of space.
Response: 451-Error (1013) closing the data set.
Response: 451 Transfer aborted due to file error.
...{code}
ftp:
{code:java}
ftp> send TRANSFER.FB80.TXT
---> PORT 10,100,113,251,254,235
200 Port request OK.
---> STOR TRANSFER.FB80.TXT
125 Storing data set TEST.TRANSFER.FB80.TXT
451-Error:
[jira] [Updated] (CAMEL-13069) Display proper FTP reply message in case of transfer error
[
https://issues.apache.org/jira/browse/CAMEL-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerold Broser updated CAMEL-13069:
--
Description:
When trying to transfer a file to an FTP server on an IBM mainframe that's too
large for the allocated data set there I get the following log message:
{code}...
2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
failed with: File operation failed: 125 Storing data set TEST.TRANSFER.FB80.TXT
IOException caught while copying.. Code: 125
...{code}
This is confusing since according to RFC 959 [reply codes {{1yz}} are
{{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
with:
{quote}[{{125 Data connection already open; transfer
starting.}}|https://tools.ietf.org/html/rfc959#page-41]
{quote}
being more informational than exceptional.
Performing the same transfer manually with FileZilla and Windows 7's command
line ftp client results in:
FileZilla:
{code:java}
...
Command:STOR TRANSFER.FB80.TXT
Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
Response: 451-Error: Name=CkResults (Write) RC=-13
Response: 451-System completion code and reason: B37-04
Response: 451-Data set is out of space.
Response: 451-Error (1013) closing the data set.
Response: 451 Transfer aborted due to file error.
...{code}
ftp:
{code:java}
ftp> send TRANSFER.FB80.TXT
---> PORT 10,100,113,251,254,235
200 Port request OK.
---> STOR TRANSFER.FB80.TXT
125 Storing data set TEST.TRANSFER.FB80.TXT
451-Error: Name=CkResults (Write) RC=-13
451-System completion code and reason: B37-04
451-Data set is out of space.
451-Error (1013) closing the data set.
451 Transfer aborted due to file error.
...{code}
To get the real cause we can use Apache Commons Net's
[{{FTP.getReply()}}|https://commons.apache.org/proper/commons-net/javadocs/api-3.6/org/apache/commons/net/ftp/FTP.html#getReply()]:
{quote}Fetches a reply from the FTP server and returns the integer reply code.
After calling this method, the actual reply text can be accessed from either
calling getReplyString or getReplyStrings . Only use this method if you are
implementing your own FTP client or if you need to fetch a secondary response
from the FTP server.
{quote}
in the {{catch (IOException e)}} block in
[{{FtpOperations.doStoreFile()}}|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L717]:
{code:java}
...
catch (IOException e) {
final IOException primary = new IOException(ftp.getReplyString());
e = new IOException(e.getMessage(), primary);
ftp.getReply(); // get secondary reply
throw new GenericFileOperationFailedException(ftp.getReplyString(), e);
}
...
{code}
which results in the following comprehensible stack trace in my test code:
{code:java}
org.apache.camel.component.file.GenericFileOperationFailedException: 451-Error:
Name=CkResults (Write) RC=-13
451-System completion code and reason: B37-04
451-Data set is out of space.
451-Error (1013) closing the data set.
451 Transfer aborted due to file error.
at my.FTPTransferTest.testMF_FTP((FTPTransferTest.java:74))
...
Caused by: java.io.IOException: IOException caught while copying.
at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:70)
... 24 more
Caused by: java.io.IOException: 125 Storing data set TEST.TRANSFER.FB80.TXT
at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:69)
... 24 more
{code}
was:
When trying to transfer a file to an FTP server on an IBM mainframe that's too
large for the allocated data set there I get the following log message:
{quote}...
2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
failed with: File operation failed: 125 Storing data set TEST.TRANSFER.FB80.TXT
IOException caught while copying.. Code: 125
...
{quote}
This is confusing since according to RFC 959 [reply codes {{1yz}} are
{{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
with:
{quote}[{{125 Data connection already open; transfer
starting.}}|https://tools.ietf.org/html/rfc959#page-41]
{quote}
being more informational than exceptional.
Performing the same transfer manually with FileZilla and Windows 7's command
line ftp client results in:
FileZilla:
{code:java}
...
Command:STOR TRANSFER.FB80.TXT
Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
Response: 451-Error: Name=CkResults (Write) RC=-13
Response: 451-System completion code and reason: B37-04
Response: 451-Data set is out of space.
Response: 451-Error (1013) closing the data set.
Response: 451 Transfer aborted due to file error.
...{code}
ftp:
{code:java}
ftp> send TRANSFER.FB80.TXT
---> PORT 10,100,113,251,254,235
200 Port request OK.
---> STOR TRANSFER.FB80.TXT
125 Storing data set TEST.TRANSFER.FB80.TXT
451-Error: Name=CkResults
[jira] [Created] (CAMEL-13069) Display proper FTP reply message in case of transfer error
Gerold Broser created CAMEL-13069:
-
Summary: Display proper FTP reply message in case of transfer error
Key: CAMEL-13069
URL: https://issues.apache.org/jira/browse/CAMEL-13069
Project: Camel
Issue Type: Improvement
Components: camel-ftp
Affects Versions: 2.23.0
Environment: Any
Reporter: Gerold Broser
When trying to transfer a file to an FTP server on an IBM mainframe that's too
large for the allocated data set there I get the following log message:
{quote}...
2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
failed with: File operation failed: 125 Storing data set TEST.TRANSFER.FB80.TXT
IOException caught while copying.. Code: 125
...
{quote}
This is confusing since according to RFC 959 [reply codes {{1yz}} are
{{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
with:
{quote}[{{125 Data connection already open; transfer
starting.}}|https://tools.ietf.org/html/rfc959#page-41]
{quote}
being more informational than exceptional.
Performing the same transfer manually with FileZilla and Windows 7's command
line ftp client results in:
FileZilla:
{code:java}
...
Command:STOR TRANSFER.FB80.TXT
Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
Response: 451-Error: Name=CkResults (Write) RC=-13
Response: 451-System completion code and reason: B37-04
Response: 451-Data set is out of space.
Response: 451-Error (1013) closing the data set.
Response: 451 Transfer aborted due to file error.
...{code}
ftp:
{code:java}
ftp> send TRANSFER.FB80.TXT
---> PORT 10,100,113,251,254,235
200 Port request OK.
---> STOR TRANSFER.FB80.TXT
125 Storing data set TEST.TRANSFER.FB80.TXT
451-Error: Name=CkResults (Write) RC=-13
451-System completion code and reason: B37-04
451-Data set is out of space.
451-Error (1013) closing the data set.
451 Transfer aborted due to file error.
...{code}
To get the real cause we can use Apache Commons Net's
[{{FTP.getReply()}}|https://commons.apache.org/proper/commons-net/javadocs/api-3.6/org/apache/commons/net/ftp/FTP.html#getReply()]:
{quote}Fetches a reply from the FTP server and returns the integer reply code.
After calling this method, the actual reply text can be accessed from either
calling getReplyString or getReplyStrings . Only use this method if you are
implementing your own FTP client or if you need to fetch a secondary response
from the FTP server.
{quote}
in the {{catch (IOException e)}} block in
[{{FtpOperations.doStoreFile()}}|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L717]:
{code:java}
...
catch (IOException e) {
final IOException primary = new IOException(ftp.getReplyString());
e = new IOException(e.getMessage(), primary);
ftp.getReply(); // get secondary reply
throw new GenericFileOperationFailedException(ftp.getReplyString(), e);
}
...
{code}
which results in the following comprehensible stack trace in my test code:
{code:java}
org.apache.camel.component.file.GenericFileOperationFailedException: 451-Error:
Name=CkResults (Write) RC=-13
451-System completion code and reason: B37-04
451-Data set is out of space.
451-Error (1013) closing the data set.
451 Transfer aborted due to file error.
at my.FTPTransferTest.testMF_FTP((FTPTransferTest.java:74))
...
Caused by: java.io.IOException: IOException caught while copying.
at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:70)
... 24 more
Caused by: java.io.IOException: 125 Storing data set TEST.TRANSFER.FB80.TXT
at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:69)
... 24 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13067) camel3 - build system - Component level metadata is missing
[ https://issues.apache.org/jira/browse/CAMEL-13067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13067. - Resolution: Fixed > camel3 - build system - Component level metadata is missing > --- > > Key: CAMEL-13067 > URL: https://issues.apache.org/jira/browse/CAMEL-13067 > Project: Camel > Issue Type: Task > Components: build system >Affects Versions: 3.0.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > In 2.x we used to have component level metadata but in 3.x they are not there > For example testManagedCamelContextExplainComponentModel fails this test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13068) Remove dependency on ActiveMQ SNAPSHOT
[ https://issues.apache.org/jira/browse/CAMEL-13068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13068: Assignee: Andrea Cosentino > Remove dependency on ActiveMQ SNAPSHOT > -- > > Key: CAMEL-13068 > URL: https://issues.apache.org/jira/browse/CAMEL-13068 > Project: Camel > Issue Type: Bug > Components: camel-activemq >Reporter: Thomas Diesler >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0 > > > Currently we have a reference to > [ActiveMQ-5.16.0-SNAPSHOT|https://github.com/apache/camel/blob/master/parent/pom.xml#L42] > in Camel-3.0.x, which prevents the WildFly-Camel build that is based on > Camel-3.0.x. We integrate the activemq component like > [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/camel-modules.xml#L60], > which has a dependency on the activemq module like > [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/activemq-modules.xml#L23]. > > Perhaps that 5.16.x snapshot can be released to some public repository. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13068) Remove dependency on ActiveMQ SNAPSHOT
Thomas Diesler created CAMEL-13068: -- Summary: Remove dependency on ActiveMQ SNAPSHOT Key: CAMEL-13068 URL: https://issues.apache.org/jira/browse/CAMEL-13068 Project: Camel Issue Type: Bug Components: camel-activemq Reporter: Thomas Diesler Fix For: 3.0.0 Currently we have a reference to [ActiveMQ-5.16.0-SNAPSHOT|https://github.com/apache/camel/blob/master/parent/pom.xml#L42] in Camel-3.0.x, which prevents the WildFly-Camel build that is based on Camel-3.0.x. We integrate the activemq component like [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/camel-modules.xml#L60], which has a dependency on the activemq module like [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/activemq-modules.xml#L23]. Perhaps that 5.16.x snapshot can be released to some public redhat repository. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13050) camel atom URL with query parameters
[
https://issues.apache.org/jira/browse/CAMEL-13050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13050.
--
Resolution: Not A Problem
> camel atom URL with query parameters
>
>
> Key: CAMEL-13050
> URL: https://issues.apache.org/jira/browse/CAMEL-13050
> Project: Camel
> Issue Type: Bug
> Components: camel-atom
>Affects Versions: 2.23.0
>Reporter: Saravanakumar Selvaraj
>Assignee: Andrea Cosentino
>Priority: Minor
>
> We are using camel-atom component to poll an atom REST API. The REST URL has
> a query parameter. This is not working.
> For example,adding a query parameter for below consumer endpoint stops
> polling for feeds.
> {{atom://https://example.com/API/feed?param=value}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13050) camel atom URL with query parameters
[
https://issues.apache.org/jira/browse/CAMEL-13050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-13050:
Assignee: Andrea Cosentino
> camel atom URL with query parameters
>
>
> Key: CAMEL-13050
> URL: https://issues.apache.org/jira/browse/CAMEL-13050
> Project: Camel
> Issue Type: Bug
> Components: camel-atom
>Affects Versions: 2.23.0
>Reporter: Saravanakumar Selvaraj
>Assignee: Andrea Cosentino
>Priority: Minor
>
> We are using camel-atom component to poll an atom REST API. The REST URL has
> a query parameter. This is not working.
> For example,adding a query parameter for below consumer endpoint stops
> polling for feeds.
> {{atom://https://example.com/API/feed?param=value}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13068) Remove dependency on ActiveMQ SNAPSHOT
[ https://issues.apache.org/jira/browse/CAMEL-13068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13068: - Description: Currently we have a reference to [ActiveMQ-5.16.0-SNAPSHOT|https://github.com/apache/camel/blob/master/parent/pom.xml#L42] in Camel-3.0.x, which prevents the WildFly-Camel build that is based on Camel-3.0.x. We integrate the activemq component like [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/camel-modules.xml#L60], which has a dependency on the activemq module like [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/activemq-modules.xml#L23]. Perhaps that 5.16.x snapshot can be released to some public repository. was: Currently we have a reference to [ActiveMQ-5.16.0-SNAPSHOT|https://github.com/apache/camel/blob/master/parent/pom.xml#L42] in Camel-3.0.x, which prevents the WildFly-Camel build that is based on Camel-3.0.x. We integrate the activemq component like [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/camel-modules.xml#L60], which has a dependency on the activemq module like [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/activemq-modules.xml#L23]. Perhaps that 5.16.x snapshot can be released to some public redhat repository. > Remove dependency on ActiveMQ SNAPSHOT > -- > > Key: CAMEL-13068 > URL: https://issues.apache.org/jira/browse/CAMEL-13068 > Project: Camel > Issue Type: Bug > Components: camel-activemq >Reporter: Thomas Diesler >Priority: Major > Fix For: 3.0.0 > > > Currently we have a reference to > [ActiveMQ-5.16.0-SNAPSHOT|https://github.com/apache/camel/blob/master/parent/pom.xml#L42] > in Camel-3.0.x, which prevents the WildFly-Camel build that is based on > Camel-3.0.x. We integrate the activemq component like > [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/camel-modules.xml#L60], > which has a dependency on the activemq module like > [this|https://github.com/wildfly-extras/wildfly-camel/blob/master/feature/modules/etc/smartics/activemq-modules.xml#L23]. > > Perhaps that 5.16.x snapshot can be released to some public repository. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
