[jira] [Work logged] (CAMEL-12947) MockEndpoint.expectedHeaderReceived should fail when no exchange received
[
https://issues.apache.org/jira/browse/CAMEL-12947?focusedWorklogId=260729&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-260729
]
ASF GitHub Bot logged work on CAMEL-12947:
--
Author: ASF GitHub Bot
Created on: 14/Jun/19 21:35
Start Date: 14/Jun/19 21:35
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #2977:
CAMEL-12947:MockEndpoint.expectedHeaderReceived should fail when no e…
URL: https://github.com/apache/camel/pull/2977
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 260729)
Time Spent: 1h (was: 50m)
> MockEndpoint.expectedHeaderReceived should fail when no exchange received
> -
>
> Key: CAMEL-12947
> URL: https://issues.apache.org/jira/browse/CAMEL-12947
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.22.1
>Reporter: Antoine Wils
>Assignee: Ramu
>Priority: Minor
> Fix For: 3.0.0, 2.24.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When expecting headers to be passed to a MockEndpoint that is never called
> the test should fail if the MockEndpoint was never called.
> However it is succeeding.
> Here an example of Junit 4 test succeeding when it should fail
> {code:java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> public class Test extends CamelTestSupport {
> @EndpointInject(uri = "mock:direct:foo")
> private MockEndpoint fooProducerMock;
> @Override
> public RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {}
> };
> }
> @Test
> public void failWhenHeaderAbsent() throws InterruptedException {
> fooProducerMock.expectedHeaderReceived("ghost", "you should be visible");
> MockEndpoint.assertIsSatisfied(context);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13038) Type Convert Problem for XQuery Build In founction
[
https://issues.apache.org/jira/browse/CAMEL-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CAMEL-13038.
--
Resolution: Information Provided
> Type Convert Problem for XQuery Build In founction
> --
>
> Key: CAMEL-13038
> URL: https://issues.apache.org/jira/browse/CAMEL-13038
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 2.22.2
>Reporter: W.Y
>Priority: Minor
> Attachments: xquerytest.zip
>
>
> when we send XML message to XQuery endpoint, it has problem with XML parsing
> Im XQuery the build in function looks like below :
> declare variable $in.body as element(*) external;
> return xf:my_xquery_function($request)
>
> the exception we got looks like
>
> org.apache.camel.RuntimeExpressionException:
> net.sf.saxon.trans.XPathException: Required item type of value of variable
> $in.body is element(); supplied value has item type
> Q{http://saxon.sf.net/java-t
> ype}org.apache.camel.converter.stream.CachedOutputStream-WrappedInputStream
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:155)
> ~[classes!/:na]
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:120)
> ~[classes!/:na]
> at
> org.apache.camel.processor.TransformProcessor.process(TransformProcessor.java:50)
> ~[camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:117)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.asyncInvoke(CxfConsumer.java:185)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:161)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_121]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_121]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(ServiceInvokerInterceptor.java:126)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:131)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
> [cxf-rt-transports-http-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:247)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:79)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> [jetty-server-9.4.11.v20180605.jar!/:9.4.11.v20180605]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
> [jetty-server-9.4.11.v20180605.jar!/:9.4.11.v201806
[jira] [Commented] (CAMEL-13038) Type Convert Problem for XQuery Build In founction
[
https://issues.apache.org/jira/browse/CAMEL-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864405#comment-16864405
]
Freeman Fang commented on CAMEL-13038:
--
I'd like to close this one for now.
> Type Convert Problem for XQuery Build In founction
> --
>
> Key: CAMEL-13038
> URL: https://issues.apache.org/jira/browse/CAMEL-13038
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 2.22.2
>Reporter: W.Y
>Priority: Minor
> Attachments: xquerytest.zip
>
>
> when we send XML message to XQuery endpoint, it has problem with XML parsing
> Im XQuery the build in function looks like below :
> declare variable $in.body as element(*) external;
> return xf:my_xquery_function($request)
>
> the exception we got looks like
>
> org.apache.camel.RuntimeExpressionException:
> net.sf.saxon.trans.XPathException: Required item type of value of variable
> $in.body is element(); supplied value has item type
> Q{http://saxon.sf.net/java-t
> ype}org.apache.camel.converter.stream.CachedOutputStream-WrappedInputStream
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:155)
> ~[classes!/:na]
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:120)
> ~[classes!/:na]
> at
> org.apache.camel.processor.TransformProcessor.process(TransformProcessor.java:50)
> ~[camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:117)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.asyncInvoke(CxfConsumer.java:185)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:161)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_121]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_121]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(ServiceInvokerInterceptor.java:126)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:131)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
> [cxf-rt-transports-http-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:247)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:79)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> [jetty-server-9.4.11.v20180605.jar!/:9.4.11.v20180605]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257
[jira] [Resolved] (CAMEL-13637) be able to enable access log for camel-undertow consumer endpoint
[ https://issues.apache.org/jira/browse/CAMEL-13637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13637. -- Resolution: Fixed > be able to enable access log for camel-undertow consumer endpoint > - > > Key: CAMEL-13637 > URL: https://issues.apache.org/jira/browse/CAMEL-13637 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0 > > > add a option/flag so we can configure camel-undertow consumer endpoint to > enable access log per each request -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13637) be able to enable access log for camel-undertow consumer endpoint
[ https://issues.apache.org/jira/browse/CAMEL-13637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864404#comment-16864404 ] Freeman Fang commented on CAMEL-13637: -- Hi [~bedla], Yup, the AccessLogReceiver is pluggable. Cheers Freeman > be able to enable access log for camel-undertow consumer endpoint > - > > Key: CAMEL-13637 > URL: https://issues.apache.org/jira/browse/CAMEL-13637 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0 > > > add a option/flag so we can configure camel-undertow consumer endpoint to > enable access log per each request -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13649) Enhance documentation for twitter search of multiple words
[ https://issues.apache.org/jira/browse/CAMEL-13649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Miranda updated CAMEL-13649: Description: To search tweets with multiple words the comma is not a valid character separator, it should use the [twitter search standard operators|https://developer.twitter.com/en/docs/tweets/search/guides/standard-operators]. The documentation should be changed to let users know how to use twitter search operators. Examples of a search query: * java OR scala * (apache camel) AND integration * camel -knative was: To search tweets with multiple words the comma is not a valid character separator, it should use the [twitter search standard operators|https://developer.twitter.com/en/docs/tweets/search/guides/standard-operators]. The documentation should be changed to let users know how to use twitter search operators. Examples of a search query: * `java OR scala` * `(apache camel) AND integration` * `camel -knative` > Enhance documentation for twitter search of multiple words > -- > > Key: CAMEL-13649 > URL: https://issues.apache.org/jira/browse/CAMEL-13649 > Project: Camel > Issue Type: Improvement > Components: camel-twitter >Reporter: Claudio Miranda >Priority: Major > > To search tweets with multiple words the comma is not a valid character > separator, it should use the [twitter search standard > operators|https://developer.twitter.com/en/docs/tweets/search/guides/standard-operators]. > The documentation should be changed to let users know how to use twitter > search operators. Examples of a search query: > * java OR scala > * (apache camel) AND integration > * camel -knative -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13649) Enhance documentation for twitter search of multiple words
Claudio Miranda created CAMEL-13649: --- Summary: Enhance documentation for twitter search of multiple words Key: CAMEL-13649 URL: https://issues.apache.org/jira/browse/CAMEL-13649 Project: Camel Issue Type: Improvement Components: camel-twitter Reporter: Claudio Miranda To search tweets with multiple words the comma is not a valid character separator, it should use the [twitter search standard operators|https://developer.twitter.com/en/docs/tweets/search/guides/standard-operators]. The documentation should be changed to let users know how to use twitter search operators. Examples of a search query: * `java OR scala` * `(apache camel) AND integration` * `camel -knative` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13638) camel-salesforce - Lookups to polymorphic relationship fields must include an attributes object with a type property
[
https://issues.apache.org/jira/browse/CAMEL-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864216#comment-16864216
]
Alex Dettinger commented on CAMEL-13638:
I fixed test expected with [this
commit|https://github.com/apache/camel/commit/f3a6a9b1c07c20a418a018ad9c7b0fd1aba84496]
on master only as I was not able to find the backport in 2.24.x.
> camel-salesforce - Lookups to polymorphic relationship fields must include an
> attributes object with a type property
>
>
> Key: CAMEL-13638
> URL: https://issues.apache.org/jira/browse/CAMEL-13638
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
>Affects Versions: 2.24.0, 3.0.0-M2
>Reporter: Jeremy Ross
>Priority: Major
> Fix For: 2.24.1, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When referencing a related record that is a polymorphic lookup, the JSON must
> include an {{attributes}} object with a {{type}} property indicating which
> type of Object is being referenced.
> E.g.:
> {code:json}
> {
> "Description": "Contact HR for further information",
> "Status": "Completed",
> "Who": {
> "attributes": {
> "type": "Contact"
> },
> "External_Id_Field__c": "cfcec54d-5d77-4ffa-a2ec-7fa2ce0e9616"
> },
> "Subject": "Comment"
> }
> {code}
> This {{attributes}} object is optional for non-polymorphic lookups, so no
> harm in including it in all lookups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13638) camel-salesforce - Lookups to polymorphic relationship fields must include an attributes object with a type property
[
https://issues.apache.org/jira/browse/CAMEL-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger updated CAMEL-13638:
---
Fix Version/s: (was: 3.0.0-M3)
3.0.0.M4
> camel-salesforce - Lookups to polymorphic relationship fields must include an
> attributes object with a type property
>
>
> Key: CAMEL-13638
> URL: https://issues.apache.org/jira/browse/CAMEL-13638
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
>Affects Versions: 2.24.0, 3.0.0-M2
>Reporter: Jeremy Ross
>Priority: Major
> Fix For: 2.24.1, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When referencing a related record that is a polymorphic lookup, the JSON must
> include an {{attributes}} object with a {{type}} property indicating which
> type of Object is being referenced.
> E.g.:
> {code:json}
> {
> "Description": "Contact HR for further information",
> "Status": "Completed",
> "Who": {
> "attributes": {
> "type": "Contact"
> },
> "External_Id_Field__c": "cfcec54d-5d77-4ffa-a2ec-7fa2ce0e9616"
> },
> "Subject": "Comment"
> }
> {code}
> This {{attributes}} object is optional for non-polymorphic lookups, so no
> harm in including it in all lookups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864147#comment-16864147
]
Andrea Cosentino commented on CAMEL-13648:
--
Here is an example on master:
[https://github.com/apache/camel/commit/aa96707b29b32be70135c3a252da442d8970e330]
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> I am trying to call an external service with some dynamic uri which will be
> comming in request e.g www.abc.com/{id} i get that id in ${header.id} which
> is perfectly log in console but when i am trying to use netty4-http component
> in camel i used same dynamic uri in path of configuration but i am getting
> error of 404 not found because the url is not properly made.
> It is not using simple expression language like "${header.id}" or any
> placeholder like "{{id}}" and also not work with this "{id}"
> I am using blue print dsl in redhat code ready studio 12.11.0 GA
> The main problem is how to use dynamic uri with netty4-http component in
> camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864090#comment-16864090
]
Andrea Cosentino commented on CAMEL-13648:
--
Anyway please show the route in your email on the users mailing list thread
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> I am trying to call an external service with some dynamic uri which will be
> comming in request e.g www.abc.com/{id} i get that id in ${header.id} which
> is perfectly log in console but when i am trying to use netty4-http component
> in camel i used same dynamic uri in path of configuration but i am getting
> error of 404 not found because the url is not properly made.
> It is not using simple expression language like "${header.id}" or any
> placeholder like "{{id}}" and also not work with this "{id}"
> I am using blue print dsl in redhat code ready studio 12.11.0 GA
> The main problem is how to use dynamic uri with netty4-http component in
> camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864033#comment-16864033
]
Andrea Cosentino edited comment on CAMEL-13648 at 6/14/19 12:59 PM:
Don't reopen and ask on the users mailing list first. Please.
If this is a bug we can reopen this. Follow the rules.
was (Author: ancosen):
Don't reopen and ask on the users mailing list. Please.
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> I am trying to call an external service with some dynamic uri which will be
> comming in request e.g www.abc.com/{id} i get that id in ${header.id} which
> is perfectly log in console but when i am trying to use netty4-http component
> in camel i used same dynamic uri in path of configuration but i am getting
> error of 404 not found because the url is not properly made.
> It is not using simple expression language like "${header.id}" or any
> placeholder like "{{id}}" and also not work with this "{id}"
> I am using blue print dsl in redhat code ready studio 12.11.0 GA
> The main problem is how to use dynamic uri with netty4-http component in
> camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13648.
--
Resolution: Invalid
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> I am trying to call an external service with some dynamic uri which will be
> comming in request e.g www.abc.com/{id} i get that id in ${header.id} which
> is perfectly log in console but when i am trying to use netty4-http component
> in camel i used same dynamic uri in path of configuration but i am getting
> error of 404 not found because the url is not properly made.
> It is not using simple expression language like "${header.id}" or any
> placeholder like "{{id}}" and also not work with this "{id}"
> I am using blue print dsl in redhat code ready studio 12.11.0 GA
> The main problem is how to use dynamic uri with netty4-http component in
> camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864033#comment-16864033
]
Andrea Cosentino commented on CAMEL-13648:
--
Don't reopen and ask on the users mailing list. Please.
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> I am trying to call an external service with some dynamic uri which will be
> comming in request e.g www.abc.com/{id} i get that id in ${header.id} which
> is perfectly log in console but when i am trying to use netty4-http component
> in camel i used same dynamic uri in path of configuration but i am getting
> error of 404 not found because the url is not properly made.
> It is not using simple expression language like "${header.id}" or any
> placeholder like "{{id}}" and also not work with this "{id}"
> I am using blue print dsl in redhat code ready studio 12.11.0 GA
> The main problem is how to use dynamic uri with netty4-http component in
> camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Muhammad Zubair reopened CAMEL-13648:
-
I am trying to call an external service with some dynamic uri which will be
comming in request e.g www.abc.com/{id} i get that id in ${header.id} which is
perfectly log in console but when i am trying to use netty4-http component in
camel i used same dynamic uri in path of configuration but i am getting error
of 404 not found because the url is not properly made.
It is not using simple expression language like "${header.id}" or any
placeholder like "{{id}}" and also not work with this "{id}"
I am using blue print dsl in redhat code ready studio 12.11.0 GA
The main problem is how to use dynamic uri with netty4-http component in camel.
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> I am trying to call an external service with some dynamic uri which will be
> comming in request e.g www.abc.com/{id} i get that id in ${header.id} which
> is perfectly log in console but when i am trying to use netty4-http component
> in camel i used same dynamic uri in path of configuration but i am getting
> error of 404 not found because the url is not properly made.
> It is not using simple expression language like "${header.id}" or any
> placeholder like "{{id}}" and also not work with this "{id}"
> I am using blue print dsl in redhat code ready studio 12.11.0 GA
> The main problem is how to use dynamic uri with netty4-http component in
> camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Muhammad Zubair updated CAMEL-13648:
Description:
I am trying to call an external service with some dynamic uri which will be
comming in request e.g www.abc.com/{id} i get that id in ${header.id} which is
perfectly log in console but when i am trying to use netty4-http component in
camel i used same dynamic uri in path of configuration but i am getting error
of 404 not found because the url is not properly made.
It is not using simple expression language like "${header.id}" or any
placeholder like "{{id}}" and also not work with this "{id}"
I am using blue print dsl in redhat code ready studio 12.11.0 GA
The main problem is how to use dynamic uri with netty4-http component in camel.
was:
how to use dynamic uri in path of netty4-http component.
while setting dynamic uri in request for external service i am unable to set
the dynamic uri in request.
it is not using simple expression language "${header.if}" or placeholder
"\{{id}}".
can any one help on this with example.
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> I am trying to call an external service with some dynamic uri which will be
> comming in request e.g www.abc.com/{id} i get that id in ${header.id} which
> is perfectly log in console but when i am trying to use netty4-http component
> in camel i used same dynamic uri in path of configuration but i am getting
> error of 404 not found because the url is not properly made.
> It is not using simple expression language like "${header.id}" or any
> placeholder like "{{id}}" and also not work with this "{id}"
> I am using blue print dsl in redhat code ready studio 12.11.0 GA
> The main problem is how to use dynamic uri with netty4-http component in
> camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864008#comment-16864008
]
Andrea Cosentino commented on CAMEL-13648:
--
If you open an issue and ask for help, it sounds really like a users mailing
list thread.
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> how to use dynamic uri in path of netty4-http component.
> while setting dynamic uri in request for external service i am unable to set
> the dynamic uri in request.
> it is not using simple expression language "${header.if}" or placeholder
> "\{{id}}".
> can any one help on this with example.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864003#comment-16864003
]
Andrea Cosentino commented on CAMEL-13648:
--
This is a question and not an issue. There are not enough details.
You need to subscribe yourself here
[users-subscr...@camel.apache.org|mailto:here%c2%a0users-subscr...@camel.apache.org]
And then start a thread at
[us...@camel.apache.org|mailto:us...@camel.apache.org]
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> how to use dynamic uri in path of netty4-http component.
> while setting dynamic uri in request for external service i am unable to set
> the dynamic uri in request.
> it is not using simple expression language "${header.if}" or placeholder
> "\{{id}}".
> can any one help on this with example.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863991#comment-16863991
]
Muhammad Zubair commented on CAMEL-13648:
-
This is a issue of camel component not a question its *netty4-http component*
issue in camel.
and from where i get the mailing list?
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> how to use dynamic uri in path of netty4-http component.
> while setting dynamic uri in request for external service i am unable to set
> the dynamic uri in request.
> it is not using simple expression language "${header.if}" or placeholder
> "\{{id}}".
> can any one help on this with example.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13648.
--
Resolution: Invalid
Please ask on the user mailing list. This is a Jira for issues and not for Q&A
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> how to use dynamic uri in path of netty4-http component.
> while setting dynamic uri in request for external service i am unable to set
> the dynamic uri in request.
> it is not using simple expression language "${header.if}" or placeholder
> "\{{id}}".
> can any one help on this with example.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-13648:
-
Priority: Minor (was: Blocker)
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Minor
>
> how to use dynamic uri in path of netty4-http component.
> while setting dynamic uri in request for external service i am unable to set
> the dynamic uri in request.
> it is not using simple expression language "${header.if}" or placeholder
> "\{{id}}".
> can any one help on this with example.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
[
https://issues.apache.org/jira/browse/CAMEL-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Muhammad Zubair updated CAMEL-13648:
Description:
how to use dynamic uri in path of netty4-http component.
while setting dynamic uri in request for external service i am unable to set
the dynamic uri in request.
it is not using simple expression language "${header.if}" or placeholder
"\{{id}}".
can any one help on this with example.
was:
how to use dynamic uri in path of netty4-http component.
it is not using simple expression language "${header.if}" or placeholder
"\{{id}}".
can any one help on this with example.
> unable to set dynamic uri in request of netty4-http component in camel
> ---
>
> Key: CAMEL-13648
> URL: https://issues.apache.org/jira/browse/CAMEL-13648
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-netty4-http
>Affects Versions: 2.21.0, 3.0.0-M1
>Reporter: Muhammad Zubair
>Priority: Blocker
>
> how to use dynamic uri in path of netty4-http component.
> while setting dynamic uri in request for external service i am unable to set
> the dynamic uri in request.
> it is not using simple expression language "${header.if}" or placeholder
> "\{{id}}".
> can any one help on this with example.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13648) unable to set dynamic uri in request of netty4-http component in camel
Muhammad Zubair created CAMEL-13648:
---
Summary: unable to set dynamic uri in request of netty4-http
component in camel
Key: CAMEL-13648
URL: https://issues.apache.org/jira/browse/CAMEL-13648
Project: Camel
Issue Type: Bug
Components: camel-http, camel-netty4-http
Affects Versions: 3.0.0-M1, 2.21.0
Reporter: Muhammad Zubair
how to use dynamic uri in path of netty4-http component.
it is not using simple expression language "${header.if}" or placeholder
"\{{id}}".
can any one help on this with example.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-8362) Camel Components - Generate per component Java fluent builder
[
https://issues.apache.org/jira/browse/CAMEL-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved CAMEL-8362.
Resolution: Fixed
> Camel Components - Generate per component Java fluent builder
> -
>
> Key: CAMEL-8362
> URL: https://issues.apache.org/jira/browse/CAMEL-8362
> Project: Camel
> Issue Type: New Feature
> Components: tooling
>Reporter: Claus Ibsen
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
>
> Similar to CAMEL-8361, but for generating java source code fluent builder, so
> people can configured components and endpoints in a nicer style.
> {code}
> Endpoint file =
> FileEndpointBuilder.directory("somepath").recursive(true).includes("*.txt").build();
> ...
> {code}
> Though there is a few tasks to figure out.
> We would need some template as skeleton for generating the source code. And
> we would need a naming convention for the class name. And also we should
> allow each builder method to have 2 options. As its original type, eg String,
> boolean, int, etc. And then an alternative that uses a String so people can
> use property placeholders, eg "{{foo}}".
> And besides endpoints we should also generate for components as well, so its
> easier to configure them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13647) camel-main - Add support for auto binding to components by interface type and discover impl class on classpath
[ https://issues.apache.org/jira/browse/CAMEL-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863892#comment-16863892 ] Claus Ibsen commented on CAMEL-13647: - Okay got a prototype working, but the classpath scanning is slow, takes 5 sec on an unit test with 600+ packages due to all the unit test classes and whatnot. We may want to add some maven plugin that can attempt to do this at build-time, and generate a META-INF/org/apache/camel/service/autowire-by-classpath file that pre-lists the possible autowires by classpath > camel-main - Add support for auto binding to components by interface type and > discover impl class on classpath > -- > > Key: CAMEL-13647 > URL: https://issues.apache.org/jira/browse/CAMEL-13647 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > This can make convention over configuration nicer. For example some > components requires a ConnectionFactory etc and if we can auto-discover that > on the classpath there is only 1 implementation of such interface, we can try > to auto create the instance and configure it on the component. > This should be an option you can turn on|off. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-12947) MockEndpoint.expectedHeaderReceived should fail when no exchange received
[
https://issues.apache.org/jira/browse/CAMEL-12947?focusedWorklogId=260255&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-260255
]
ASF GitHub Bot logged work on CAMEL-12947:
--
Author: ASF GitHub Bot
Created on: 14/Jun/19 09:27
Start Date: 14/Jun/19 09:27
Worklog Time Spent: 10m
Work Description: jonathanvila commented on pull request #2977:
CAMEL-12947:MockEndpoint.expectedHeaderReceived should fail when no e…
URL: https://github.com/apache/camel/pull/2977
…xchange received (#2669)
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 260255)
Time Spent: 50m (was: 40m)
> MockEndpoint.expectedHeaderReceived should fail when no exchange received
> -
>
> Key: CAMEL-12947
> URL: https://issues.apache.org/jira/browse/CAMEL-12947
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.22.1
>Reporter: Antoine Wils
>Assignee: Ramu
>Priority: Minor
> Fix For: 3.0.0, 2.24.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When expecting headers to be passed to a MockEndpoint that is never called
> the test should fail if the MockEndpoint was never called.
> However it is succeeding.
> Here an example of Junit 4 test succeeding when it should fail
> {code:java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> public class Test extends CamelTestSupport {
> @EndpointInject(uri = "mock:direct:foo")
> private MockEndpoint fooProducerMock;
> @Override
> public RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {}
> };
> }
> @Test
> public void failWhenHeaderAbsent() throws InterruptedException {
> fooProducerMock.expectedHeaderReceived("ghost", "you should be visible");
> MockEndpoint.assertIsSatisfied(context);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13647) camel-main - Add support for auto binding to components by interface type and discover impl class on classpath
[ https://issues.apache.org/jira/browse/CAMEL-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863849#comment-16863849 ] Claus Ibsen commented on CAMEL-13647: - The problem is to do a full classpath scanning where you don't know the package names, as this can be in any of the packages. So we need to find all the JARs on the classpath, and look inside them, to gather their package names. All of this comes with a performance penalty. > camel-main - Add support for auto binding to components by interface type and > discover impl class on classpath > -- > > Key: CAMEL-13647 > URL: https://issues.apache.org/jira/browse/CAMEL-13647 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > This can make convention over configuration nicer. For example some > components requires a ConnectionFactory etc and if we can auto-discover that > on the classpath there is only 1 implementation of such interface, we can try > to auto create the instance and configure it on the component. > This should be an option you can turn on|off. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-12947) MockEndpoint.expectedHeaderReceived should fail when no exchange received
[
https://issues.apache.org/jira/browse/CAMEL-12947?focusedWorklogId=260237&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-260237
]
ASF GitHub Bot logged work on CAMEL-12947:
--
Author: ASF GitHub Bot
Created on: 14/Jun/19 08:54
Start Date: 14/Jun/19 08:54
Worklog Time Spent: 10m
Work Description: jonathanvila commented on pull request #2976:
CAMEL-12947:MockEndpoint.expectedHeaderReceived should fail when no e…
URL: https://github.com/apache/camel/pull/2976
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 260237)
Time Spent: 40m (was: 0.5h)
> MockEndpoint.expectedHeaderReceived should fail when no exchange received
> -
>
> Key: CAMEL-12947
> URL: https://issues.apache.org/jira/browse/CAMEL-12947
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.22.1
>Reporter: Antoine Wils
>Assignee: Ramu
>Priority: Minor
> Fix For: 3.0.0, 2.24.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When expecting headers to be passed to a MockEndpoint that is never called
> the test should fail if the MockEndpoint was never called.
> However it is succeeding.
> Here an example of Junit 4 test succeeding when it should fail
> {code:java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> public class Test extends CamelTestSupport {
> @EndpointInject(uri = "mock:direct:foo")
> private MockEndpoint fooProducerMock;
> @Override
> public RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {}
> };
> }
> @Test
> public void failWhenHeaderAbsent() throws InterruptedException {
> fooProducerMock.expectedHeaderReceived("ghost", "you should be visible");
> MockEndpoint.assertIsSatisfied(context);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13642) Testing for an expected Header in a MockEndpoint doesnt happen if there is no Exchange received
[
https://issues.apache.org/jira/browse/CAMEL-13642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863846#comment-16863846
]
Jonathan Vila commented on CAMEL-13642:
---
PR: [https://github.com/apache/camel/pull/2976]
> Testing for an expected Header in a MockEndpoint doesnt happen if there is no
> Exchange received
> ---
>
> Key: CAMEL-13642
> URL: https://issues.apache.org/jira/browse/CAMEL-13642
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Jonathan Vila
>Priority: Major
> Fix For: 2.23.0
>
>
> Context
> {quote}
> When we have a MockEndpoint that expects for any header to be received, now
> there is no error raised if there is no Exchange received.
> So , it only checks for the expression if there is an Exchange, therefore the
> test doesn't fail.
> {quote}
> Where
> {quote}MockEndpoint.expectedHeaderReceived:519
> {quote}
> Fix
> {quote}Add an assert for getReceivedExchanges > 0
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-12947) MockEndpoint.expectedHeaderReceived should fail when no exchange received
[
https://issues.apache.org/jira/browse/CAMEL-12947?focusedWorklogId=260236&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-260236
]
ASF GitHub Bot logged work on CAMEL-12947:
--
Author: ASF GitHub Bot
Created on: 14/Jun/19 08:51
Start Date: 14/Jun/19 08:51
Worklog Time Spent: 10m
Work Description: jonathanvila commented on pull request #2976:
CAMEL-12947:MockEndpoint.expectedHeaderReceived should fail when no e…
URL: https://github.com/apache/camel/pull/2976
…xchange received (#2669)
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 260236)
Time Spent: 0.5h (was: 20m)
> MockEndpoint.expectedHeaderReceived should fail when no exchange received
> -
>
> Key: CAMEL-12947
> URL: https://issues.apache.org/jira/browse/CAMEL-12947
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.22.1
>Reporter: Antoine Wils
>Assignee: Ramu
>Priority: Minor
> Fix For: 3.0.0, 2.24.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When expecting headers to be passed to a MockEndpoint that is never called
> the test should fail if the MockEndpoint was never called.
> However it is succeeding.
> Here an example of Junit 4 test succeeding when it should fail
> {code:java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> public class Test extends CamelTestSupport {
> @EndpointInject(uri = "mock:direct:foo")
> private MockEndpoint fooProducerMock;
> @Override
> public RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {}
> };
> }
> @Test
> public void failWhenHeaderAbsent() throws InterruptedException {
> fooProducerMock.expectedHeaderReceived("ghost", "you should be visible");
> MockEndpoint.assertIsSatisfied(context);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13639) camel-pulsar build is flaky
[ https://issues.apache.org/jira/browse/CAMEL-13639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-13639. Resolution: Fixed Fix Version/s: 3.0.0.M4 That's 3 builds without anymore pulsar related issues, resolving. > camel-pulsar build is flaky > --- > > Key: CAMEL-13639 > URL: https://issues.apache.org/jira/browse/CAMEL-13639 > Project: Camel > Issue Type: Bug >Affects Versions: 3.0.0-M3 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0.M4 > > > The camel-pulsar build sometime fails with an error message containing > "Policies not found for public/default namespace". > But actually, the default/namespace should be in the container out of the box. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13647) camel-main - Add support for auto binding to components by interface type and discover impl class on classpath
Claus Ibsen created CAMEL-13647: --- Summary: camel-main - Add support for auto binding to components by interface type and discover impl class on classpath Key: CAMEL-13647 URL: https://issues.apache.org/jira/browse/CAMEL-13647 Project: Camel Issue Type: New Feature Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.0.0, 3.0.0.M4 This can make convention over configuration nicer. For example some components requires a ConnectionFactory etc and if we can auto-discover that on the classpath there is only 1 implementation of such interface, we can try to auto create the instance and configure it on the component. This should be an option you can turn on|off. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13645) camel-spring - NPE in NotifyBuilder during testing
[ https://issues.apache.org/jira/browse/CAMEL-13645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13645. - Resolution: Fixed Assignee: Claus Ibsen > camel-spring - NPE in NotifyBuilder during testing > -- > > Key: CAMEL-13645 > URL: https://issues.apache.org/jira/browse/CAMEL-13645 > Project: Camel > Issue Type: Test > Components: camel-spring >Affects Versions: 3.0.0-M3 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > Just noticed some NPEs while doing test of camel-spring > 019-06-13 15:02:08,902 WARN EventHelper - Error notifying event > ID-davsclaus-pro-local-1560430811107-235-1 exchange created: > Exchange[ID-davsclaus-pro-local-1560430811107-235-1]. This exception will be > ignored. > java.lang.NullPointerException: null > at > org.apache.camel.builder.NotifyBuilder$3.onExchange(NotifyBuilder.java:194) > ~[camel-core-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT] > at > org.apache.camel.builder.NotifyBuilder$EventPredicateSupport.onExchangeCreated(NotifyBuilder.java:1293) > ~[camel-core-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT] > at > org.apache.camel.builder.NotifyBuilder$CompoundEventPredicate.onExchangeCreated(NotifyBuilder.java:1381) > ~[camel-core-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT] > at > org.apache.camel.builder.NotifyBuilder$ExchangeNotifier.onExchangeCreated(NotifyBuilder.java:1154) > ~[camel-core-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT] > at > org.apache.camel.builder.NotifyBuilder$ExchangeNotifier.notify(NotifyBuilder.java:1135) > ~[camel-core-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT] > at > org.apache.camel.support.EventHelper.doNotifyEvent(EventHelper.java:288) > [camel-support-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT] > at org.apache.camel.support.EventHelper.doNotify(EventHelper.java:27 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13646) camel-jms - Add support for DynamicAware endpoints for toD with dynamic desintation
Claus Ibsen created CAMEL-13646: --- Summary: camel-jms - Add support for DynamicAware endpoints for toD with dynamic desintation Key: CAMEL-13646 URL: https://issues.apache.org/jira/browse/CAMEL-13646 Project: Camel Issue Type: Improvement Components: camel-jms Reporter: Claus Ibsen Fix For: 3.0.0 Related to this user group issue http://camel.465427.n5.nabble.com/Intermittent-RejectedExecutionException-tp5836376.html We can improve camel-jms with toD to not have to create new endpoints for each dynamic destination, but instead use DynamicAware which we do for the http components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
