[jira] [Updated] (CAMEL-11178) Default method is invisible during Camel Simple evaluation

[Anton Sulim (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Sulim updated CAMEL-11178:

Description: 
Issue can be reproduced with below unit test, I have not found it in tracker. 
Essence: interface A has default method, interface B extends A, default method 
is invisible during Simple language evaluation. 

{code:java}
import org.apache.camel.CamelContext;
import org.apache.camel.Exchange;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.impl.DefaultCamelContext;
import org.apache.camel.impl.DefaultExchange;
import org.junit.Assert;
import org.junit.Test;

public class DefaultMethodIsInvisibleTest {

public static interface A {
public default String defaultMethod() {
return "default method result";
}
}

public static interface B extends A {
}

@Test
public void camelSimpleDoesNotSeeDefaultMethod() throws Exception {
CamelContext context = new DefaultCamelContext();
context.addRoutes(new RouteBuilder() {
public void configure() {

from("direct:camelSimpleDoesNotSeeDefaultMethod").script().simple("${exchangeProperty.myObject.defaultMethod}");
}
});
context.start();

Exchange incomingExchange = new DefaultExchange(context);
incomingExchange.setProperty("myObject", new B() {
});

Exchange result = 
context.createProducerTemplate().send("direct:camelSimpleDoesNotSeeDefaultMethod",
 incomingExchange);

Assert.assertNull(result.getException());
}

}
{code}

Stacktrace:
{code}
Caused by: org.apache.camel.language.bean.RuntimeBeanExpressionException: 
Failed to invoke method: defaultMethod on null due to: 
org.apache.camel.component.bean.MethodNotFoundException: Method with name: 
defaultMethod not found on bean: 
com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2@5dafbe45 
of type: com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2. 
Exchange[][Message: [Body is null]]
at 
org.apache.camel.language.bean.BeanExpression$OgnlInvokeProcessor.process(BeanExpression.java:290)
at 
org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:114)
... 46 common frames omitted
Caused by: org.apache.camel.component.bean.MethodNotFoundException: Method with 
name: defaultMethod not found on bean: 
com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2@5dafbe45 
of type: com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2. 
Exchange[][Message: [Body is null]]
at 
org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:269)
at 
org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:183)
at 
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:159)
{code}

  was:
Issue can be reproduced with below unit test, I have not found it in tracker. 
Essence: interface A has default method, interface B extends A, default method 
is invisible during Simple language evaluation. 

{code:java}
import org.apache.camel.CamelContext;
import org.apache.camel.Exchange;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.impl.DefaultCamelContext;
import org.apache.camel.impl.DefaultExchange;
import org.junit.Assert;
import org.junit.Test;

public class DefaultMethodIsInvisibleTest {

public static interface A {
public default String defaultMethod() {
return "default method result";
}
}

public static interface B extends A {
}

@Test
public void camelSimpleDoesNotSeeDefaultMethod() throws Exception {
CamelContext context = new DefaultCamelContext();
context.addRoutes(new RouteBuilder() {
public void configure() {
from("direct:camelSimpleDoesNotSeeDefaultMethod").log("Result 
of default method invocation is ${exchangeProperty.myObject.defaultMethod}");
}
});
context.start();

Exchange incomingExchange = new DefaultExchange(context);
incomingExchange.setProperty("myObject", new B() {
});

Exchange result = 
context.createProducerTemplate().send("direct:camelSimpleDoesNotSeeDefaultMethod",
 incomingExchange);

Assert.assertNull(result.getException());
}

}
{code}

Stacktrace:
{code}
Caused by: org.apache.camel.language.bean.RuntimeBeanExpressionException: 
Failed to invoke method: defaultMethod on null due to: 
org.apache.camel.component.bean.MethodNotFoundException: Method with name: 
defaultMethod not found on bean: 
com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2@5dafbe45 
of type: com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2. 
Exchange[][Message: [Body is null]]
at 

[jira] [Created] (CAMEL-11183) Checkstyle errors in camel-package-maven-plugin

[Gregor Zurowski (JIRA)]

Gregor Zurowski created CAMEL-11183:
---

 Summary: Checkstyle errors in camel-package-maven-plugin
 Key: CAMEL-11183
 URL: https://issues.apache.org/jira/browse/CAMEL-11183
 Project: Camel
  Issue Type: Task
  Components: camel-package-maven-plugin
Affects Versions: 2.19.0
Reporter: Gregor Zurowski
Assignee: Gregor Zurowski
Priority: Minor


The following Checkstyle errors are reported for the camel-package-maven-plugin 
module:

{code}
[ERROR] 
C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PackageDataFormatMojo.java:105:5:
 Executable statement count is 101 (max allowed is 100). 
[ExecutableStatementCount]
[ERROR] 
C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PackageHelper.java:165:13:
 Boolean expression complexity is 7 (max allowed is 6). 
[BooleanExpressionComplexity]
[ERROR] 
C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PrepareCatalogKarafMojo.java:394:21:
 Boolean expression complexity is 9 (max allowed is 6). 
[BooleanExpressionComplexity]
[ERROR] 
C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PrepareCatalogMojo.java:323:5:
 Executable statement count is 109 (max allowed is 100). 
[ExecutableStatementCount]
[ERROR] 
C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PrepareCatalogMojo.java:795:21:
 Boolean expression complexity is 9 (max allowed is 6). 
[BooleanExpressionComplexity]
[ERROR] 
C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PrepareCatalogSpringBootMojo.java:426:21:
 Boolean expression complexity is 9 (max allowed is 6). 
[BooleanExpressionComplexity]
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (CAMEL-11183) Checkstyle errors in camel-package-maven-plugin

[Gregor Zurowski (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gregor Zurowski reassigned CAMEL-11183:
---

Assignee: (was: Gregor Zurowski)

> Checkstyle errors in camel-package-maven-plugin
> ---
>
> Key: CAMEL-11183
> URL: https://issues.apache.org/jira/browse/CAMEL-11183
> Project: Camel
>  Issue Type: Task
>  Components: camel-package-maven-plugin
>Affects Versions: 2.19.0
>Reporter: Gregor Zurowski
>Priority: Minor
>
> The following Checkstyle errors are reported for the 
> camel-package-maven-plugin module:
> {code}
> [ERROR] 
> C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PackageDataFormatMojo.java:105:5:
>  Executable statement count is 101 (max allowed is 100). 
> [ExecutableStatementCount]
> [ERROR] 
> C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PackageHelper.java:165:13:
>  Boolean expression complexity is 7 (max allowed is 6). 
> [BooleanExpressionComplexity]
> [ERROR] 
> C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PrepareCatalogKarafMojo.java:394:21:
>  Boolean expression complexity is 9 (max allowed is 6). 
> [BooleanExpressionComplexity]
> [ERROR] 
> C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PrepareCatalogMojo.java:323:5:
>  Executable statement count is 109 (max allowed is 100). 
> [ExecutableStatementCount]
> [ERROR] 
> C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PrepareCatalogMojo.java:795:21:
>  Boolean expression complexity is 9 (max allowed is 6). 
> [BooleanExpressionComplexity]
> [ERROR] 
> C:\var\git\camel\tooling\maven\camel-package-maven-plugin\src\main\java\org\apache\camel\maven\packaging\PrepareCatalogSpringBootMojo.java:426:21:
>  Boolean expression complexity is 9 (max allowed is 6). 
> [BooleanExpressionComplexity]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11182) SolrParams are not honored when sending SolrInputDocument.

[Chirag Anand (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chirag Anand updated CAMEL-11182:
-
Description: I have an update Processor chain which triggers during every 
update of the solr document which requires SolrParams to be passed. I noticed 
SolrParams is not applicable when trying to push SolrInputDocument(referring to 
SolrProducer.java). Can i submit a fix for this?   (was: I have an update 
Processor chain which triggers during every update of the solr document which 
requires SolrParams to be passed. I noticed SolrParams is not applicable when 
trying to push SolrInputSocument(referring to SolrProducer.java). Can i submit 
a fix for this? )

> SolrParams are not honored when sending SolrInputDocument.
> --
>
> Key: CAMEL-11182
> URL: https://issues.apache.org/jira/browse/CAMEL-11182
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-solr
>Affects Versions: 2.18.3
> Environment: Apache Solr , Apache Camel
>Reporter: Chirag Anand
>
> I have an update Processor chain which triggers during every update of the 
> solr document which requires SolrParams to be passed. I noticed SolrParams is 
> not applicable when trying to push SolrInputDocument(referring to 
> SolrProducer.java). Can i submit a fix for this? 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-11178) Default method is invisible during Camel Simple evaluation

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-11178.
-
   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: 2.18.3

> Default method is invisible during Camel Simple evaluation
> --
>
> Key: CAMEL-11178
> URL: https://issues.apache.org/jira/browse/CAMEL-11178
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.1
>Reporter: Anton Sulim
>Assignee: Claus Ibsen
> Fix For: 2.18.3
>
>
> Issue can be reproduced with below unit test, I have not found it in tracker. 
> Essence: interface A has default method, interface B extends A, default 
> method is invisible during Simple language evaluation. 
> {code:java}
> import org.apache.camel.CamelContext;
> import org.apache.camel.Exchange;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.impl.DefaultCamelContext;
> import org.apache.camel.impl.DefaultExchange;
> import org.junit.Assert;
> import org.junit.Test;
> public class DefaultMethodIsInvisibleTest {
> public static interface A {
> public default String defaultMethod() {
> return "default method result";
> }
> }
> public static interface B extends A {
> }
> @Test
> public void camelSimpleDoesNotSeeDefaultMethod() throws Exception {
> CamelContext context = new DefaultCamelContext();
> context.addRoutes(new RouteBuilder() {
> public void configure() {
> from("direct:camelSimpleDoesNotSeeDefaultMethod").log("Result 
> of default method invocation is ${exchangeProperty.myObject.defaultMethod}");
> }
> });
> context.start();
> Exchange incomingExchange = new DefaultExchange(context);
> incomingExchange.setProperty("myObject", new B() {
> });
> Exchange result = 
> context.createProducerTemplate().send("direct:camelSimpleDoesNotSeeDefaultMethod",
>  incomingExchange);
> Assert.assertNull(result.getException());
> }
> }
> {code}
> Stacktrace:
> {code}
> Caused by: org.apache.camel.language.bean.RuntimeBeanExpressionException: 
> Failed to invoke method: defaultMethod on null due to: 
> org.apache.camel.component.bean.MethodNotFoundException: Method with name: 
> defaultMethod not found on bean: 
> com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2@5dafbe45
>  of type: 
> com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2. 
> Exchange[][Message: [Body is null]]
> at 
> org.apache.camel.language.bean.BeanExpression$OgnlInvokeProcessor.process(BeanExpression.java:290)
> at 
> org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:114)
> ... 46 common frames omitted
> Caused by: org.apache.camel.component.bean.MethodNotFoundException: Method 
> with name: defaultMethod not found on bean: 
> com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2@5dafbe45
>  of type: 
> com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2. 
> Exchange[][Message: [Body is null]]
> at 
> org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:269)
> at 
> org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:183)
> at 
> org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:159)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-10141) Test Apache Camel on Java 9

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978715#comment-15978715
 ] 

ASF GitHub Bot commented on CAMEL-10141:


Github user johnpoth closed the pull request at:

https://github.com/apache/camel/pull/1653


> Test Apache Camel on Java 9
> ---
>
> Key: CAMEL-10141
> URL: https://issues.apache.org/jira/browse/CAMEL-10141
> Project: Camel
>  Issue Type: Test
>  Components: build system
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> To find out early if we have problems with Java 9 and Apache Camel.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-10141) Test Apache Camel on Java 9

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978686#comment-15978686
 ] 

ASF GitHub Bot commented on CAMEL-10141:


GitHub user johnpoth opened a pull request:

https://github.com/apache/camel/pull/1653

CAMEL-10141 upgrade to Java 9 build 165

This PR makes more modules unit tests pass on the latest Java 9 build 165

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnpoth/camel CAMEL-10141

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1653.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1653


commit 8f7c92b36156e1337a56fe1388ef40abad1f5d8d
Author: jpoth 
Date:   2017-04-18T18:27:19Z

CAMEL-10141: make camel-test tests pass on Java 9

commit ecbd9ff2515a1f17c525ca6f594a627c6b18d4cd
Author: jpoth 
Date:   2017-04-20T17:14:00Z

CAMEL-10141: make camel-example-rest-producer tests pass on Java 9

commit e37ef278e8169b5af49cd3114458ae9313e75e9d
Author: jpoth 
Date:   2017-04-21T10:11:45Z

CAMEL-10141: skip opentracing tests on Java 9 until Byteman upgrade to 4.x

commit e79925e1ccb764541a0c0ff4b367cd049ccad96b
Author: jpoth 
Date:   2017-04-21T10:13:55Z

CAMEL-10141: make camel-eip-documentation-enricher-maven-plugin tests pass 
on Java 9

commit 2f039df6ea133e570d42352ae9e6724f5f24c35a
Author: jpoth 
Date:   2017-04-21T12:47:06Z

CAMEL-10141: make camel-testng tests pass on Java 9

commit e76424ef50b8670144690ad90ec43a769ed4a57e
Author: jpoth 
Date:   2017-04-21T12:47:26Z

CAMEL-10141: make camel-test-spring tests pass on Java 9

commit 4d149be9c759394a5af53a3b648a917620d6e572
Author: jpoth 
Date:   2017-04-21T12:47:48Z

CAMEL-10141: make camel-spring-javaconfig tests pass on Java 9

commit 8272be50d8caa2430a8ea106e87f2dd2f74388ac
Author: jpoth 
Date:   2017-04-21T12:51:10Z

CAMEL-10141: make camel-spring tests pass on Java 9. This required the use 
of Java's native shemagen instead of jaxb-xjc's embedded schemagen which 
doesn't work on Java 9




> Test Apache Camel on Java 9
> ---
>
> Key: CAMEL-10141
> URL: https://issues.apache.org/jira/browse/CAMEL-10141
> Project: Camel
>  Issue Type: Test
>  Components: build system
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> To find out early if we have problems with Java 9 and Apache Camel.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11181) Replace gmaven with gmavenplus Maven plugin

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978575#comment-15978575
 ] 

ASF GitHub Bot commented on CAMEL-11181:


Github user zregvart closed the pull request at:

https://github.com/apache/camel/pull/1651


> Replace gmaven with gmavenplus Maven plugin
> ---
>
> Key: CAMEL-11181
> URL: https://issues.apache.org/jira/browse/CAMEL-11181
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Trivial
>
> See the discussion [Camel 2.19 
> Roadmap|http://camel.465427.n5.nabble.com/Camel-2-19-Roadmap-tp5792559p5798015.html]
>  on the camel-dev mailing list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11181) Replace gmaven with gmavenplus Maven plugin

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978445#comment-15978445
 ] 

ASF GitHub Bot commented on CAMEL-11181:


GitHub user zregvart opened a pull request:

https://github.com/apache/camel/pull/1651

CAMEL-11181 Replace gmaven with gmavenplus Maven plugin

This replaces the use of `gmaven` plugin with `gmavenplus` plugin.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zregvart/camel CAMEL-11181

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1651.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1651


commit 8d9c106588777b284299592555b9c4a18b1a4f0b
Author: Zoran Regvart 
Date:   2017-04-21T10:10:00Z

CAMEL-11181 Replace gmaven with gmavenplus Mave...

...n plugin

This replaces the use of `gmaven` plugin with `gmavenplus` plugin.




> Replace gmaven with gmavenplus Maven plugin
> ---
>
> Key: CAMEL-11181
> URL: https://issues.apache.org/jira/browse/CAMEL-11181
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Trivial
>
> See the discussion [Camel 2.19 
> Roadmap|http://camel.465427.n5.nabble.com/Camel-2-19-Roadmap-tp5792559p5798015.html]
>  on the camel-dev mailing list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11181) Replace gmaven with gmavenplus Maven plugin

[Zoran Regvart (JIRA)]

Zoran Regvart created CAMEL-11181:
-

 Summary: Replace gmaven with gmavenplus Maven plugin
 Key: CAMEL-11181
 URL: https://issues.apache.org/jira/browse/CAMEL-11181
 Project: Camel
  Issue Type: Task
  Components: build system
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Priority: Trivial


See the discussion [Camel 2.19 
Roadmap|http://camel.465427.n5.nabble.com/Camel-2-19-Roadmap-tp5792559p5798015.html]
 on the camel-dev mailing list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11179) MultiThread race condition in DefaultShutdownStrategy for suspend/resume

[Benjamin Graf (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978440#comment-15978440
 ] 

Benjamin Graf commented on CAMEL-11179:
---

Well, timeout is used by default (300s) and there does not a exist a 
"forceSuspend" feature. Therefor this can only be avoided by setting default 
timeout to infinity? Not a good idea.

> MultiThread race condition in DefaultShutdownStrategy for suspend/resume
> 
>
> Key: CAMEL-11179
> URL: https://issues.apache.org/jira/browse/CAMEL-11179
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.18.3
>Reporter: Benjamin Graf
>Priority: Minor
>
> If call to suspend with timeout does timeout than two threads are invoking 
> forced processing one for suspending and one for hard stopping. This causes 
> the Consumer to be possibly left in a dead state.
> E.g. Jms consuming route:
> # Timeout occurs, ShutdownTask gets completed before main thread
> -> JmsConsumer gets stopped (listener gets destroyed), resume has no effect
> # Timeout occurs, ShutdownTask get completet after main thread
> -> JmsConsumer gets stopped first (listener gets destroyed) and get suspended 
> second, resume sets Consumer to started but the listener is still destroyed!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-11180) Place Eclipse workspace setup in camel-etc in a profile

[Zoran Regvart (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart resolved CAMEL-11180.
---
   Resolution: Done
Fix Version/s: 2.19.0

> Place Eclipse workspace setup in camel-etc in a profile
> ---
>
> Key: CAMEL-11180
> URL: https://issues.apache.org/jira/browse/CAMEL-11180
> Project: Camel
>  Issue Type: Task
>  Components: tooling
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Trivial
> Fix For: 2.19.0
>
>
> See the discussion on [To put eclipse setup in camel-etc in profile? 
> |http://camel.465427.n5.nabble.com/To-put-eclipse-setup-in-camel-etc-in-profile-tp5797966.html]
>  at the camel-dev mailing list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-10798) camel-twitter, camel-ignite - Make the uri endpoints separated

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-10798:
-
Fix Version/s: (was: 2.19.0)
   Future

> camel-twitter, camel-ignite - Make the uri endpoints separated
> --
>
> Key: CAMEL-10798
> URL: https://issues.apache.org/jira/browse/CAMEL-10798
> Project: Camel
>  Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Tomohisa Igarashi
> Fix For: Future
>
>
> They currently have the same @UriEndpoint that represents all of their 
> possible endpoint combinations. This usually works fine for Camel components. 
> But some components such as twitter, ignite, hazelcast etc do have to many 
> different endpoints that have very specific options per different endpoint.
> We should split up this in different components so they are separated.
> So we have
> twitter-status
> twitter-search
> twitter-direct
> Or something.
> This will also help tooling, documentation, et all so they are clearly 
> separated and there are no confusion. For example twitter mention do not 
> support the delay option which only twitter search uses etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-11150) camel-ignite is removed from readme on each full build

[Tomohisa Igarashi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomohisa Igarashi resolved CAMEL-11150.
---
   Resolution: Fixed
Fix Version/s: 2.19.0

It has been fixed as a part of CAMEL-10798.
https://github.com/apache/camel/pull/1648

> camel-ignite is removed from readme on each full build
> --
>
> Key: CAMEL-11150
> URL: https://issues.apache.org/jira/browse/CAMEL-11150
> Project: Camel
>  Issue Type: Task
>  Components: documentation
>Reporter: Tomohisa Igarashi
>Assignee: Tomohisa Igarashi
>Priority: Minor
> Fix For: 2.19.0
>
>
> On each full build camel-solr is removed from components/readme.adoc and 
> docs/user-manual/en/SUMMARY.md which shouldn't happen.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-10798) camel-twitter, camel-ignite - Make the uri endpoints separated

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-10798:
-
Fix Version/s: (was: 3.0.0)
   2.19.0

> camel-twitter, camel-ignite - Make the uri endpoints separated
> --
>
> Key: CAMEL-10798
> URL: https://issues.apache.org/jira/browse/CAMEL-10798
> Project: Camel
>  Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Tomohisa Igarashi
> Fix For: 2.19.0
>
>
> They currently have the same @UriEndpoint that represents all of their 
> possible endpoint combinations. This usually works fine for Camel components. 
> But some components such as twitter, ignite, hazelcast etc do have to many 
> different endpoints that have very specific options per different endpoint.
> We should split up this in different components so they are separated.
> So we have
> twitter-status
> twitter-search
> twitter-direct
> Or something.
> This will also help tooling, documentation, et all so they are clearly 
> separated and there are no confusion. For example twitter mention do not 
> support the delay option which only twitter search uses etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-10798) camel-twitter, camel-ignite - Make the uri endpoints separated

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978381#comment-15978381
 ] 

ASF GitHub Bot commented on CAMEL-10798:


Github user igarashitm closed the pull request at:

https://github.com/apache/camel/pull/1648


> camel-twitter, camel-ignite - Make the uri endpoints separated
> --
>
> Key: CAMEL-10798
> URL: https://issues.apache.org/jira/browse/CAMEL-10798
> Project: Camel
>  Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Tomohisa Igarashi
> Fix For: 2.19.0
>
>
> They currently have the same @UriEndpoint that represents all of their 
> possible endpoint combinations. This usually works fine for Camel components. 
> But some components such as twitter, ignite, hazelcast etc do have to many 
> different endpoints that have very specific options per different endpoint.
> We should split up this in different components so they are separated.
> So we have
> twitter-status
> twitter-search
> twitter-direct
> Or something.
> This will also help tooling, documentation, et all so they are clearly 
> separated and there are no confusion. For example twitter mention do not 
> support the delay option which only twitter search uses etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CAMEL-11180) Place Eclipse workspace setup in camel-etc in a profile

[Zoran Regvart (JIRA)]

Zoran Regvart created CAMEL-11180:
-

 Summary: Place Eclipse workspace setup in camel-etc in a profile
 Key: CAMEL-11180
 URL: https://issues.apache.org/jira/browse/CAMEL-11180
 Project: Camel
  Issue Type: Task
  Components: tooling
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Priority: Trivial


See the discussion on [To put eclipse setup in camel-etc in profile? 
|http://camel.465427.n5.nabble.com/To-put-eclipse-setup-in-camel-etc-in-profile-tp5797966.html]
 at the camel-dev mailing list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-10985) camel-coap fails to return results when enableCORS(true) is set

[James Netherton (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978341#comment-15978341
 ] 

James Netherton commented on CAMEL-10985:
-

Ok, I'll take a peek at it early next week.

> camel-coap fails to return results when enableCORS(true) is set
> ---
>
> Key: CAMEL-10985
> URL: https://issues.apache.org/jira/browse/CAMEL-10985
> Project: Camel
>  Issue Type: Bug
>  Components: camel-coap
>Affects Versions: 2.19.0
>Reporter: Scott Cranton
>Priority: Minor
>
> In the CoAPRestVerbTest, if you add to the restConfiguration() 
> .enableCORS(true), then all of the unit tests that return a result fail as no 
> response is returned
> https://github.com/apache/camel/blob/master/components/camel-coap/src/test/java/org/apache/camel/coap/CoAPRestVerbTest.java#L106



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-10985) camel-coap fails to return results when enableCORS(true) is set

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978306#comment-15978306
 ] 

Claus Ibsen commented on CAMEL-10985:
-

[~jamesnetherton] in case you want to have more fun with camel-coap then we 
have this ticket

> camel-coap fails to return results when enableCORS(true) is set
> ---
>
> Key: CAMEL-10985
> URL: https://issues.apache.org/jira/browse/CAMEL-10985
> Project: Camel
>  Issue Type: Bug
>  Components: camel-coap
>Affects Versions: 2.19.0
>Reporter: Scott Cranton
>Priority: Minor
>
> In the CoAPRestVerbTest, if you add to the restConfiguration() 
> .enableCORS(true), then all of the unit tests that return a result fail as no 
> response is returned
> https://github.com/apache/camel/blob/master/components/camel-coap/src/test/java/org/apache/camel/coap/CoAPRestVerbTest.java#L106



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-10985) camel-coap fails to return results when enableCORS(true) is set

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978305#comment-15978305
 ] 

Claus Ibsen commented on CAMEL-10985:
-

Wonder if the recent fix in camel-coap may have improved this? We can test on 
master.

> camel-coap fails to return results when enableCORS(true) is set
> ---
>
> Key: CAMEL-10985
> URL: https://issues.apache.org/jira/browse/CAMEL-10985
> Project: Camel
>  Issue Type: Bug
>  Components: camel-coap
>Affects Versions: 2.19.0
>Reporter: Scott Cranton
>Priority: Minor
>
> In the CoAPRestVerbTest, if you add to the restConfiguration() 
> .enableCORS(true), then all of the unit tests that return a result fail as no 
> response is returned
> https://github.com/apache/camel/blob/master/components/camel-coap/src/test/java/org/apache/camel/coap/CoAPRestVerbTest.java#L106



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11172) Java 9 - camel-restdsl-swagger-plugin fails integration test and camel-example-kotlin cannot compile

[John Poth (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978297#comment-15978297
 ] 

John Poth commented on CAMEL-11172:
---

Great! I think I'll have my fixes ready by the EOD.

> Java 9 - camel-restdsl-swagger-plugin fails integration test and 
> camel-example-kotlin cannot compile
> 
>
> Key: CAMEL-11172
> URL: https://issues.apache.org/jira/browse/CAMEL-11172
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.19.0
>Reporter: Claus Ibsen
> Fix For: 2.19.0
>
>
> See the CI output
> https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.notest.java9/185/consoleText



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11172) Java 9 - camel-restdsl-swagger-plugin fails integration test and camel-example-kotlin cannot compile

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11172:

Fix Version/s: (was: 2.20.0)

> Java 9 - camel-restdsl-swagger-plugin fails integration test and 
> camel-example-kotlin cannot compile
> 
>
> Key: CAMEL-11172
> URL: https://issues.apache.org/jira/browse/CAMEL-11172
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.19.0
>Reporter: Claus Ibsen
> Fix For: 2.19.0
>
>
> See the CI output
> https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.notest.java9/185/consoleText



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11176) Remove @Ignore on Camel Catalog Maven tests

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11176:

Component/s: camel-catalog

> Remove @Ignore on Camel Catalog Maven tests
> ---
>
> Key: CAMEL-11176
> URL: https://issues.apache.org/jira/browse/CAMEL-11176
> Project: Camel
>  Issue Type: Task
>  Components: camel-catalog
>Affects Versions: 2.19.0
>Reporter: Aurelien Pupier
> Fix For: Future
>
>
> they currently have several requirements to work that are not expressed in 
> the code:
> - my-foo-connector
> - dummy-component
> - several versions of  Camel Catalog



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11176) Remove @Ignore on Camel Catalog Maven tests

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11176:

Fix Version/s: Future

> Remove @Ignore on Camel Catalog Maven tests
> ---
>
> Key: CAMEL-11176
> URL: https://issues.apache.org/jira/browse/CAMEL-11176
> Project: Camel
>  Issue Type: Task
>  Components: camel-catalog
>Affects Versions: 2.19.0
>Reporter: Aurelien Pupier
>Priority: Minor
> Fix For: Future
>
>
> they currently have several requirements to work that are not expressed in 
> the code:
> - my-foo-connector
> - dummy-component
> - several versions of  Camel Catalog



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11176) Remove @Ignore on Camel Catalog Maven tests

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11176:

Priority: Minor  (was: Major)

> Remove @Ignore on Camel Catalog Maven tests
> ---
>
> Key: CAMEL-11176
> URL: https://issues.apache.org/jira/browse/CAMEL-11176
> Project: Camel
>  Issue Type: Task
>  Components: camel-catalog
>Affects Versions: 2.19.0
>Reporter: Aurelien Pupier
>Priority: Minor
> Fix For: Future
>
>
> they currently have several requirements to work that are not expressed in 
> the code:
> - my-foo-connector
> - dummy-component
> - several versions of  Camel Catalog



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11179) MultiThread race condition in DefaultShutdownStrategy for suspend/resume

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11179:

Priority: Minor  (was: Major)

> MultiThread race condition in DefaultShutdownStrategy for suspend/resume
> 
>
> Key: CAMEL-11179
> URL: https://issues.apache.org/jira/browse/CAMEL-11179
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.18.3
>Reporter: Benjamin Graf
>Priority: Minor
>
> If call to suspend with timeout does timeout than two threads are invoking 
> forced processing one for suspending and one for hard stopping. This causes 
> the Consumer to be possibly left in a dead state.
> E.g. Jms consuming route:
> # Timeout occurs, ShutdownTask gets completed before main thread
> -> JmsConsumer gets stopped (listener gets destroyed), resume has no effect
> # Timeout occurs, ShutdownTask get completet after main thread
> -> JmsConsumer gets stopped first (listener gets destroyed) and get suspended 
> second, resume sets Consumer to started but the listener is still destroyed!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11178) Default method is invisible during Camel Simple evaluation

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978273#comment-15978273
 ] 

Claus Ibsen commented on CAMEL-11178:
-

Okay that is fine then you likely need to upgrade to have it working for you. 
It may also work on latest 2.17.x but I dont know.

> Default method is invisible during Camel Simple evaluation
> --
>
> Key: CAMEL-11178
> URL: https://issues.apache.org/jira/browse/CAMEL-11178
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.1
>Reporter: Anton Sulim
>
> Issue can be reproduced with below unit test, I have not found it in tracker. 
> Essence: interface A has default method, interface B extends A, default 
> method is invisible during Simple language evaluation. 
> {code:java}
> import org.apache.camel.CamelContext;
> import org.apache.camel.Exchange;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.impl.DefaultCamelContext;
> import org.apache.camel.impl.DefaultExchange;
> import org.junit.Assert;
> import org.junit.Test;
> public class DefaultMethodIsInvisibleTest {
> public static interface A {
> public default String defaultMethod() {
> return "default method result";
> }
> }
> public static interface B extends A {
> }
> @Test
> public void camelSimpleDoesNotSeeDefaultMethod() throws Exception {
> CamelContext context = new DefaultCamelContext();
> context.addRoutes(new RouteBuilder() {
> public void configure() {
> from("direct:camelSimpleDoesNotSeeDefaultMethod").log("Result 
> of default method invocation is ${exchangeProperty.myObject.defaultMethod}");
> }
> });
> context.start();
> Exchange incomingExchange = new DefaultExchange(context);
> incomingExchange.setProperty("myObject", new B() {
> });
> Exchange result = 
> context.createProducerTemplate().send("direct:camelSimpleDoesNotSeeDefaultMethod",
>  incomingExchange);
> Assert.assertNull(result.getException());
> }
> }
> {code}
> Stacktrace:
> {code}
> Caused by: org.apache.camel.language.bean.RuntimeBeanExpressionException: 
> Failed to invoke method: defaultMethod on null due to: 
> org.apache.camel.component.bean.MethodNotFoundException: Method with name: 
> defaultMethod not found on bean: 
> com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2@5dafbe45
>  of type: 
> com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2. 
> Exchange[][Message: [Body is null]]
> at 
> org.apache.camel.language.bean.BeanExpression$OgnlInvokeProcessor.process(BeanExpression.java:290)
> at 
> org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:114)
> ... 46 common frames omitted
> Caused by: org.apache.camel.component.bean.MethodNotFoundException: Method 
> with name: defaultMethod not found on bean: 
> com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2@5dafbe45
>  of type: 
> com.ubs.wma.gfi.tradersbook.subscriber.DefaultMethodIsInvisibleTest$2. 
> Exchange[][Message: [Body is null]]
> at 
> org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:269)
> at 
> org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:183)
> at 
> org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:159)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CAMEL-11177) CoAP component starts redundant server instance

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-11177.
--
Resolution: Fixed

> CoAP component starts redundant server instance
> ---
>
> Key: CAMEL-11177
> URL: https://issues.apache.org/jira/browse/CAMEL-11177
> Project: Camel
>  Issue Type: Bug
>  Components: camel-coap
>Affects Versions: 2.18.3, 2.19.0
>Reporter: James Netherton
>Assignee: Andrea Cosentino
> Fix For: 2.19.0
>
>
> If I configure a simple camel-coap consumer endpoint like:
> {code}
> from("coap://localhost:8080/foo")
> {code}
> Logging reveals that two server instances were started:
> {code}
> [org.eclipse.californium.core.network.CoapEndpoint] (pool-3-thread-1) 
> Stopping endpoint at address 0.0.0.0/0.0.0.0:52697
> [org.eclipse.californium.core.network.CoapEndpoint] (pool-3-thread-1) 
> Stopping endpoint at address 0.0.0.0/0.0.0.0:8080 
> {code}
> [This|https://github.com/apache/camel/blob/master/components/camel-coap/src/main/java/org/apache/camel/coap/CoAPComponent.java#L148-L153]
>  appears to be the logic that causes the behaviour. 
> Do we need it? It seems to be a duplicate of what already happens in 
> {{createConsumer()}}. Also, the creation of a default server can easily be 
> done in the {{createServer()}} method, I don't think we need it in 
> {{doStart()}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CAMEL-11177) CoAP component starts redundant server instance

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-11177:
-
Fix Version/s: 2.19.0

> CoAP component starts redundant server instance
> ---
>
> Key: CAMEL-11177
> URL: https://issues.apache.org/jira/browse/CAMEL-11177
> Project: Camel
>  Issue Type: Bug
>  Components: camel-coap
>Affects Versions: 2.18.3, 2.19.0
>Reporter: James Netherton
>Assignee: Andrea Cosentino
> Fix For: 2.19.0
>
>
> If I configure a simple camel-coap consumer endpoint like:
> {code}
> from("coap://localhost:8080/foo")
> {code}
> Logging reveals that two server instances were started:
> {code}
> [org.eclipse.californium.core.network.CoapEndpoint] (pool-3-thread-1) 
> Stopping endpoint at address 0.0.0.0/0.0.0.0:52697
> [org.eclipse.californium.core.network.CoapEndpoint] (pool-3-thread-1) 
> Stopping endpoint at address 0.0.0.0/0.0.0.0:8080 
> {code}
> [This|https://github.com/apache/camel/blob/master/components/camel-coap/src/main/java/org/apache/camel/coap/CoAPComponent.java#L148-L153]
>  appears to be the logic that causes the behaviour. 
> Do we need it? It seems to be a duplicate of what already happens in 
> {{createConsumer()}}. Also, the creation of a default server can easily be 
> done in the {{createServer()}} method, I don't think we need it in 
> {{doStart()}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CAMEL-11177) CoAP component starts redundant server instance

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978210#comment-15978210
 ] 

ASF GitHub Bot commented on CAMEL-11177:


Github user asfgit closed the pull request at:

https://github.com/apache/camel/pull/1647


> CoAP component starts redundant server instance
> ---
>
> Key: CAMEL-11177
> URL: https://issues.apache.org/jira/browse/CAMEL-11177
> Project: Camel
>  Issue Type: Bug
>  Components: camel-coap
>Affects Versions: 2.18.3, 2.19.0
>Reporter: James Netherton
>Assignee: Andrea Cosentino
>
> If I configure a simple camel-coap consumer endpoint like:
> {code}
> from("coap://localhost:8080/foo")
> {code}
> Logging reveals that two server instances were started:
> {code}
> [org.eclipse.californium.core.network.CoapEndpoint] (pool-3-thread-1) 
> Stopping endpoint at address 0.0.0.0/0.0.0.0:52697
> [org.eclipse.californium.core.network.CoapEndpoint] (pool-3-thread-1) 
> Stopping endpoint at address 0.0.0.0/0.0.0.0:8080 
> {code}
> [This|https://github.com/apache/camel/blob/master/components/camel-coap/src/main/java/org/apache/camel/coap/CoAPComponent.java#L148-L153]
>  appears to be the logic that causes the behaviour. 
> Do we need it? It seems to be a duplicate of what already happens in 
> {{createConsumer()}}. Also, the creation of a default server can easily be 
> done in the {{createServer()}} method, I don't think we need it in 
> {{doStart()}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)