[jira] [Assigned] (CAMEL-6707) Asynchronous Mode In camel-servlet, Servlet 3.0 AsyncContext
[ https://issues.apache.org/jira/browse/CAMEL-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-6707: -- Assignee: Claus Ibsen > Asynchronous Mode In camel-servlet, Servlet 3.0 AsyncContext > > > Key: CAMEL-6707 > URL: https://issues.apache.org/jira/browse/CAMEL-6707 > Project: Camel > Issue Type: Improvement > Components: camel-http, camel-servlet >Affects Versions: 2.13.0 >Reporter: Jörg Schubert >Assignee: Claus Ibsen > Fix For: 2.18.0 > > > My Goal is routing larger amounts of HTTP-Traffic > CamelServlet is blocking the HTTP-thread while message is being processed. > I'm currently preparing a patch which uses AsyncContext and starts processor > in async mode. Hope that will improve throughput. > The async feature is switchable by parameter. > I will attach a patch as soon as it works. > There is one point: To avoid conflicts geronimo-servlet_2.5_spec must be > replaced by geronimo-servlet_3.0_spec in parent pom. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-9900) camel-jms - provide option for MessageListenerContainer for reply managers to stop quicker when CamelContext is stopping
Jonathan Anstey created CAMEL-9900:
--
Summary: camel-jms - provide option for MessageListenerContainer
for reply managers to stop quicker when CamelContext is stopping
Key: CAMEL-9900
URL: https://issues.apache.org/jira/browse/CAMEL-9900
Project: Camel
Issue Type: Improvement
Reporter: Jonathan Anstey
Assignee: Jonathan Anstey
Fix For: 2.17.1, 2.18.0
CAMEL-7667 included a fix for the DMLC used in JMS consumers to stop quickly if
the CameContext is already shutting down. This helps avoid spring-jms getting
into a bad state with a null sharedConnection which has a telling stack like:
{code}
2014-08-07 10:33:42,975 [sonnel.records]] ERROR ultJmsMessageListenerContainer
- Could not refresh JMS Connection for destination 'personnel.records' -
retrying in 5000 ms. Cause: null
java.lang.NullPointerException
at
org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:392)
at
org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:885)
at
org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:861)
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1012)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{code}
This can also occur in the DMLC used for request-reply messaging. We should
provide an option for this to be enabled because usually this is not an issue
and you don't mind waiting for a while for replies to come in.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-9899) camel-rx - Use a worker pool for tasks such as stopping consumers
[ https://issues.apache.org/jira/browse/CAMEL-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9899. Resolution: Fixed > camel-rx - Use a worker pool for tasks such as stopping consumers > - > > Key: CAMEL-9899 > URL: https://issues.apache.org/jira/browse/CAMEL-9899 > Project: Camel > Issue Type: Improvement > Components: camel-rx >Affects Versions: 2.17.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.17.1, 2.18.0 > > > // a worker pool for running tasks such as stopping consumers which > should not use the event loop > // thread from rx-java but use our own thread to process such tasks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-9899) camel-rx - Use a worker pool for tasks such as stopping consumers
Claus Ibsen created CAMEL-9899: -- Summary: camel-rx - Use a worker pool for tasks such as stopping consumers Key: CAMEL-9899 URL: https://issues.apache.org/jira/browse/CAMEL-9899 Project: Camel Issue Type: Improvement Components: camel-rx Affects Versions: 2.17.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.17.1, 2.18.0 // a worker pool for running tasks such as stopping consumers which should not use the event loop // thread from rx-java but use our own thread to process such tasks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-9898) SimpleBuilder throws NullPointerException when replacing string using regexAll method and the regex contains }
[
https://issues.apache.org/jira/browse/CAMEL-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9898.
Resolution: Fixed
Fix Version/s: 2.18.0
> SimpleBuilder throws NullPointerException when replacing string using
> regexAll method and the regex contains }
> --
>
> Key: CAMEL-9898
> URL: https://issues.apache.org/jira/browse/CAMEL-9898
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.17.0
>Reporter: Lefteris Tsallas
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.18.0
>
>
>
> Add this unit test in org.apache.camel.builder.SimpleBuilderTest to reproduce
> the issue. Only fails when the regex contains }
> {code}
> public void testRegexAllWithPlaceHolders() {
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/(id)/activate");
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\(id\\)\",\"12\")}").evaluate(exchange,String.class));
> //passes when contains { only
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\",\"12\")}").evaluate(exchange,String.class));
> String replaced =
> "http://some/rest/api/{id}/activate".replaceAll("\\{id\\}","12");
> assertEquals( "http://some/rest/api/12/activate;, replaced);
> /// But throws throws NullPointerException when regexALl inside a
> simple expression
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id}/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\\}\",\"12\")}").evaluate(exchange,String.class));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9898) SimpleBuilder throws NullPointerException when replacing string using regexAll method and the regex contains }
[
https://issues.apache.org/jira/browse/CAMEL-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252461#comment-15252461
]
Claus Ibsen commented on CAMEL-9898:
We can improve the parser to support escaping curly-bracket-end so its not
mistakenly taken as a function end marker.
> SimpleBuilder throws NullPointerException when replacing string using
> regexAll method and the regex contains }
> --
>
> Key: CAMEL-9898
> URL: https://issues.apache.org/jira/browse/CAMEL-9898
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.17.0
>Reporter: Lefteris Tsallas
>Assignee: Claus Ibsen
>Priority: Minor
>
>
> Add this unit test in org.apache.camel.builder.SimpleBuilderTest to reproduce
> the issue. Only fails when the regex contains }
> {code}
> public void testRegexAllWithPlaceHolders() {
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/(id)/activate");
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\(id\\)\",\"12\")}").evaluate(exchange,String.class));
> //passes when contains { only
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\",\"12\")}").evaluate(exchange,String.class));
> String replaced =
> "http://some/rest/api/{id}/activate".replaceAll("\\{id\\}","12");
> assertEquals( "http://some/rest/api/12/activate;, replaced);
> /// But throws throws NullPointerException when regexALl inside a
> simple expression
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id}/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\\}\",\"12\")}").evaluate(exchange,String.class));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-8637) Upgrade Jetty version to 9.x in Camel-CometD
[ https://issues.apache.org/jira/browse/CAMEL-8637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-8637. - Resolution: Fixed > Upgrade Jetty version to 9.x in Camel-CometD > - > > Key: CAMEL-8637 > URL: https://issues.apache.org/jira/browse/CAMEL-8637 > Project: Camel > Issue Type: Task > Components: camel-cometd >Reporter: Willem Jiang >Assignee: Andrea Cosentino > Fix For: 2.18.0 > > > It's time to upgrade the Jetty version to 9.x as the 8.x is EOL for a while. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-9898) SimpleBuilder throws NullPointerException when replacing string using regexAll method and the regex contains }
[
https://issues.apache.org/jira/browse/CAMEL-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-9898:
--
Assignee: Claus Ibsen
> SimpleBuilder throws NullPointerException when replacing string using
> regexAll method and the regex contains }
> --
>
> Key: CAMEL-9898
> URL: https://issues.apache.org/jira/browse/CAMEL-9898
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.17.0
>Reporter: Lefteris Tsallas
>Assignee: Claus Ibsen
>Priority: Minor
>
>
> Add this unit test in org.apache.camel.builder.SimpleBuilderTest to reproduce
> the issue. Only fails when the regex contains }
> {code}
> public void testRegexAllWithPlaceHolders() {
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/(id)/activate");
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\(id\\)\",\"12\")}").evaluate(exchange,String.class));
> //passes when contains { only
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\",\"12\")}").evaluate(exchange,String.class));
> String replaced =
> "http://some/rest/api/{id}/activate".replaceAll("\\{id\\}","12");
> assertEquals( "http://some/rest/api/12/activate;, replaced);
> /// But throws throws NullPointerException when regexALl inside a
> simple expression
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id}/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\\}\",\"12\")}").evaluate(exchange,String.class));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (CAMEL-9894) RXCamel is not releasing the ActiveMQ connection once the subscription is complete
[
https://issues.apache.org/jira/browse/CAMEL-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun updated CAMEL-9894:
Comment: was deleted
(was: I feel its an issue with Camel.)
> RXCamel is not releasing the ActiveMQ connection once the subscription is
> complete
> --
>
> Key: CAMEL-9894
> URL: https://issues.apache.org/jira/browse/CAMEL-9894
> Project: Camel
> Issue Type: Bug
> Components: camel-rx
>Affects Versions: 2.17.0
>Reporter: Arun
>Assignee: Claus Ibsen
>Priority: Critical
>
> I am using camel-rx to observe some messages from Active MQ. After I complete
> the subscription I am getting onCompleted() event also. But If I look in
> Active MQ console, I can still see the consumer live.
> I feel Is it an issue with camel. How to release this connection once
> subscription is over?
> Code :
> ReactiveCamel rx = new ReactiveCamel(camel);
>
> Observable observable1 =
> rx.toObservable("activemq:queue:Output Queue -
> 01?selector=JMSCorrelationID%3D'"+ uuid + "' AND eventType%3D'cust_msg'");
>
> observable1.first().subscribe(new Subscriber()
> {
>
> // methods here
>
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9894) RXCamel is not releasing the ActiveMQ connection once the subscription is complete
[
https://issues.apache.org/jira/browse/CAMEL-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252036#comment-15252036
]
Arun commented on CAMEL-9894:
-
OK. Got it
> RXCamel is not releasing the ActiveMQ connection once the subscription is
> complete
> --
>
> Key: CAMEL-9894
> URL: https://issues.apache.org/jira/browse/CAMEL-9894
> Project: Camel
> Issue Type: Bug
> Components: camel-rx
>Affects Versions: 2.17.0
>Reporter: Arun
>Assignee: Claus Ibsen
>Priority: Critical
>
> I am using camel-rx to observe some messages from Active MQ. After I complete
> the subscription I am getting onCompleted() event also. But If I look in
> Active MQ console, I can still see the consumer live.
> I feel Is it an issue with camel. How to release this connection once
> subscription is over?
> Code :
> ReactiveCamel rx = new ReactiveCamel(camel);
>
> Observable observable1 =
> rx.toObservable("activemq:queue:Output Queue -
> 01?selector=JMSCorrelationID%3D'"+ uuid + "' AND eventType%3D'cust_msg'");
>
> observable1.first().subscribe(new Subscriber()
> {
>
> // methods here
>
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-9894) RXCamel is not releasing the ActiveMQ connection once the subscription is complete
[
https://issues.apache.org/jira/browse/CAMEL-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9894.
Resolution: Invalid
Please do not reopen tickets.
Things are to be discussed on the user forum / mailing list first. We cannot
have people open 1s of issue tracker at their will.
> RXCamel is not releasing the ActiveMQ connection once the subscription is
> complete
> --
>
> Key: CAMEL-9894
> URL: https://issues.apache.org/jira/browse/CAMEL-9894
> Project: Camel
> Issue Type: Bug
> Components: camel-rx
>Affects Versions: 2.17.0
>Reporter: Arun
>Assignee: Claus Ibsen
>Priority: Critical
>
> I am using camel-rx to observe some messages from Active MQ. After I complete
> the subscription I am getting onCompleted() event also. But If I look in
> Active MQ console, I can still see the consumer live.
> I feel Is it an issue with camel. How to release this connection once
> subscription is over?
> Code :
> ReactiveCamel rx = new ReactiveCamel(camel);
>
> Observable observable1 =
> rx.toObservable("activemq:queue:Output Queue -
> 01?selector=JMSCorrelationID%3D'"+ uuid + "' AND eventType%3D'cust_msg'");
>
> observable1.first().subscribe(new Subscriber()
> {
>
> // methods here
>
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (CAMEL-9894) RXCamel is not releasing the ActiveMQ connection once the subscription is complete
[
https://issues.apache.org/jira/browse/CAMEL-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun reopened CAMEL-9894:
-
I feel its an issue with Camel.
> RXCamel is not releasing the ActiveMQ connection once the subscription is
> complete
> --
>
> Key: CAMEL-9894
> URL: https://issues.apache.org/jira/browse/CAMEL-9894
> Project: Camel
> Issue Type: Bug
> Components: camel-rx
>Affects Versions: 2.17.0
>Reporter: Arun
>Assignee: Claus Ibsen
>Priority: Critical
>
> I am using camel-rx to observe some messages from Active MQ. After I complete
> the subscription I am getting onCompleted() event also. But If I look in
> Active MQ console, I can still see the consumer live.
> I feel Is it an issue with camel. How to release this connection once
> subscription is over?
> Code :
> ReactiveCamel rx = new ReactiveCamel(camel);
>
> Observable observable1 =
> rx.toObservable("activemq:queue:Output Queue -
> 01?selector=JMSCorrelationID%3D'"+ uuid + "' AND eventType%3D'cust_msg'");
>
> observable1.first().subscribe(new Subscriber()
> {
>
> // methods here
>
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9894) RXCamel is not releasing the ActiveMQ connection once the subscription is complete
[
https://issues.apache.org/jira/browse/CAMEL-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun updated CAMEL-9894:
Description:
I am using camel-rx to observe some messages from Active MQ. After I complete
the subscription I am getting onCompleted() event also. But If I look in Active
MQ console, I can still see the consumer live.
I feel Is it an issue with camel. How to release this connection once
subscription is over?
Code :
ReactiveCamel rx = new ReactiveCamel(camel);
Observable observable1 =
rx.toObservable("activemq:queue:Output Queue -
01?selector=JMSCorrelationID%3D'"+ uuid + "' AND eventType%3D'cust_msg'");
observable1.first().subscribe(new Subscriber()
{
// methods here
}
was:
I am using camel-rx to observe some messages from Active MQ. After I complete
the subscription I am getting onCompleted() event also. But If I look in Active
MQ console, I can still see the consumer live. How to release this connection
once subscription is over?
Code :
ReactiveCamel rx = new ReactiveCamel(camel);
Observable observable1 =
rx.toObservable("activemq:queue:Output Queue -
01?selector=JMSCorrelationID%3D'"+ uuid + "' AND eventType%3D'cust_msg'");
observable1.first().subscribe(new Subscriber()
{
// methods here
}
> RXCamel is not releasing the ActiveMQ connection once the subscription is
> complete
> --
>
> Key: CAMEL-9894
> URL: https://issues.apache.org/jira/browse/CAMEL-9894
> Project: Camel
> Issue Type: Bug
> Components: camel-rx
>Affects Versions: 2.17.0
>Reporter: Arun
>Assignee: Claus Ibsen
>Priority: Critical
>
> I am using camel-rx to observe some messages from Active MQ. After I complete
> the subscription I am getting onCompleted() event also. But If I look in
> Active MQ console, I can still see the consumer live.
> I feel Is it an issue with camel. How to release this connection once
> subscription is over?
> Code :
> ReactiveCamel rx = new ReactiveCamel(camel);
>
> Observable observable1 =
> rx.toObservable("activemq:queue:Output Queue -
> 01?selector=JMSCorrelationID%3D'"+ uuid + "' AND eventType%3D'cust_msg'");
>
> observable1.first().subscribe(new Subscriber()
> {
>
> // methods here
>
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9895) Setup a by default password to access the spring boot ssh server
[
https://issues.apache.org/jira/browse/CAMEL-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-9895:
---
Issue Type: Improvement (was: Bug)
> Setup a by default password to access the spring boot ssh server
>
>
> Key: CAMEL-9895
> URL: https://issues.apache.org/jira/browse/CAMEL-9895
> Project: Camel
> Issue Type: Improvement
> Components: examples
>Reporter: Charles Moulliard
>Assignee: Charles Moulliard
> Fix For: 2.18.0
>
>
> Setup a by default password to access the spring boot ssh server in order to
> simplify the access to the SSH server as it is not so easy to get the random
> generated password
> {code}
> Parameter to be added within the application.yml file
> shell.auth.simple.user.password: password
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-9892) Aggregator completionPredicate does not support a more complex block with scala DSL
[ https://issues.apache.org/jira/browse/CAMEL-9892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9892. Resolution: Fixed Assignee: Claus Ibsen Fix Version/s: 2.18.0 Thanks > Aggregator completionPredicate does not support a more complex block with > scala DSL > --- > > Key: CAMEL-9892 > URL: https://issues.apache.org/jira/browse/CAMEL-9892 > Project: Camel > Issue Type: Improvement > Components: camel-scala >Affects Versions: 2.17.0 >Reporter: Bob Gaudaen >Assignee: Claus Ibsen > Fix For: 2.18.0 > > > Will provide pull request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-9892) Aggregator completionPredicate does not support a more complex block with scala DSL
[ https://issues.apache.org/jira/browse/CAMEL-9892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-9892: --- Issue Type: Improvement (was: Bug) > Aggregator completionPredicate does not support a more complex block with > scala DSL > --- > > Key: CAMEL-9892 > URL: https://issues.apache.org/jira/browse/CAMEL-9892 > Project: Camel > Issue Type: Improvement > Components: camel-scala >Affects Versions: 2.17.0 >Reporter: Bob Gaudaen > > Will provide pull request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-9894) RXCamel is not releasing the ActiveMQ connection once the subscription is complete
[
https://issues.apache.org/jira/browse/CAMEL-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251990#comment-15251990
]
Arun commented on CAMEL-9894:
-
But Ideally it should release the connection. Right? Is it an issue with Camel
or is it supposed to behave like that?
I mean if onCompleted() is getting called the consumer should release the
connection. but it is not getting released
> RXCamel is not releasing the ActiveMQ connection once the subscription is
> complete
> --
>
> Key: CAMEL-9894
> URL: https://issues.apache.org/jira/browse/CAMEL-9894
> Project: Camel
> Issue Type: Bug
> Components: camel-rx
>Affects Versions: 2.17.0
>Reporter: Arun
>Assignee: Claus Ibsen
>Priority: Critical
>
> I am using camel-rx to observe some messages from Active MQ. After I complete
> the subscription I am getting onCompleted() event also. But If I look in
> Active MQ console, I can still see the consumer live. How to release this
> connection once subscription is over?
> Code :
> ReactiveCamel rx = new ReactiveCamel(camel);
>
> Observable observable1 =
> rx.toObservable("activemq:queue:Output Queue -
> 01?selector=JMSCorrelationID%3D'"+ uuid + "' AND eventType%3D'cust_msg'");
>
> observable1.first().subscribe(new Subscriber()
> {
>
> // methods here
>
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9898) SimpleBuilder throws NullPointerException when replacing string using regexAll method and the regex contains }
[
https://issues.apache.org/jira/browse/CAMEL-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251906#comment-15251906
]
Lefteris Tsallas commented on CAMEL-9898:
-
Sure there are alternatives, but I thought It would be good to report it. I
always prefer the simple language, when it's possible.
> SimpleBuilder throws NullPointerException when replacing string using
> regexAll method and the regex contains }
> --
>
> Key: CAMEL-9898
> URL: https://issues.apache.org/jira/browse/CAMEL-9898
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.17.0
>Reporter: Lefteris Tsallas
>Priority: Minor
>
>
> Add this unit test in org.apache.camel.builder.SimpleBuilderTest to reproduce
> the issue. Only fails when the regex contains }
> {code}
> public void testRegexAllWithPlaceHolders() {
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/(id)/activate");
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\(id\\)\",\"12\")}").evaluate(exchange,String.class));
> //passes when contains { only
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\",\"12\")}").evaluate(exchange,String.class));
> String replaced =
> "http://some/rest/api/{id}/activate".replaceAll("\\{id\\}","12");
> assertEquals( "http://some/rest/api/12/activate;, replaced);
> /// But throws throws NullPointerException when regexALl inside a
> simple expression
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id}/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\\}\",\"12\")}").evaluate(exchange,String.class));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9896) Deadletter Failure processor is invoked even if error handling strategy defines to continue routing
[ https://issues.apache.org/jira/browse/CAMEL-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-9896: --- Patch Info: (was: Patch Available) > Deadletter Failure processor is invoked even if error handling strategy > defines to continue routing > --- > > Key: CAMEL-9896 > URL: https://issues.apache.org/jira/browse/CAMEL-9896 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.15.6 > Environment: stage >Reporter: Nikhil Kumar >Priority: Minor > > When a DeadLetterChannel is used as context scoped error handling strategy > with FailureProcessor set and a route scoped error handling strategy is > defined to continue routing in case of certain exception classes, then it is > observed that even in case of exceptions which belong to exceptions defined > in OnException clause, the dead letter's failure processor is still > triggered. > A test case to simulate this behaviour is pasted. > http://pastebin.com/raw/cfQhsJj0 - contains test case. > http://pastebin.com/raw/K6wZc9Yh - test output -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-9896) Deadletter Failure processor is invoked even if error handling strategy defines to continue routing
[ https://issues.apache.org/jira/browse/CAMEL-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-9896: --- Priority: Minor (was: Critical) > Deadletter Failure processor is invoked even if error handling strategy > defines to continue routing > --- > > Key: CAMEL-9896 > URL: https://issues.apache.org/jira/browse/CAMEL-9896 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.15.6 > Environment: stage >Reporter: Nikhil Kumar >Priority: Minor > > When a DeadLetterChannel is used as context scoped error handling strategy > with FailureProcessor set and a route scoped error handling strategy is > defined to continue routing in case of certain exception classes, then it is > observed that even in case of exceptions which belong to exceptions defined > in OnException clause, the dead letter's failure processor is still > triggered. > A test case to simulate this behaviour is pasted. > http://pastebin.com/raw/cfQhsJj0 - contains test case. > http://pastebin.com/raw/K6wZc9Yh - test output -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-9898) SimpleBuilder throws NullPointerException when replacing string using regexAll method and the regex contains }
[
https://issues.apache.org/jira/browse/CAMEL-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251889#comment-15251889
]
Claus Ibsen commented on CAMEL-9898:
The simple parser sounds like is not detecting the closing } is in the quote
and thus not the paired close } for the command itself.
> SimpleBuilder throws NullPointerException when replacing string using
> regexAll method and the regex contains }
> --
>
> Key: CAMEL-9898
> URL: https://issues.apache.org/jira/browse/CAMEL-9898
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.17.0
>Reporter: Lefteris Tsallas
>Priority: Minor
>
>
> Add this unit test in org.apache.camel.builder.SimpleBuilderTest to reproduce
> the issue. Only fails when the regex contains }
> {code}
> public void testRegexAllWithPlaceHolders() {
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/(id)/activate");
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\(id\\)\",\"12\")}").evaluate(exchange,String.class));
> //passes when contains { only
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\",\"12\")}").evaluate(exchange,String.class));
> String replaced =
> "http://some/rest/api/{id}/activate".replaceAll("\\{id\\}","12");
> assertEquals( "http://some/rest/api/12/activate;, replaced);
> /// But throws throws NullPointerException when regexALl inside a
> simple expression
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id}/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\\}\",\"12\")}").evaluate(exchange,String.class));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9898) SimpleBuilder throws NullPointerException when replacing string using regexAll method and the regex contains }
[
https://issues.apache.org/jira/browse/CAMEL-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251887#comment-15251887
]
Claus Ibsen commented on CAMEL-9898:
You can use groovy or mvel to call such methods.
> SimpleBuilder throws NullPointerException when replacing string using
> regexAll method and the regex contains }
> --
>
> Key: CAMEL-9898
> URL: https://issues.apache.org/jira/browse/CAMEL-9898
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.17.0
>Reporter: Lefteris Tsallas
>Priority: Minor
>
>
> Add this unit test in org.apache.camel.builder.SimpleBuilderTest to reproduce
> the issue. Only fails when the regex contains }
> {code}
> public void testRegexAllWithPlaceHolders() {
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/(id)/activate");
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\(id\\)\",\"12\")}").evaluate(exchange,String.class));
> //passes when contains { only
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\",\"12\")}").evaluate(exchange,String.class));
> String replaced =
> "http://some/rest/api/{id}/activate".replaceAll("\\{id\\}","12");
> assertEquals( "http://some/rest/api/12/activate;, replaced);
> /// But throws throws NullPointerException when regexALl inside a
> simple expression
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id}/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\\}\",\"12\")}").evaluate(exchange,String.class));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-9894) RXCamel is not releasing the ActiveMQ connection once the subscription is complete
[
https://issues.apache.org/jira/browse/CAMEL-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9894.
Resolution: Invalid
Assignee: Claus Ibsen
Use the mailing list / user forum to get help
> RXCamel is not releasing the ActiveMQ connection once the subscription is
> complete
> --
>
> Key: CAMEL-9894
> URL: https://issues.apache.org/jira/browse/CAMEL-9894
> Project: Camel
> Issue Type: Bug
> Components: camel-rx
>Affects Versions: 2.17.0
>Reporter: Arun
>Assignee: Claus Ibsen
>Priority: Critical
>
> I am using camel-rx to observe some messages from Active MQ. After I complete
> the subscription I am getting onCompleted() event also. But If I look in
> Active MQ console, I can still see the consumer live. How to release this
> connection once subscription is over?
> Code :
> ReactiveCamel rx = new ReactiveCamel(camel);
>
> Observable observable1 =
> rx.toObservable("activemq:queue:Output Queue -
> 01?selector=JMSCorrelationID%3D'"+ uuid + "' AND eventType%3D'cust_msg'");
>
> observable1.first().subscribe(new Subscriber()
> {
>
> // methods here
>
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9894) RXCamel is not releasing the ActiveMQ connection once the subscription is complete
[
https://issues.apache.org/jira/browse/CAMEL-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun updated CAMEL-9894:
Priority: Critical (was: Major)
> RXCamel is not releasing the ActiveMQ connection once the subscription is
> complete
> --
>
> Key: CAMEL-9894
> URL: https://issues.apache.org/jira/browse/CAMEL-9894
> Project: Camel
> Issue Type: Bug
> Components: camel-rx
>Affects Versions: 2.17.0
>Reporter: Arun
>Priority: Critical
>
> I am using camel-rx to observe some messages from Active MQ. After I complete
> the subscription I am getting onCompleted() event also. But If I look in
> Active MQ console, I can still see the consumer live. How to release this
> connection once subscription is over?
> Code :
> ReactiveCamel rx = new ReactiveCamel(camel);
>
> Observable observable1 =
> rx.toObservable("activemq:queue:Output Queue -
> 01?selector=JMSCorrelationID%3D'"+ uuid + "' AND eventType%3D'cust_msg'");
>
> observable1.first().subscribe(new Subscriber()
> {
>
> // methods here
>
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-8637) Upgrade Jetty version to 9.x in Camel-CometD
[ https://issues.apache.org/jira/browse/CAMEL-8637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-8637: --- Assignee: Andrea Cosentino > Upgrade Jetty version to 9.x in Camel-CometD > - > > Key: CAMEL-8637 > URL: https://issues.apache.org/jira/browse/CAMEL-8637 > Project: Camel > Issue Type: Task > Components: camel-cometd >Reporter: Willem Jiang >Assignee: Andrea Cosentino > Fix For: 2.18.0 > > > It's time to upgrade the Jetty version to 9.x as the 8.x is EOL for a while. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-3962) don't always load the content of a file when unmarshalling
[ https://issues.apache.org/jira/browse/CAMEL-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251763#comment-15251763 ] Mamta commented on CAMEL-3962: -- Not sure if this is fixed - I am using camel 2.11.0 version, still facing similar issue. We are sending files via sftp, so why it is giving us Storage exception. Strange thing is files are getting delivered to users successfully, but our process is getting this exception, which is not letting us throw the correct alert. And we are forced to check with end users whether they received files are not. There should be a way to know if the files have been successfully delivered. Please help me as this is something we identified in our running prod code on a regular basis. > don't always load the content of a file when unmarshalling > -- > > Key: CAMEL-3962 > URL: https://issues.apache.org/jira/browse/CAMEL-3962 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Romain Manni-Bucau >Assignee: Claus Ibsen > Fix For: 2.8.0, 2.7.4 > > > org.apache.camel.component.file.GenericFileConverter#genericFileToInputStream > always load the content of a file, it can be improved for well known types > (returning a FileInputStream). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-9898) SimpleBuilder throws NullPointerException when replacing string using regexAll method and the regex contains }
[
https://issues.apache.org/jira/browse/CAMEL-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lefteris Tsallas updated CAMEL-9898:
Description:
Add this unit test in org.apache.camel.builder.SimpleBuilderTest to reproduce
the issue. Only fails when the regex contains }
{code}
public void testRegexAllWithPlaceHolders() {
exchange.getIn().setHeader("activateUrl",
"http://some/rest/api/(id)/activate");
assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\(id\\)\",\"12\")}").evaluate(exchange,String.class));
//passes when contains { only
exchange.getIn().setHeader("activateUrl",
"http://some/rest/api/{id/activate;);
assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\",\"12\")}").evaluate(exchange,String.class));
String replaced =
"http://some/rest/api/{id}/activate".replaceAll("\\{id\\}","12");
assertEquals( "http://some/rest/api/12/activate;, replaced);
/// But throws throws NullPointerException when regexALl inside a
simple expression
exchange.getIn().setHeader("activateUrl",
"http://some/rest/api/{id}/activate;);
assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\\}\",\"12\")}").evaluate(exchange,String.class));
}
{code}
was:
Add this unit test in org.apache.camel.builder.SimpleBuilderTest to reproduce
the issue. Only fails when the regex contains }
{code}
public void testRegexAllWithPlaceHolders() {
exchange.getIn().setHeader("activateUrl",
"http://some/rest/api/(id)/activate");
assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\(id\\)\",\"12\")}").evaluate(exchange,String.class));
//passes when contains { only
exchange.getIn().setHeader("activateUrl",
"http://some/rest/api/{id/activate;);
assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\",\"12\")}").evaluate(exchange,String.class));
String replaced =
"http://some/rest/api/{id}/activate".replaceAll("\\{id\\}","12");
assertEquals( "http://some/rest/api/12/activate;, replaced);
/// But throws throws NullPointerException when regexALl inside a
simple expression
exchange.getIn().setHeader("activateUrl",
"http://some/rest/api/{d}/activate;);
assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\\}\",\"12\")}").evaluate(exchange,String.class));
}
{code}
> SimpleBuilder throws NullPointerException when replacing string using
> regexAll method and the regex contains }
> --
>
> Key: CAMEL-9898
> URL: https://issues.apache.org/jira/browse/CAMEL-9898
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.17.0
>Reporter: Lefteris Tsallas
>Priority: Minor
>
>
> Add this unit test in org.apache.camel.builder.SimpleBuilderTest to reproduce
> the issue. Only fails when the regex contains }
> {code}
> public void testRegexAllWithPlaceHolders() {
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/(id)/activate");
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\(id\\)\",\"12\")}").evaluate(exchange,String.class));
> //passes when contains { only
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\",\"12\")}").evaluate(exchange,String.class));
> String replaced =
> "http://some/rest/api/{id}/activate".replaceAll("\\{id\\}","12");
> assertEquals( "http://some/rest/api/12/activate;, replaced);
> /// But throws throws NullPointerException when regexALl inside a
> simple expression
> exchange.getIn().setHeader("activateUrl",
> "http://some/rest/api/{id}/activate;);
>
> assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\\}\",\"12\")}").evaluate(exchange,String.class));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-9898) SimpleBuilder throws NullPointerException when replacing string using regexAll method and the regex contains }
Lefteris Tsallas created CAMEL-9898:
---
Summary: SimpleBuilder throws NullPointerException when replacing
string using regexAll method and the regex contains }
Key: CAMEL-9898
URL: https://issues.apache.org/jira/browse/CAMEL-9898
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.17.0
Reporter: Lefteris Tsallas
Priority: Minor
Add this unit test in org.apache.camel.builder.SimpleBuilderTest to reproduce
the issue. Only fails when the regex contains }
{code}
public void testRegexAllWithPlaceHolders() {
exchange.getIn().setHeader("activateUrl",
"http://some/rest/api/(id)/activate");
assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\(id\\)\",\"12\")}").evaluate(exchange,String.class));
//passes when contains { only
exchange.getIn().setHeader("activateUrl",
"http://some/rest/api/{id/activate;);
assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\",\"12\")}").evaluate(exchange,String.class));
String replaced =
"http://some/rest/api/{id}/activate".replaceAll("\\{id\\}","12");
assertEquals( "http://some/rest/api/12/activate;, replaced);
/// But throws throws NullPointerException when regexALl inside a
simple expression
exchange.getIn().setHeader("activateUrl",
"http://some/rest/api/{d}/activate;);
assertEquals("http://some/rest/api/12/activate",SimpleBuilder.simple("${header.activateUrl.replaceAll(\"\\{id\\}\",\"12\")}").evaluate(exchange,String.class));
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-9897) Add an Option to the XSLT Component to support custom EntityResolver
Hubertus Willuhn created CAMEL-9897:
---
Summary: Add an Option to the XSLT Component to support custom
EntityResolver
Key: CAMEL-9897
URL: https://issues.apache.org/jira/browse/CAMEL-9897
Project: Camel
Issue Type: Improvement
Components: camel-core
Affects Versions: 2.17.0
Environment: all (windows, linux)
Reporter: Hubertus Willuhn
Priority: Minor
While using the XSLT component of Camel i came across this post in Nabble:
[http://camel.465427.n5.nabble.com/Make-xslt-component-not-to-validate-dtd-s-or-use-local-copy-td5727789.html#a5728034]
I am using XML files that looks like:
{code:xml}
A8:20:018046
mtalliques sdimentation
pargravi
...
{code}
so it would be nice to have a EntityResolver for my DTD and the entities.
At the moment i can only specify a custom URIResolver bean (which works great,
by the way).
(see "uriResolver"-option documentation [http://camel.apache.org/xslt.html])
Is it possible to add an simliar option to the XSLT component to achieve this?
I am using Camel 2.17.0 and Saxon 9.5.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9896) Deadletter Failure processor is invoked even if error handling strategy defines to continue routing
[ https://issues.apache.org/jira/browse/CAMEL-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Kumar updated CAMEL-9896: Affects Version/s: (was: 2.15.0) 2.15.6 > Deadletter Failure processor is invoked even if error handling strategy > defines to continue routing > --- > > Key: CAMEL-9896 > URL: https://issues.apache.org/jira/browse/CAMEL-9896 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.15.6 > Environment: stage >Reporter: Nikhil Kumar >Priority: Critical > > When a DeadLetterChannel is used as context scoped error handling strategy > with FailureProcessor set and a route scoped error handling strategy is > defined to continue routing in case of certain exception classes, then it is > observed that even in case of exceptions which belong to exceptions defined > in OnException clause, the dead letter's failure processor is still > triggered. > A test case to simulate this behaviour is pasted. > http://pastebin.com/raw/cfQhsJj0 - contains test case. > http://pastebin.com/raw/K6wZc9Yh - test output -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-9896) Deadletter Failure processor is invoked even if error handling strategy defines to continue routing
Nikhil Kumar created CAMEL-9896: --- Summary: Deadletter Failure processor is invoked even if error handling strategy defines to continue routing Key: CAMEL-9896 URL: https://issues.apache.org/jira/browse/CAMEL-9896 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.15.0 Environment: stage Reporter: Nikhil Kumar Priority: Critical When a DeadLetterChannel is used as context scoped error handling strategy with FailureProcessor set and a route scoped error handling strategy is defined to continue routing in case of certain exception classes, then it is observed that even in case of exceptions which belong to exceptions defined in OnException clause, the dead letter's failure processor is still triggered. A test case to simulate this behaviour is pasted. http://pastebin.com/raw/cfQhsJj0 - contains test case. http://pastebin.com/raw/K6wZc9Yh - test output -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-9882) Support importing Camel XML configuration files in Camel CDI
[
https://issues.apache.org/jira/browse/CAMEL-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonin Stefanutti updated CAMEL-9882:
--
Description:
So that user can use their existing Camel XML files with CDI or use Camel XML
for configuring their Camel contexts.
For example, given the following Camel XML:
{code}
http://camel.apache.org/schema/spring;>
${body} contains 'exception'
Response to ${body}
{code}
And following bean:
{code}
@Named
@Produces
Exception failure = new CamelException("failure message!");
{code}
The Camel XML elements with an {{id}} attributes ({{errorHandler}} in the
example) get deployed as CDI beans and vice-versa the {{ref}} attributes can
refer to CDI beans ({{@Named("failure")}} in the example).
The current proposition is to expose an annotation that the developer can use
on any CDI bean to declare the Camel XML files to import in her/his Camel CDI
application, e.g.:
{code}
@ImportResource("imported-context.xml")
class MyCamelCdiBean {
}
{code}
> Support importing Camel XML configuration files in Camel CDI
>
>
> Key: CAMEL-9882
> URL: https://issues.apache.org/jira/browse/CAMEL-9882
> Project: Camel
> Issue Type: New Feature
> Components: camel-cdi
>Reporter: Antonin Stefanutti
>Assignee: Antonin Stefanutti
> Fix For: 2.18.0
>
>
> So that user can use their existing Camel XML files with CDI or use Camel XML
> for configuring their Camel contexts.
> For example, given the following Camel XML:
> {code}
>xmlns="http://camel.apache.org/schema/spring;>
>type="LoggingErrorHandler"
> logName="error"
> level="WARN"/>
>
>
>
>
> ${body} contains 'exception'
>
>
>
>
> Response to ${body}
>
>
>
>
>
>
> {code}
> And following bean:
> {code}
> @Named
> @Produces
> Exception failure = new CamelException("failure message!");
> {code}
> The Camel XML elements with an {{id}} attributes ({{errorHandler}} in the
> example) get deployed as CDI beans and vice-versa the {{ref}} attributes can
> refer to CDI beans ({{@Named("failure")}} in the example).
> The current proposition is to expose an annotation that the developer can use
> on any CDI bean to declare the Camel XML files to import in her/his Camel CDI
> application, e.g.:
> {code}
> @ImportResource("imported-context.xml")
> class MyCamelCdiBean {
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-9895) Setup a by default password to access the spring boot ssh server
[
https://issues.apache.org/jira/browse/CAMEL-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Moulliard reassigned CAMEL-9895:
Assignee: Charles Moulliard
> Setup a by default password to access the spring boot ssh server
>
>
> Key: CAMEL-9895
> URL: https://issues.apache.org/jira/browse/CAMEL-9895
> Project: Camel
> Issue Type: Bug
> Components: examples
>Reporter: Charles Moulliard
>Assignee: Charles Moulliard
> Fix For: 2.18.0
>
>
> Setup a by default password to access the spring boot ssh server in order to
> simplify the access to the SSH server as it is not so easy to get the random
> generated password
> {code}
> Parameter to be added within the application.yml file
> shell.auth.simple.user.password: password
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-9895) Setup a by default password to access the spring boot ssh server
[
https://issues.apache.org/jira/browse/CAMEL-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Moulliard resolved CAMEL-9895.
--
Resolution: Fixed
> Setup a by default password to access the spring boot ssh server
>
>
> Key: CAMEL-9895
> URL: https://issues.apache.org/jira/browse/CAMEL-9895
> Project: Camel
> Issue Type: Bug
> Components: examples
>Reporter: Charles Moulliard
>Assignee: Charles Moulliard
> Fix For: 2.18.0
>
>
> Setup a by default password to access the spring boot ssh server in order to
> simplify the access to the SSH server as it is not so easy to get the random
> generated password
> {code}
> Parameter to be added within the application.yml file
> shell.auth.simple.user.password: password
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-9895) Setup a by default password to access the spring boot ssh server
Charles Moulliard created CAMEL-9895:
Summary: Setup a by default password to access the spring boot ssh
server
Key: CAMEL-9895
URL: https://issues.apache.org/jira/browse/CAMEL-9895
Project: Camel
Issue Type: Bug
Components: examples
Reporter: Charles Moulliard
Fix For: 2.18.0
Setup a by default password to access the spring boot ssh server in order to
simplify the access to the SSH server as it is not so easy to get the random
generated password
{code}
Parameter to be added within the application.yml file
shell.auth.simple.user.password: password
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
