[jira] [Work started] (CAMEL-9800) Create Spring Boot example with REST DSL and Swagger
[ https://issues.apache.org/jira/browse/CAMEL-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-9800 started by Gregor Zurowski. -- > Create Spring Boot example with REST DSL and Swagger > > > Key: CAMEL-9800 > URL: https://issues.apache.org/jira/browse/CAMEL-9800 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Gregor Zurowski >Assignee: Gregor Zurowski >Priority: Minor > Fix For: 2.18.0 > > > Create a new Camel example showing how work with Spring Boot, Camel REST DSL > and Swagger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-9800) Create Spring Boot example with REST DSL and Swagger
Gregor Zurowski created CAMEL-9800: -- Summary: Create Spring Boot example with REST DSL and Swagger Key: CAMEL-9800 URL: https://issues.apache.org/jira/browse/CAMEL-9800 Project: Camel Issue Type: New Feature Components: camel-spring-boot Reporter: Gregor Zurowski Assignee: Gregor Zurowski Priority: Minor Fix For: 2.18.0 Create a new Camel example showing how work with Spring Boot, Camel REST DSL and Swagger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CAMEL-9788) Jetty endpoint option "matchOnUriPrefix" does not work properly
[ https://issues.apache.org/jira/browse/CAMEL-9788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovník closed CAMEL-9788. -- > Jetty endpoint option "matchOnUriPrefix" does not work properly > --- > > Key: CAMEL-9788 > URL: https://issues.apache.org/jira/browse/CAMEL-9788 > Project: Camel > Issue Type: Bug > Components: camel-jetty >Affects Versions: 2.18.0 >Reporter: Martin Basovník >Assignee: Claus Ibsen > Fix For: 2.18.0 > > Attachments: camel-9788.zip > > > Jetty endpoint option "matchOnUriPrefix" does not work properly. Body does > not contain original content. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-9788) Jetty endpoint option "matchOnUriPrefix" does not work properly
[ https://issues.apache.org/jira/browse/CAMEL-9788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223015#comment-15223015 ] Martin Basovník commented on CAMEL-9788: My fault. Thank you for clarification! > Jetty endpoint option "matchOnUriPrefix" does not work properly > --- > > Key: CAMEL-9788 > URL: https://issues.apache.org/jira/browse/CAMEL-9788 > Project: Camel > Issue Type: Bug > Components: camel-jetty >Affects Versions: 2.18.0 >Reporter: Martin Basovník >Assignee: Claus Ibsen > Fix For: 2.18.0 > > Attachments: camel-9788.zip > > > Jetty endpoint option "matchOnUriPrefix" does not work properly. Body does > not contain original content. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[ https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222969#comment-15222969 ] ASF GitHub Bot commented on CAMEL-6132: --- Github user hqstevenson closed the pull request at: https://github.com/apache/camel/pull/923 > camel-test-karaf - To allow end users more easily do Camel and Karaf > integration test > - > > Key: CAMEL-6132 > URL: https://issues.apache.org/jira/browse/CAMEL-6132 > Project: Camel > Issue Type: New Feature > Components: karaf >Reporter: Claus Ibsen >Assignee: Quinn Stevenson > Fix For: Future > > > We should introduce a proper camel-test-karaf component that *end users* can > use to do Camel and Karaf integration tests. > The code we have in tests/camel-itest-karaf is for internal usage and testing > of Camel. The code is not polished and intended for end users. > We should create a new module for that, and take the good parts of > camel-itest-karaf and make it user friendly etc. And of course have docs to > go with as well. > And when its good, we can use that in camel-itest-karaf also (eat our own dog > food) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-9799) JSON/JSON Schema validator
Andreas Gebhardt created CAMEL-9799: --- Summary: JSON/JSON Schema validator Key: CAMEL-9799 URL: https://issues.apache.org/jira/browse/CAMEL-9799 Project: Camel Issue Type: Wish Reporter: Andreas Gebhardt > Von: Gnanaguru S > An: ★ d...@camel.apache.org > > Subject: \[DISCUSS\] - Thoughts on Apache Camel 2.18 and towards 3.0 > > \[...\] > 7. JSON validator. XML XSD validation is nice and straight forward, but it > will be great if we have something similar for JSON as well. like > to:json-validator:classpath/response.json > \[...\] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-9798) camel-cdi - Add support for injecting default ProducerTemplate
[
https://issues.apache.org/jira/browse/CAMEL-9798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222855#comment-15222855
]
Claus Ibsen commented on CAMEL-9798:
Also I wonder if we can get rid of those INFO logs?
{code}
2016-04-02 13:13:29,663 [main ] INFO Event
- WELD-000411: Observer method [BackedAnnotatedMethod] private
org.apache.camel.cdi.CdiCamelExtension.processAnnotatedType(@Observes
ProcessAnnotatedType) receives events for all annotated types. Consider
restricting events using @WithAnnotations or a generic type with bounds.
2016-04-02 13:13:29,672 [main ] INFO Event
- WELD-000411: Observer method [BackedAnnotatedMethod] private
org.apache.camel.cdi.CdiCamelExtension.processAnnotatedType(@Observes
ProcessAnnotatedType) receives events for all annotated types. Consider
restricting events using @WithAnnotations or a generic type with bounds.
{code}
> camel-cdi - Add support for injecting default ProducerTemplate
> --
>
> Key: CAMEL-9798
> URL: https://issues.apache.org/jira/browse/CAMEL-9798
> Project: Camel
> Issue Type: Improvement
> Components: camel-cdi
>Affects Versions: 2.17.0
>Reporter: Claus Ibsen
>Assignee: Antonin Stefanutti
>
> We should be able to inject a default producer template using
> {code}
> @Inject
> private ProducerTemplate template;
> {code}
> Currently that does not work and you get an error (see below)
> But if you setup a default endpoint with @Uri it works
> {code}
> @Inject @Uri("file:target/inbox")
> private ProducerTemplate template;
> {code}
> The error you get
> {code}
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied
> dependencies for type ProducerTemplate with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private
> camelinaction.FirstTest.template
> at camelinaction.FirstTest.template(FirstTest.java:0)
> WELD-001475: The following beans match by type, but none have matching
> qualifiers:
> - Producer Method [ProducerTemplate] with qualifiers [@Excluded @Any]
> declared as [[UnbackedAnnotatedMethod] @Produces @Excluded private static
> org.apache.camel.cdi.CdiCamelFactory.producerTemplate(InjectionPoint, @Any
> Instance, CdiCamelExtension)],
> - Producer Method [ProducerTemplate] with qualifiers [@Excluded @Any]
> declared as [[UnbackedAnnotatedMethod] @Produces @Excluded private static
> org.apache.camel.cdi.CdiCamelFactory.producerTemplate(InjectionPoint, @Any
> Instance, CdiCamelExtension)]
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:359)
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:281)
> at
> org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
> at
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
> at
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> The same thing for ConsumerTemplate which should also be injectable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9798) camel-cdi - Add support for injecting default ProducerTemplate
[
https://issues.apache.org/jira/browse/CAMEL-9798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222854#comment-15222854
]
Claus Ibsen commented on CAMEL-9798:
There is an example here
https://github.com/camelinaction/camelinaction2/tree/master/chapter9/firsttest-cdi
> camel-cdi - Add support for injecting default ProducerTemplate
> --
>
> Key: CAMEL-9798
> URL: https://issues.apache.org/jira/browse/CAMEL-9798
> Project: Camel
> Issue Type: Improvement
> Components: camel-cdi
>Affects Versions: 2.17.0
>Reporter: Claus Ibsen
>
> We should be able to inject a default producer template using
> {code}
> @Inject
> private ProducerTemplate template;
> {code}
> Currently that does not work and you get an error (see below)
> But if you setup a default endpoint with @Uri it works
> {code}
> @Inject @Uri("file:target/inbox")
> private ProducerTemplate template;
> {code}
> The error you get
> {code}
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied
> dependencies for type ProducerTemplate with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private
> camelinaction.FirstTest.template
> at camelinaction.FirstTest.template(FirstTest.java:0)
> WELD-001475: The following beans match by type, but none have matching
> qualifiers:
> - Producer Method [ProducerTemplate] with qualifiers [@Excluded @Any]
> declared as [[UnbackedAnnotatedMethod] @Produces @Excluded private static
> org.apache.camel.cdi.CdiCamelFactory.producerTemplate(InjectionPoint, @Any
> Instance, CdiCamelExtension)],
> - Producer Method [ProducerTemplate] with qualifiers [@Excluded @Any]
> declared as [[UnbackedAnnotatedMethod] @Produces @Excluded private static
> org.apache.camel.cdi.CdiCamelFactory.producerTemplate(InjectionPoint, @Any
> Instance, CdiCamelExtension)]
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:359)
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:281)
> at
> org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
> at
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
> at
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> The same thing for ConsumerTemplate which should also be injectable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-9798) camel-cdi - Add support for injecting default ProducerTemplate
Claus Ibsen created CAMEL-9798:
--
Summary: camel-cdi - Add support for injecting default
ProducerTemplate
Key: CAMEL-9798
URL: https://issues.apache.org/jira/browse/CAMEL-9798
Project: Camel
Issue Type: Improvement
Components: camel-cdi
Affects Versions: 2.17.0
Reporter: Claus Ibsen
We should be able to inject a default producer template using
{code}
@Inject
private ProducerTemplate template;
{code}
Currently that does not work and you get an error (see below)
But if you setup a default endpoint with @Uri it works
{code}
@Inject @Uri("file:target/inbox")
private ProducerTemplate template;
{code}
The error you get
{code}
org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied
dependencies for type ProducerTemplate with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private
camelinaction.FirstTest.template
at camelinaction.FirstTest.template(FirstTest.java:0)
WELD-001475: The following beans match by type, but none have matching
qualifiers:
- Producer Method [ProducerTemplate] with qualifiers [@Excluded @Any]
declared as [[UnbackedAnnotatedMethod] @Produces @Excluded private static
org.apache.camel.cdi.CdiCamelFactory.producerTemplate(InjectionPoint, @Any
Instance, CdiCamelExtension)],
- Producer Method [ProducerTemplate] with qualifiers [@Excluded @Any]
declared as [[UnbackedAnnotatedMethod] @Produces @Excluded private static
org.apache.camel.cdi.CdiCamelFactory.producerTemplate(InjectionPoint, @Any
Instance, CdiCamelExtension)]
at
org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:359)
at
org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:281)
at
org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
at
org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at
org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at
org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
at
org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
The same thing for ConsumerTemplate which should also be injectable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9798) camel-cdi - Add support for injecting default ProducerTemplate
[
https://issues.apache.org/jira/browse/CAMEL-9798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-9798:
---
Assignee: Antonin Stefanutti
> camel-cdi - Add support for injecting default ProducerTemplate
> --
>
> Key: CAMEL-9798
> URL: https://issues.apache.org/jira/browse/CAMEL-9798
> Project: Camel
> Issue Type: Improvement
> Components: camel-cdi
>Affects Versions: 2.17.0
>Reporter: Claus Ibsen
>Assignee: Antonin Stefanutti
>
> We should be able to inject a default producer template using
> {code}
> @Inject
> private ProducerTemplate template;
> {code}
> Currently that does not work and you get an error (see below)
> But if you setup a default endpoint with @Uri it works
> {code}
> @Inject @Uri("file:target/inbox")
> private ProducerTemplate template;
> {code}
> The error you get
> {code}
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied
> dependencies for type ProducerTemplate with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private
> camelinaction.FirstTest.template
> at camelinaction.FirstTest.template(FirstTest.java:0)
> WELD-001475: The following beans match by type, but none have matching
> qualifiers:
> - Producer Method [ProducerTemplate] with qualifiers [@Excluded @Any]
> declared as [[UnbackedAnnotatedMethod] @Produces @Excluded private static
> org.apache.camel.cdi.CdiCamelFactory.producerTemplate(InjectionPoint, @Any
> Instance, CdiCamelExtension)],
> - Producer Method [ProducerTemplate] with qualifiers [@Excluded @Any]
> declared as [[UnbackedAnnotatedMethod] @Produces @Excluded private static
> org.apache.camel.cdi.CdiCamelFactory.producerTemplate(InjectionPoint, @Any
> Instance, CdiCamelExtension)]
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:359)
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:281)
> at
> org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
> at
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
> at
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> The same thing for ConsumerTemplate which should also be injectable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-9724) Kafka karaf bundle points to incorrect scala version
[
https://issues.apache.org/jira/browse/CAMEL-9724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9724.
Resolution: Won't Fix
Assignee: Claus Ibsen
Yeah upgrade to 2.17 that is Java based, and there is no more scala version
hell.
> Kafka karaf bundle points to incorrect scala version
>
>
> Key: CAMEL-9724
> URL: https://issues.apache.org/jira/browse/CAMEL-9724
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka, karaf
>Affects Versions: 2.16.2
> Environment: karaf 4.0.4
> camel 2.16.2
> JDK 1.7
>Reporter: Jose Luis Pedrosa
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.3
>
>
> Hi
> I see there's a missalingment between the features dependencies and the pom
> of the camel-kafka component that makes impossible to run a Producer in
> karaf. I can see that in the features.xml
> {code:xml}
> dependency='true'>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.kafka-clients/${kafka-clients-bundle-version}
> dependency='true'>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.kafka_2.10/${kafka-bundle-version}
> {code}
> It's trying to use 2.10 scala version, but in the pom.xml we point to 2.11
> scala version
> {code:xml}
>
> org.apache.kafka
> kafka_2.11
> ${kafka-version}
>
>
> org.slf4j
> slf4j-simple
>
>
> scala-library
> org.scala-lang
>
>
>
> {code}
> this causes some Class not found exceptions (funny some how) only in the
> producer, but the consumer is ok.
> {noformat}
> org.apache.camel.FailedToCreateProducerException: Failed to create Producer
> for endpoint: Endpoint[kafka://.].
> Reason: java.lang.ClassNotFoundException: kafka.serializer.DefaultEncoder
> {noformat}
> {noformat}
> karaf@root()> bundle:list | grep kaf
> 68 | Active | 50 | 2.16.2| camel-kafka
> 70 | Active | 50 | 0.8.2.2_1 | Apache
> ServiceMix :: Bundles :: kafka-clients
> 71 | Active | 50 | 0.8.2.2_1 | Apache
> ServiceMix :: Bundles :: kafka_2.10
> {noformat}
> I see this is already fix in master... so this should not apply to 2.17.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9797) camel-elastichsearch - Tests fails since recent upgrade
[
https://issues.apache.org/jira/browse/CAMEL-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222810#comment-15222810
]
Andrea Cosentino commented on CAMEL-9797:
-
The problem was related to the upgrade of Lucene to 5.5.0.
ES 2.2.1 is still base on Lucene 5.4.1.
Now everything is ok and Camel-Lucene works in OSGi too.
> camel-elastichsearch - Tests fails since recent upgrade
> ---
>
> Key: CAMEL-9797
> URL: https://issues.apache.org/jira/browse/CAMEL-9797
> Project: Camel
> Issue Type: Test
> Components: camel-elasticsearch
>Affects Versions: 2.18.0
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
> Fix For: 2.18.0
>
>
> It was upgraded to 2.2.1 and then the tests starts to fail with some weird
> errors
> {code}
> Tests in error:
> ElasticsearchBulkTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
> Inconsiste...
> ElasticsearchClusterIndexTest>ElasticsearchClusterBaseTest.cleanUpOnce:53 »
> Verify
>
> ElasticsearchGetSearchDeleteExistsUpdateTest>ElasticsearchBaseTest.cleanupOnce:44
> » Verify
> ElasticsearchIndexTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
> Inconsist...
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-9797) camel-elastichsearch - Tests fails since recent upgrade
[
https://issues.apache.org/jira/browse/CAMEL-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-9797.
-
Resolution: Fixed
> camel-elastichsearch - Tests fails since recent upgrade
> ---
>
> Key: CAMEL-9797
> URL: https://issues.apache.org/jira/browse/CAMEL-9797
> Project: Camel
> Issue Type: Test
> Components: camel-elasticsearch
>Affects Versions: 2.18.0
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
> Fix For: 2.18.0
>
>
> It was upgraded to 2.2.1 and then the tests starts to fail with some weird
> errors
> {code}
> Tests in error:
> ElasticsearchBulkTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
> Inconsiste...
> ElasticsearchClusterIndexTest>ElasticsearchClusterBaseTest.cleanUpOnce:53 »
> Verify
>
> ElasticsearchGetSearchDeleteExistsUpdateTest>ElasticsearchBaseTest.cleanupOnce:44
> » Verify
> ElasticsearchIndexTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
> Inconsist...
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-9788) Jetty endpoint option "matchOnUriPrefix" does not work properly
[
https://issues.apache.org/jira/browse/CAMEL-9788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9788.
Resolution: Invalid
Assignee: Claus Ibsen
Fix Version/s: 2.18.0
You do a HTTP GET command then the body is not included when sending.
Specify the parameter should be POST
{code}
@Test
public void testJettyUriRewrite() throws Exception {
String out =
template.requestBodyAndHeader("http4://localhost:8081/foo?phrase=test",
"camel", Exchange.HTTP_METHOD, "post", String.class);
assertEquals("test camel", out);
}
{code}
> Jetty endpoint option "matchOnUriPrefix" does not work properly
> ---
>
> Key: CAMEL-9788
> URL: https://issues.apache.org/jira/browse/CAMEL-9788
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 2.18.0
>Reporter: Martin Basovník
>Assignee: Claus Ibsen
> Fix For: 2.18.0
>
> Attachments: camel-9788.zip
>
>
> Jetty endpoint option "matchOnUriPrefix" does not work properly. Body does
> not contain original content.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9791) DeadLetterChannel not triggered on RejectedExecutionException
[ https://issues.apache.org/jira/browse/CAMEL-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222779#comment-15222779 ] Claus Ibsen commented on CAMEL-9791: Can you provide an unit test or sample project demonstrating this? > DeadLetterChannel not triggered on RejectedExecutionException > - > > Key: CAMEL-9791 > URL: https://issues.apache.org/jira/browse/CAMEL-9791 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.17.0 >Reporter: Thibaut Robert >Priority: Minor > > I use a thread processor to implement multi-threading > I wish that the deadletter endpoint of the route to be called when the pool > reject the execution of the task (to save the message on disk) > However, whatever the rejectedPolicy I choose, the rejected exchange is just > dropped because the exchange is marked with routeStop and redeliveryExhausted. > I think it's correct to not redeliver (we are lacking resources, replaying > won't help), but there should at least be a way to handle the failed message > somehow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-9796) Internal Access still displayed, no change to JSON generated
[
https://issues.apache.org/jira/browse/CAMEL-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9796.
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: 2.16.3
The option is deprecated and no longer in use from 2.18 onwards.
Do not use it
> Internal Access still displayed, no change to JSON generated
>
>
> Key: CAMEL-9796
> URL: https://issues.apache.org/jira/browse/CAMEL-9796
> Project: Camel
> Issue Type: Improvement
> Components: camel-swagger, rest
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.3, 2.18.0, 2.17.1
>
>
> When setting ".access" either "internal" or as "false" it still appears in
> Swagger-UI/doesn't modify the JSON to "paramAccess":"internal"
> {code}
> rest(baseUrl).get("/{customerId}")
> //Swagger Documentation
>
> .param().name("customerId").access("internal").type(RestParamType.body).description("The
> customer ID number.").required(true).dataType("string").endParam();
> {code}
> JSON Generated:
> {code}
> parameters: [{
> name: "customerId",
> in: "path",
> description: "The customer ID number.",
> required: true,
> type: "string"
> },...]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9796) Internal Access still displayed, no change to JSON generated
[
https://issues.apache.org/jira/browse/CAMEL-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-9796:
---
Component/s: rest
> Internal Access still displayed, no change to JSON generated
>
>
> Key: CAMEL-9796
> URL: https://issues.apache.org/jira/browse/CAMEL-9796
> Project: Camel
> Issue Type: Improvement
> Components: camel-swagger, rest
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
>Priority: Minor
> Fix For: 2.18.0, 2.17.1
>
>
> When setting ".access" either "internal" or as "false" it still appears in
> Swagger-UI/doesn't modify the JSON to "paramAccess":"internal"
> {code}
> rest(baseUrl).get("/{customerId}")
> //Swagger Documentation
>
> .param().name("customerId").access("internal").type(RestParamType.body).description("The
> customer ID number.").required(true).dataType("string").endParam();
> {code}
> JSON Generated:
> {code}
> parameters: [{
> name: "customerId",
> in: "path",
> description: "The customer ID number.",
> required: true,
> type: "string"
> },...]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9796) Internal Access still displayed, no change to JSON generated
[
https://issues.apache.org/jira/browse/CAMEL-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-9796:
---
Issue Type: Improvement (was: Bug)
> Internal Access still displayed, no change to JSON generated
>
>
> Key: CAMEL-9796
> URL: https://issues.apache.org/jira/browse/CAMEL-9796
> Project: Camel
> Issue Type: Improvement
> Components: camel-swagger, rest
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
> Fix For: 2.18.0, 2.17.1
>
>
> When setting ".access" either "internal" or as "false" it still appears in
> Swagger-UI/doesn't modify the JSON to "paramAccess":"internal"
> {code}
> rest(baseUrl).get("/{customerId}")
> //Swagger Documentation
>
> .param().name("customerId").access("internal").type(RestParamType.body).description("The
> customer ID number.").required(true).dataType("string").endParam();
> {code}
> JSON Generated:
> {code}
> parameters: [{
> name: "customerId",
> in: "path",
> description: "The customer ID number.",
> required: true,
> type: "string"
> },...]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9796) Internal Access still displayed, no change to JSON generated
[
https://issues.apache.org/jira/browse/CAMEL-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-9796:
---
Fix Version/s: 2.17.1
2.18.0
> Internal Access still displayed, no change to JSON generated
>
>
> Key: CAMEL-9796
> URL: https://issues.apache.org/jira/browse/CAMEL-9796
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger, rest
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
> Fix For: 2.18.0, 2.17.1
>
>
> When setting ".access" either "internal" or as "false" it still appears in
> Swagger-UI/doesn't modify the JSON to "paramAccess":"internal"
> {code}
> rest(baseUrl).get("/{customerId}")
> //Swagger Documentation
>
> .param().name("customerId").access("internal").type(RestParamType.body).description("The
> customer ID number.").required(true).dataType("string").endParam();
> {code}
> JSON Generated:
> {code}
> parameters: [{
> name: "customerId",
> in: "path",
> description: "The customer ID number.",
> required: true,
> type: "string"
> },...]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9796) Internal Access still displayed, no change to JSON generated
[
https://issues.apache.org/jira/browse/CAMEL-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-9796:
---
Priority: Minor (was: Major)
> Internal Access still displayed, no change to JSON generated
>
>
> Key: CAMEL-9796
> URL: https://issues.apache.org/jira/browse/CAMEL-9796
> Project: Camel
> Issue Type: Improvement
> Components: camel-swagger, rest
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
>Priority: Minor
> Fix For: 2.18.0, 2.17.1
>
>
> When setting ".access" either "internal" or as "false" it still appears in
> Swagger-UI/doesn't modify the JSON to "paramAccess":"internal"
> {code}
> rest(baseUrl).get("/{customerId}")
> //Swagger Documentation
>
> .param().name("customerId").access("internal").type(RestParamType.body).description("The
> customer ID number.").required(true).dataType("string").endParam();
> {code}
> JSON Generated:
> {code}
> parameters: [{
> name: "customerId",
> in: "path",
> description: "The customer ID number.",
> required: true,
> type: "string"
> },...]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9796) Internal Access still displayed, no change to JSON generated
[
https://issues.apache.org/jira/browse/CAMEL-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222760#comment-15222760
]
Claus Ibsen commented on CAMEL-9796:
access is an old parameter from 1.x. Its not in use in 2.0 spec.
> Internal Access still displayed, no change to JSON generated
>
>
> Key: CAMEL-9796
> URL: https://issues.apache.org/jira/browse/CAMEL-9796
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
>
> When setting ".access" either "internal" or as "false" it still appears in
> Swagger-UI/doesn't modify the JSON to "paramAccess":"internal"
> {code}
> rest(baseUrl).get("/{customerId}")
> //Swagger Documentation
>
> .param().name("customerId").access("internal").type(RestParamType.body).description("The
> customer ID number.").required(true).dataType("string").endParam();
> {code}
> JSON Generated:
> {code}
> parameters: [{
> name: "customerId",
> in: "path",
> description: "The customer ID number.",
> required: true,
> type: "string"
> },...]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-9793) PropertyPlaceHolder not loading Property, thinks it is a Parameter
[
https://issues.apache.org/jira/browse/CAMEL-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9793.
Resolution: Fixed
Thanks found the bug
> PropertyPlaceHolder not loading Property, thinks it is a Parameter
> --
>
> Key: CAMEL-9793
> URL: https://issues.apache.org/jira/browse/CAMEL-9793
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger, rest
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.3, 2.18.0, 2.17.1
>
>
> When loading a standard rest service into Camel and setting up Swagger.
> {code}
> rest("{{BASE_URL}}").get("/{customerId}").description("...")...
> {code}
> The {{Base_URL}} portion is
> 1. interpreted as a parameter much like {customerId}, i.e. the JSON displays:
> "{BASE_URL}" and "customerId" as the parameter name (removing outside curly
> brace)
> 2. the associated property is not loaded from the properties file
> The Property Place Holder portion though works for the rest-dsl configuration:
> {code}
> restConfiguration().apiProperty("api.title", "{{spring.application.name}}")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9793) PropertyPlaceHolder not loading Property, thinks it is a Parameter
[
https://issues.apache.org/jira/browse/CAMEL-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-9793:
---
Fix Version/s: 2.17.1
2.18.0
2.16.3
> PropertyPlaceHolder not loading Property, thinks it is a Parameter
> --
>
> Key: CAMEL-9793
> URL: https://issues.apache.org/jira/browse/CAMEL-9793
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger, rest
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.3, 2.18.0, 2.17.1
>
>
> When loading a standard rest service into Camel and setting up Swagger.
> {code}
> rest("{{BASE_URL}}").get("/{customerId}").description("...")...
> {code}
> The {{Base_URL}} portion is
> 1. interpreted as a parameter much like {customerId}, i.e. the JSON displays:
> "{BASE_URL}" and "customerId" as the parameter name (removing outside curly
> brace)
> 2. the associated property is not loaded from the properties file
> The Property Place Holder portion though works for the rest-dsl configuration:
> {code}
> restConfiguration().apiProperty("api.title", "{{spring.application.name}}")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-9797) camel-elastichsearch - Tests fails since recent upgrade
[
https://issues.apache.org/jira/browse/CAMEL-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-9797:
---
Assignee: Andrea Cosentino
> camel-elastichsearch - Tests fails since recent upgrade
> ---
>
> Key: CAMEL-9797
> URL: https://issues.apache.org/jira/browse/CAMEL-9797
> Project: Camel
> Issue Type: Test
> Components: camel-elasticsearch
>Affects Versions: 2.18.0
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
> Fix For: 2.18.0
>
>
> It was upgraded to 2.2.1 and then the tests starts to fail with some weird
> errors
> {code}
> Tests in error:
> ElasticsearchBulkTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
> Inconsiste...
> ElasticsearchClusterIndexTest>ElasticsearchClusterBaseTest.cleanUpOnce:53 »
> Verify
>
> ElasticsearchGetSearchDeleteExistsUpdateTest>ElasticsearchBaseTest.cleanupOnce:44
> » Verify
> ElasticsearchIndexTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
> Inconsist...
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-9793) PropertyPlaceHolder not loading Property, thinks it is a Parameter
[
https://issues.apache.org/jira/browse/CAMEL-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-9793:
--
Assignee: Claus Ibsen
> PropertyPlaceHolder not loading Property, thinks it is a Parameter
> --
>
> Key: CAMEL-9793
> URL: https://issues.apache.org/jira/browse/CAMEL-9793
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger, rest
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
>Assignee: Claus Ibsen
>Priority: Minor
>
> When loading a standard rest service into Camel and setting up Swagger.
> {code}
> rest("{{BASE_URL}}").get("/{customerId}").description("...")...
> {code}
> The {{Base_URL}} portion is
> 1. interpreted as a parameter much like {customerId}, i.e. the JSON displays:
> "{BASE_URL}" and "customerId" as the parameter name (removing outside curly
> brace)
> 2. the associated property is not loaded from the properties file
> The Property Place Holder portion though works for the rest-dsl configuration:
> {code}
> restConfiguration().apiProperty("api.title", "{{spring.application.name}}")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9793) PropertyPlaceHolder not loading Property, thinks it is a Parameter
[
https://issues.apache.org/jira/browse/CAMEL-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-9793:
---
Component/s: rest
> PropertyPlaceHolder not loading Property, thinks it is a Parameter
> --
>
> Key: CAMEL-9793
> URL: https://issues.apache.org/jira/browse/CAMEL-9793
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger, rest
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
>Priority: Minor
>
> When loading a standard rest service into Camel and setting up Swagger.
> {code}
> rest("{{BASE_URL}}").get("/{customerId}").description("...")...
> {code}
> The {{Base_URL}} portion is
> 1. interpreted as a parameter much like {customerId}, i.e. the JSON displays:
> "{BASE_URL}" and "customerId" as the parameter name (removing outside curly
> brace)
> 2. the associated property is not loaded from the properties file
> The Property Place Holder portion though works for the rest-dsl configuration:
> {code}
> restConfiguration().apiProperty("api.title", "{{spring.application.name}}")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9793) PropertyPlaceHolder not loading Property, thinks it is a Parameter
[
https://issues.apache.org/jira/browse/CAMEL-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-9793:
---
Labels: (was: propertyplaceholder,)
> PropertyPlaceHolder not loading Property, thinks it is a Parameter
> --
>
> Key: CAMEL-9793
> URL: https://issues.apache.org/jira/browse/CAMEL-9793
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger, rest
>Affects Versions: 2.16.2, 2.17.0
>Reporter: Flavel Heyman
>Priority: Minor
>
> When loading a standard rest service into Camel and setting up Swagger.
> {code}
> rest("{{BASE_URL}}").get("/{customerId}").description("...")...
> {code}
> The {{Base_URL}} portion is
> 1. interpreted as a parameter much like {customerId}, i.e. the JSON displays:
> "{BASE_URL}" and "customerId" as the parameter name (removing outside curly
> brace)
> 2. the associated property is not loaded from the properties file
> The Property Place Holder portion though works for the rest-dsl configuration:
> {code}
> restConfiguration().apiProperty("api.title", "{{spring.application.name}}")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9797) camel-elastichsearch - Tests fails since recent upgrade
[
https://issues.apache.org/jira/browse/CAMEL-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222751#comment-15222751
]
Andrea Cosentino commented on CAMEL-9797:
-
Locally everything was working fine after the upgrade. I will take a look.
> camel-elastichsearch - Tests fails since recent upgrade
> ---
>
> Key: CAMEL-9797
> URL: https://issues.apache.org/jira/browse/CAMEL-9797
> Project: Camel
> Issue Type: Test
> Components: camel-elasticsearch
>Affects Versions: 2.18.0
>Reporter: Claus Ibsen
> Fix For: 2.18.0
>
>
> It was upgraded to 2.2.1 and then the tests starts to fail with some weird
> errors
> {code}
> Tests in error:
> ElasticsearchBulkTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
> Inconsiste...
> ElasticsearchClusterIndexTest>ElasticsearchClusterBaseTest.cleanUpOnce:53 »
> Verify
>
> ElasticsearchGetSearchDeleteExistsUpdateTest>ElasticsearchBaseTest.cleanupOnce:44
> » Verify
> ElasticsearchIndexTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
> Inconsist...
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9797) camel-elastichsearch - Tests fails since recent upgrade
[
https://issues.apache.org/jira/browse/CAMEL-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222749#comment-15222749
]
Claus Ibsen commented on CAMEL-9797:
Such as
{code}
org.apache.camel.component.elasticsearch.ElasticsearchIndexTest Time elapsed:
0.332 sec <<< ERROR!
java.lang.VerifyError:
Inconsistent stackmap frames at branch target 32
Exception Details:
Location:
org/elasticsearch/common/lucene/Lucene.asSequentialAccessBits(ILorg/apache/lucene/search/Scorer;)Lorg/apache/lucene/util/Bits;
@32: new
Reason:
Type 'org/apache/lucene/search/Scorer' (current frame, locals[3]) is not
assignable to 'org/apache/lucene/search/DocIdSetIterator' (stack map, locals[3])
Current Frame:
bci: @24
flags: { }
locals: { integer, 'org/apache/lucene/search/Scorer',
'org/apache/lucene/search/TwoPhaseIterator', 'org/apache/lucene/search/Scorer' }
stack: { }
Stackmap Frame:
bci: @32
flags: { }
locals: { integer, 'org/apache/lucene/search/Scorer',
'org/apache/lucene/search/TwoPhaseIterator',
'org/apache/lucene/search/DocIdSetIterator' }
stack: { }
Bytecode:
0x000: 2bc7 000c bb00 cf59 1ab7 00d0 b02b b600
0x010: d14d 2cc7 0008 2b4e a700 082c b600 d24e
0x020: bb00 d359 1a2d 2cb7 00d4 b0
Stackmap Table:
same_frame(@13)
append_frame(@27,Object[#490])
append_frame(@32,Object[#491])
{code}
> camel-elastichsearch - Tests fails since recent upgrade
> ---
>
> Key: CAMEL-9797
> URL: https://issues.apache.org/jira/browse/CAMEL-9797
> Project: Camel
> Issue Type: Test
> Components: camel-elasticsearch
>Affects Versions: 2.18.0
>Reporter: Claus Ibsen
> Fix For: 2.18.0
>
>
> It was upgraded to 2.2.1 and then the tests starts to fail with some weird
> errors
> {code}
> Tests in error:
> ElasticsearchBulkTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
> Inconsiste...
> ElasticsearchClusterIndexTest>ElasticsearchClusterBaseTest.cleanUpOnce:53 »
> Verify
>
> ElasticsearchGetSearchDeleteExistsUpdateTest>ElasticsearchBaseTest.cleanupOnce:44
> » Verify
> ElasticsearchIndexTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
> Inconsist...
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-9797) camel-elastichsearch - Tests fails since recent upgrade
Claus Ibsen created CAMEL-9797:
--
Summary: camel-elastichsearch - Tests fails since recent upgrade
Key: CAMEL-9797
URL: https://issues.apache.org/jira/browse/CAMEL-9797
Project: Camel
Issue Type: Test
Components: camel-elasticsearch
Affects Versions: 2.18.0
Reporter: Claus Ibsen
Fix For: 2.18.0
It was upgraded to 2.2.1 and then the tests starts to fail with some weird
errors
{code}
Tests in error:
ElasticsearchBulkTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
Inconsiste...
ElasticsearchClusterIndexTest>ElasticsearchClusterBaseTest.cleanUpOnce:53 »
Verify
ElasticsearchGetSearchDeleteExistsUpdateTest>ElasticsearchBaseTest.cleanupOnce:44
» Verify
ElasticsearchIndexTest>ElasticsearchBaseTest.cleanupOnce:44 » Verify
Inconsist...
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
