[jira] [Resolved] (CAMEL-13600) Memory leaks when using camel 2.24.0
[
https://issues.apache.org/jira/browse/CAMEL-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13600.
-
Resolution: Cannot Reproduce
> Memory leaks when using camel 2.24.0
>
>
> Key: CAMEL-13600
> URL: https://issues.apache.org/jira/browse/CAMEL-13600
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.24.0
>Reporter: Mikhail Kornienko
>Priority: Major
> Attachments: 2.23.1_memory.png, 2.23.1_memory_grapf.png,
> 2.23.1_thread.png, 2.24.0_memory.png, 2.24.0_memory_grapf.png,
> 2.24.0_thread.png
>
>
> When using the same code, version 2.21.1 works correctly, but when using
> version 2.24.0, a memory leak is detected.
> Screen shots in attache.
> {code:java}
> http://camel.apache.org/schema/spring;>
>
>
>
> ${header.FROM_TOPIC} == 'TOPIC-1'
>
>
> ${header.type1} in '1,2,3' and ${header.type2}
> == 4
>
> 'TOPIC-2'
>
>
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (CAMEL-13047) Validator Component Fails on XSD with file Relative Imports or include
[ https://issues.apache.org/jira/browse/CAMEL-13047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13047: Priority: Minor (was: Major) > Validator Component Fails on XSD with file Relative Imports or include > --- > > Key: CAMEL-13047 > URL: https://issues.apache.org/jira/browse/CAMEL-13047 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.22.0, 2.22.1, 2.22.2 >Reporter: W.Y >Priority: Minor > Attachments: testcase.zip > > > When using the validator component with an XSD that references > (import/include) a second XSD on a different path, and where the second XSD > references a third XSD using a relative path, the path of the third XSD is > resolved relative to the first schema rather than relative to the second. > I found it it same bug ticket reported , although it stated it is fixed > already at camel 2.10, but it does not work for us when we use >=camel 2.22. > The problem is reported as fixed at > https://issues.apache.org/jira/browse/CAMEL-6013 . i modified testcase of it > and put it here again for you to reproduce the problem. thanks and rgds -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13452) Refactor routeId generation and initiation for REST and common DSLs
[ https://issues.apache.org/jira/browse/CAMEL-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13452: Fix Version/s: (was: 3.0.0) 3.x > Refactor routeId generation and initiation for REST and common DSLs > --- > > Key: CAMEL-13452 > URL: https://issues.apache.org/jira/browse/CAMEL-13452 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-13706) Allow conditional exception propagation to parent RouteBuilders from DefaultErrorHandler
[
https://issues.apache.org/jira/browse/CAMEL-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13706.
-
Resolution: Later
Sorry error handling is already complex as-is, and at this time we are not
looking at further complicate it.
> Allow conditional exception propagation to parent RouteBuilders from
> DefaultErrorHandler
>
>
> Key: CAMEL-13706
> URL: https://issues.apache.org/jira/browse/CAMEL-13706
> Project: Camel
> Issue Type: New Feature
>Reporter: Stig Rohde Døssing
>Priority: Major
>
> Exception propagation between RouteBuilders is currently only possible with
> the NoErrorHandler. It would be great if the DefaultErrorHandler could be
> configured to propagate exceptions it is not configured to handle. This would
> allow more Java-like exception handling for pipelines that cross
> RouteBuilders.
> Basically the behavior I'd like from the DefaultErrorHandler is that
> exceptions thrown from a route that are not handled, and exceptions thrown
> from onException clauses, are handled the same way they would if the
> NoErrorHandler were configured. This would cause them to propagate to
> handlers in the parent.
> An example of how this could look:
> {code:java}
> class RestRouteBuilder extends RouteBuilder {
> onException(Exception.class)
> .handled(true)
> .process(return a 500-series code)
> onException(JsonProcessingException.class)
> .handled(true)
> .process(return a 400-series code)
>from(rest)
> .choice()
>.when(the request is type A)
> .to(type A route)
>.otherwise()
> .to(type B route)
> }
> class TypeARouteBuilder extends RouteBuilder {
>
> setErrorHandlerBuilder(defaultErrorHandler().propagateUncaughtExceptions());
> onException(SomeRouteSpecificException.class)
> .handled(true)
> //Any exception thrown here is propagated to the RestRouteBuilder's
> onException clauses
> from(type A route)
> //SomeRouteSpecificException gets handled by the onException clause above
> //Anything else is propagated to the RestRouteBuilder's onException
> clauses
> .to(write to DB route)
> }
> class TypeBRouteBuilder extends RouteBuilder {
> setErrorHandlerBuilder(defaultErrorHandler().propagateUncaughtExceptions());
>
> onException(SomeOtherRouteSpecificException.class)
> .handled(true)
> //Any exception thrown here is propagated to the RestRouteBuilder's
> onException clauses
> from(type B route)
> //SomeOtherRouteSpecificException gets handled by the onException clause
> above
> //Anything else is propagated to the RestRouteBuilder's onException
> clauses
> .to(write to DB route)
> }
> class DBRouteBuilder extends RouteBuilder {
> setErrorHandlerBuilder(defaultErrorHandler().propagateUncaughtExceptions());
> onException(AuthenticationException.class)
> .redeliveryPolicy(new RedeliveryPolicy().maximumRedeliveries(10))
> from(type A route)
> //AuthenticationException gets handled by the onException clause above
> //Anything else is propagated to either TypeA or TypeB onException
> clauses, and possibly on to RestRouteBuilder's clauses
> .to(the DB endpoint)
> }
> {code}
> I'd be happy to work on implementing this option, assuming there isn't
> opposition to creating a feature like this.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (CAMEL-13611) Camel Web3j - Upgrade to Web3j 4.3.1
[ https://issues.apache.org/jira/browse/CAMEL-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13611: Issue Type: Improvement (was: New Feature) > Camel Web3j - Upgrade to Web3j 4.3.1 > > > Key: CAMEL-13611 > URL: https://issues.apache.org/jira/browse/CAMEL-13611 > Project: Camel > Issue Type: Improvement >Reporter: Choucri Fahed >Priority: Major > > Support the latest version of Web3j. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (CAMEL-13611) Camel Web3j - Upgrade to Web3j 4.3.1
[ https://issues.apache.org/jira/browse/CAMEL-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-13611: --- Assignee: (was: Bilgin Ibryam) > Camel Web3j - Upgrade to Web3j 4.3.1 > > > Key: CAMEL-13611 > URL: https://issues.apache.org/jira/browse/CAMEL-13611 > Project: Camel > Issue Type: New Feature >Reporter: Choucri Fahed >Priority: Major > > Support the latest version of Web3j. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13611) Camel Web3j - Upgrade to Web3j 4.3.1
[ https://issues.apache.org/jira/browse/CAMEL-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13611: Fix Version/s: (was: 2.25.0) (was: 3.0.0) > Camel Web3j - Upgrade to Web3j 4.3.1 > > > Key: CAMEL-13611 > URL: https://issues.apache.org/jira/browse/CAMEL-13611 > Project: Camel > Issue Type: New Feature >Reporter: Choucri Fahed >Assignee: Bilgin Ibryam >Priority: Major > > Support the latest version of Web3j. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-12938) clientRequestValidation does not validate existence of POST request body
[ https://issues.apache.org/jira/browse/CAMEL-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12938. - Resolution: Cannot Reproduce > clientRequestValidation does not validate existence of POST request body > > > Key: CAMEL-12938 > URL: https://issues.apache.org/jira/browse/CAMEL-12938 > Project: Camel > Issue Type: Bug > Components: rest >Affects Versions: 2.22.1 >Reporter: Robert Gründler >Assignee: Ramu >Priority: Minor > > According to the [documentation > |[https://github.com/apache/camel/blob/master/camel-core/src/main/docs/rest-dsl.adoc#client-request-validation],] > the `clientRequestValidation` option should validate the existence of the > client request body for POST requests. > However, when we send POST requests to a camel rest endpoint that has the > option enabled, a null body is passed to the camel routes afterwards. > > There seems to be a `requiredBody` flag in the RestBindingAdvice.java class, > but this always evalutates to `false`, and there does not seem to be a way to > set it in the configuration -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-12504) Test Apache Camel on Java 9 and newer
[ https://issues.apache.org/jira/browse/CAMEL-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897711#comment-16897711 ] Claus Ibsen commented on CAMEL-12504: - Yeah Jan you are welcome to create a JIRA and then remove it on master and deprecate it on camel-2.x > Test Apache Camel on Java 9 and newer > - > > Key: CAMEL-12504 > URL: https://issues.apache.org/jira/browse/CAMEL-12504 > Project: Camel > Issue Type: Test > Components: build system >Reporter: Luca Burgazzoli >Assignee: John Poth >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-12504) Test Apache Camel on Java 9 and newer
[ https://issues.apache.org/jira/browse/CAMEL-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897459#comment-16897459 ] Jan Bednar commented on CAMEL-12504: [~davsclaus] There is unresolved issue about boon, which we have reported in 2017 ([https://github.com/boonproject/boon/issues/376]) and there is no single commit from this time. The last working JDK for boon was 1.8 and the project seems to be abandoned. Maybe it is the right time to remove camel-boon? > Test Apache Camel on Java 9 and newer > - > > Key: CAMEL-12504 > URL: https://issues.apache.org/jira/browse/CAMEL-12504 > Project: Camel > Issue Type: Test > Components: build system >Reporter: Luca Burgazzoli >Assignee: John Poth >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-12618) Compilation failure on Java 11
[
https://issues.apache.org/jira/browse/CAMEL-12618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12618.
-
Resolution: Fixed
> Compilation failure on Java 11
> --
>
> Key: CAMEL-12618
> URL: https://issues.apache.org/jira/browse/CAMEL-12618
> Project: Camel
> Issue Type: Sub-task
> Components: build system
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0
>
>
> Maven compiler fails on JDK 11 for us. The error is not that helpful.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
> (default-compile) on project json-simple-ordered: Compilation failure ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
> (default-compile) on project json-simple-ordered: Compilation failure
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-12504) Test Apache Camel on Java 9 and newer
[ https://issues.apache.org/jira/browse/CAMEL-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12504. - Resolution: Fixed > Test Apache Camel on Java 9 and newer > - > > Key: CAMEL-12504 > URL: https://issues.apache.org/jira/browse/CAMEL-12504 > Project: Camel > Issue Type: Test > Components: build system >Reporter: Luca Burgazzoli >Assignee: John Poth >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-13356) cassandra-unit test dependency removal ?
[ https://issues.apache.org/jira/browse/CAMEL-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13356. - Resolution: Fixed Fix Version/s: 3.0.0 Thanks William > cassandra-unit test dependency removal ? > > > Key: CAMEL-13356 > URL: https://issues.apache.org/jira/browse/CAMEL-13356 > Project: Camel > Issue Type: Task >Reporter: Etienne Chauchot >Priority: Major > Fix For: 3.0.0 > > > I'm a PMC member of Beam project were I use cassandra-unit in the test > dependencies of a module just like you do in Cassandra CQL module: > https://mvnrepository.com/artifact/org.apache.camel/camel-cassandraql/2.23.1 > The problem is that this lib is licensed under LGPLV3 which is a category X > unauthorized licence. I just figured out that it seems to be forbidden even > in test code to use LGPL libs (see [here > |https://issues.apache.org/jira/browse/LEGAL-153 ] and [here| > https://issues.apache.org/jira/browse/LEGAL-207?focusedCommentId=14080037=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14080037]). > I'm removing it from Beam. I went through some of the apache projects that > use cassandra-unit and I found Camel friends. Hence this advice. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13342: Fix Version/s: 3.0.0 > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > > Exploratory preparation work happens in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13342: Priority: Major (was: Minor) > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > > Exploratory preparation work happens in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-13311) camel-cdi and camel-blueprint - Cleanup bean post processor
[ https://issues.apache.org/jira/browse/CAMEL-13311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897434#comment-16897434 ] Claus Ibsen commented on CAMEL-13311: - camel-cdi has been cleaned up > camel-cdi and camel-blueprint - Cleanup bean post processor > --- > > Key: CAMEL-13311 > URL: https://issues.apache.org/jira/browse/CAMEL-13311 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > Looks like they do some custom code that likely is not longer needed and can > rely on the default out of the box. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-13206) Component state management a.k.a. domain mode
[ https://issues.apache.org/jira/browse/CAMEL-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13206. - Resolution: Won't Fix > Component state management a.k.a. domain mode > - > > Key: CAMEL-13206 > URL: https://issues.apache.org/jira/browse/CAMEL-13206 > Project: Camel > Issue Type: Task >Reporter: Thomas Diesler >Priority: Major > > There have been requests to also support Camel in WildFly domain mode. AFAIU, > this could work for stateless components or components that have its state > replication (or general state management) handled by the underlying platform. > Perhaps it'd be useful to first mark those components that are stateless or > alternatively need some sort of state management. In a further step it would > perhaps be useful to provide some sort of state management API that can then > be implemented by the underlying platform. > In EAP this could then perhaps be delegated to the domain mode state > management. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13094) Context MBean not unregistered on startup failure
[ https://issues.apache.org/jira/browse/CAMEL-13094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13094: Fix Version/s: 3.0.0.M5 > Context MBean not unregistered on startup failure > - > > Key: CAMEL-13094 > URL: https://issues.apache.org/jira/browse/CAMEL-13094 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.0.0 >Reporter: Thomas Diesler >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > > In Camel-2.23.x a failure to start the context would call > ServiceSupport.doStop(). This is no longer the case. Instead, a > CamelContextStartupFailureEvent is thrown and services that might previously > have been started are never stopped. > As a result or (side effect) the context MBean may remain registered if the > startup failure occurred after its initial registration. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-12923) BindingComponent support for endpoint parameters
[
https://issues.apache.org/jira/browse/CAMEL-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12923.
-
Resolution: Won't Fix
binding is deprecated
> BindingComponent support for endpoint parameters
>
>
> Key: CAMEL-12923
> URL: https://issues.apache.org/jira/browse/CAMEL-12923
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.22.1
>Reporter: Marc Carter
>Priority: Minor
>
> Both BindingComponent and BindingNameComponent wrap a delegate Endpoint with
> some common contract. Neither support passing of URI parameters to their
> delegate and this critically limits their use.
> (/) binding:xxx:jms:queue:a.b.c
> (x) binding:xxx:jms:queue:a.b.c?preserveMessageQos=true
> {quote}org.apache.camel.ResolveEndpointFailedException: Failed to resolve
> endpoint: binding://xxx:jms:queue:a.b.c?preserveMessageQos=true due to:
> Failed to resolve endpoint: jms://queue:a.b.c?preserveMessageQos=true due to:
> There are 1 parameters that couldn't be set on the endpoint. Check the uri if
> the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[\{preserveMessageQos=true}]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-13139) ModelCamelContext.setTracing(true) makes Camel Salesforce APEX calls fragile
[
https://issues.apache.org/jira/browse/CAMEL-13139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13139.
-
Resolution: Not A Problem
> ModelCamelContext.setTracing(true) makes Camel Salesforce APEX calls fragile
>
>
> Key: CAMEL-13139
> URL: https://issues.apache.org/jira/browse/CAMEL-13139
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 2.23.1
>Reporter: Jesse Sightler
>Priority: Major
>
> We were having an issue with a process hanging on Salesforce APEX REST calls.
> It turns out that the key factor was whether or not tracing was enabled.
> It isn't clear to me as to what the correct fix is, but this code change
> works around the problem:
> {quote}---
> a/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/internal/processor/JsonRestProcessor.java
> +++
> b/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/internal/processor/JsonRestProcessor.java
> @@ -188,6 +188,7 @@ public class JsonRestProcessor extends
> AbstractRestProcessor {
> // if an exception is reported we should not loose it
> if (shouldReport(ex)) {
> exchange.setException(ex);
> + out.setBody("");
> }
> } else if (responseEntity != null) {
> // do we need to un-marshal a response
> {quote}
> All of the cases of it hanging were when there were exceptions thrown by the
> service.
> Basically if the body of the out message is set, then it doesn't hang. I can
> provide more details if need be as well.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAMEL-13070) sftp incorrectly catches files with filename in Windows-1251 encoding
[ https://issues.apache.org/jira/browse/CAMEL-13070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897427#comment-16897427 ] Claus Ibsen commented on CAMEL-13070: - You are welcome to work on a PR / contribution > sftp incorrectly catches files with filename in Windows-1251 encoding > - > > Key: CAMEL-13070 > URL: https://issues.apache.org/jira/browse/CAMEL-13070 > Project: Camel > Issue Type: Improvement > Components: camel-ftp >Affects Versions: 2.21.4 >Reporter: Igor Piddubnyi >Priority: Minor > > While processing files with Windows-1251 encoded filename I have not found > ability to define filename encoding. > sftp component does not support "ftpClientConfig.serverLanguageCode=de" > option. > Howevever underlying ChannelSftp has setFilenameEncoding method > Could this be exposed as additional parameter? -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13087) Add more obvious exception handling for "multicast"
[
https://issues.apache.org/jira/browse/CAMEL-13087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13087:
Fix Version/s: (was: 3.0.0)
Future
> Add more obvious exception handling for "multicast"
> ---
>
> Key: CAMEL-13087
> URL: https://issues.apache.org/jira/browse/CAMEL-13087
> Project: Camel
> Issue Type: Wish
>Reporter: Peter Keller
>Priority: Major
> Fix For: Future
>
>
> Add more obvious exception handling for {{multicast}}.
> E.g. see
> *
> https://stackoverflow.com/questions/35896325/camel-multicast-exception-propagation
> *
> https://stackoverflow.com/questions/51156635/apache-camel-how-to-catch-exception-with-multicast
> *
> https://stackoverflow.com/questions/40281605/camel-isnt-propagating-exceptions-when-they-are-thrown-inside-of-a-multicast-wh
> *
> https://stackoverflow.com/questions/7317776/apache-camel-multicast-exception-and-aggregation-strategy
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (CAMEL-13036) Add the possibility to disable the invocation of ModelHelper.dumpModelAsXml() during testing
[
https://issues.apache.org/jira/browse/CAMEL-13036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13036:
Fix Version/s: 3.0.0.M5
3.0.0
> Add the possibility to disable the invocation of ModelHelper.dumpModelAsXml()
> during testing
>
>
> Key: CAMEL-13036
> URL: https://issues.apache.org/jira/browse/CAMEL-13036
> Project: Camel
> Issue Type: Improvement
> Components: camel-test
>Affects Versions: 2.23.0
>Reporter: Peter Keller
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M5
>
>
> Add the possibility to disable the invocation of
> {{ModelHelper.dumpModelAsXml()}}. This is particularly disturbing for Camel
> contexts with a lot of route definitions as this uses a lot of processing
> time and the information is only used for log output.
> Actual use in 2.x in {{RouteDefinition.java}}:
> {code:java|title=RouteDefinition.java}
> String beforeAsXml = ModelHelper.dumpModelAsXml(camelContext, this);
> ...
> String afterAsXml = ModelHelper.dumpModelAsXml(camelContext, merged);
> log.info("Adviced route before/after as XML:\n{}\n{}", beforeAsXml,
> afterAsXml);
> {code}
> In 2.X this should be optimized in {{RouteDefinition.java}}, in 3.X in
> {{RouteReifier.java}}.
> Possible solution: Add {{log.isInfoEnabled{}}} guard.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (CAMEL-13036) Add the possibility to disable the invocation of ModelHelper.dumpModelAsXml() during testing
[
https://issues.apache.org/jira/browse/CAMEL-13036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-13036:
---
Assignee: Claus Ibsen
> Add the possibility to disable the invocation of ModelHelper.dumpModelAsXml()
> during testing
>
>
> Key: CAMEL-13036
> URL: https://issues.apache.org/jira/browse/CAMEL-13036
> Project: Camel
> Issue Type: Improvement
> Components: camel-test
>Affects Versions: 2.23.0
>Reporter: Peter Keller
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M5
>
>
> Add the possibility to disable the invocation of
> {{ModelHelper.dumpModelAsXml()}}. This is particularly disturbing for Camel
> contexts with a lot of route definitions as this uses a lot of processing
> time and the information is only used for log output.
> Actual use in 2.x in {{RouteDefinition.java}}:
> {code:java|title=RouteDefinition.java}
> String beforeAsXml = ModelHelper.dumpModelAsXml(camelContext, this);
> ...
> String afterAsXml = ModelHelper.dumpModelAsXml(camelContext, merged);
> log.info("Adviced route before/after as XML:\n{}\n{}", beforeAsXml,
> afterAsXml);
> {code}
> In 2.X this should be optimized in {{RouteDefinition.java}}, in 3.X in
> {{RouteReifier.java}}.
> Possible solution: Add {{log.isInfoEnabled{}}} guard.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-11361) AsyncCallback API - Include Exchange if we do change the API
[ https://issues.apache.org/jira/browse/CAMEL-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-11361. - Resolution: Won't Fix Lets keep the API as is > AsyncCallback API - Include Exchange if we do change the API > > > Key: CAMEL-11361 > URL: https://issues.apache.org/jira/browse/CAMEL-11361 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: Future, 3.0.0 > > > The AsyncCallback has a done method with only a boolean. If we had included > the Exchange as well, then we could often obtain any needed information in > the callback method from the exchange instead of having to refer to instances > from the surrounding scope via final keywords. > This also avoids creating a new object per call which, which then take up > memory. > void done(boolean syncDone, Exchange exchange) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-12968) DefaultFluentProducerTemplate is not thread safe (endpoint, etc.)
[
https://issues.apache.org/jira/browse/CAMEL-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-12968:
Fix Version/s: 3.0.0.M5
3.0.0
> DefaultFluentProducerTemplate is not thread safe (endpoint, etc.)
> -
>
> Key: CAMEL-12968
> URL: https://issues.apache.org/jira/browse/CAMEL-12968
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.22.1, 2.23.0
>Reporter: Paul D Johe
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M5
>
>
> The DefaultFluentProducerTemplate saves state between method calls. This
> leads to unexpected behavior when the javadoc specifies that it should be
> thread safe.
> For example:
> # thread 1 calls fluentProducerTemplate.to("direct:a").send("message1");
> # thread 2 calls fluentProducerTemplate.to("direct:b").send("message2");
> If these are run in parallel, the sequence of calls can be:
> # thread 1 calls to("direct:a") - endpoint in the object is direct:a
> # thread 2 calls to("direct:b") - endpoint in the object is direct:b
> # *thread 1 calls send("message1") - this gets sent incorrectly to direct:b*
> # thread 2 calls send("message2") - this gets sent correctly to direct:b
> Endpoint is one example, but almost all fields in this class share this
> behavior. It should be clearly documented which fields can be used fluently
> over multiple threads, and which cannot. As the API is today, all methods
> returning 'this' should be made thread-safe (state is only local to the
> caller) so that the fluent interface works as expected.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (CAMEL-12968) DefaultFluentProducerTemplate is not thread safe (endpoint, etc.)
[
https://issues.apache.org/jira/browse/CAMEL-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-12968:
---
Assignee: Claus Ibsen
> DefaultFluentProducerTemplate is not thread safe (endpoint, etc.)
> -
>
> Key: CAMEL-12968
> URL: https://issues.apache.org/jira/browse/CAMEL-12968
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.22.1, 2.23.0
>Reporter: Paul D Johe
>Assignee: Claus Ibsen
>Priority: Major
>
> The DefaultFluentProducerTemplate saves state between method calls. This
> leads to unexpected behavior when the javadoc specifies that it should be
> thread safe.
> For example:
> # thread 1 calls fluentProducerTemplate.to("direct:a").send("message1");
> # thread 2 calls fluentProducerTemplate.to("direct:b").send("message2");
> If these are run in parallel, the sequence of calls can be:
> # thread 1 calls to("direct:a") - endpoint in the object is direct:a
> # thread 2 calls to("direct:b") - endpoint in the object is direct:b
> # *thread 1 calls send("message1") - this gets sent incorrectly to direct:b*
> # thread 2 calls send("message2") - this gets sent correctly to direct:b
> Endpoint is one example, but almost all fields in this class share this
> behavior. It should be clearly documented which fields can be used fluently
> over multiple threads, and which cannot. As the API is today, all methods
> returning 'this' should be made thread-safe (state is only local to the
> caller) so that the fluent interface works as expected.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (CAMEL-12981) camel-catalog: provide information about active/passive endpoints
[ https://issues.apache.org/jira/browse/CAMEL-12981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-12981: --- Assignee: Claus Ibsen > camel-catalog: provide information about active/passive endpoints > - > > Key: CAMEL-12981 > URL: https://issues.apache.org/jira/browse/CAMEL-12981 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Nicola Ferraro >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > In Camel K we need to distinguish active from passive endpoints in order to > determine when a integration can be scaled down to 0. > > E.g. > * a "timer" (start) endpoint is *active*, because it needs to have a JVM > always running and do something at each interval > * a "jms" (start) endpoint is *active* because it needs to establish a > connection to the broker and keep it alive > * a "direct" or "seda" endpoint is *passive*, because they do something when > they receive an exchange from another route > * a "undertow" (start) endpoint is *passive*, because it does nothing until > somebody calls it from an +external+ service (http based endpoints can all be > considered passive in Knative+CamelK) > > We should add this information to the catalog. Now I've embedded it in Camel > K. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-12962) Allow from and size for SearchSource / SearchRequest to be set via URI
[ https://issues.apache.org/jira/browse/CAMEL-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12962: Estimated Complexity: Novice (was: Unknown) > Allow from and size for SearchSource / SearchRequest to be set via URI > -- > > Key: CAMEL-12962 > URL: https://issues.apache.org/jira/browse/CAMEL-12962 > Project: Camel > Issue Type: Improvement > Components: camel-elasticsearch-rest >Affects Versions: 2.22.1 >Reporter: Derek White >Priority: Minor > > There is currently no straightforward way that I know of to request more than > the first 10 search results. Please allow from and size for SearchSource / > SearchRequest to be set via URI. > To add, since the ElasticsearchActionRequestConverter actually pulls the root > node of the Query DSL, setting from and size in the request body string or > Map is actually ignored. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-11708) spring boot code generation: the nested property processor does not handle object hierarchies
[
https://issues.apache.org/jira/browse/CAMEL-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897423#comment-16897423
]
Claus Ibsen commented on CAMEL-11708:
-
I think this works today if not mistaking
> spring boot code generation: the nested property processor does not handle
> object hierarchies
> -
>
> Key: CAMEL-11708
> URL: https://issues.apache.org/jira/browse/CAMEL-11708
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.0.0
>
>
> Assuming you have complex configuration object that inherits from another
> configuration object, the spring boot code generation will creates the
> configuration properties object only for the properties of the last class so
> i.e. for a simple hierarchy like:
> {code}
> Common {
> String getX()
> void setX(String);
> }
> Specific extends Common {
> String getY()
> void setY(String);
> }
> {code}
> the generator will provides bindings only for
> {code}
> String getX()
> setX(String)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-11722) catalog: it should be possible to enrich catalogs's data with custom json
[
https://issues.apache.org/jira/browse/CAMEL-11722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-11722.
-
Resolution: Won't Fix
> catalog: it should be possible to enrich catalogs's data with custom json
> -
>
> Key: CAMEL-11722
> URL: https://issues.apache.org/jira/browse/CAMEL-11722
> Project: Camel
> Issue Type: Improvement
> Components: camel-catalog
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0
>
>
> I may be useful to have the catalog to load additional catalog properties
> like i.e. [spring-boot meta
> data|https://docs.spring.io/spring-boot/docs/current/reference/html/configuration-metadata.html#configuration-metadata-additional-metadata]
> so one can add information about additional stuffs like extensions.
> The extension files could be placed in META-INF/camel/catalog with a content
> like:
> {code}
> {
> "extensions": {
> "my.Extension.class": {
> "inheritsProperties": true,
> "properties": {
>
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAMEL-11887) JDK9 - Module names for Apache Camel
[ https://issues.apache.org/jira/browse/CAMEL-11887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897420#comment-16897420 ] Claus Ibsen commented on CAMEL-11887: - I dont think its worth the pain and effort for this, and nobody is asking for this. > JDK9 - Module names for Apache Camel > > > Key: CAMEL-11887 > URL: https://issues.apache.org/jira/browse/CAMEL-11887 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > We should decide what JDK9 module name to use for Apache Camel. > There is a bit of information about this at this PR > https://github.com/apache/camel/pull/2007 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-12851) org.apache.camel.component.validator.CustomSchemaFactoryFeatureTest.testCustomSchemaFactory() failing with JDK 10
[
https://issues.apache.org/jira/browse/CAMEL-12851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12851.
-
Resolution: Fixed
Fix Version/s: (was: Future)
3.0.0.M5
> org.apache.camel.component.validator.CustomSchemaFactoryFeatureTest.testCustomSchemaFactory()
> failing with JDK 10
> -
>
> Key: CAMEL-12851
> URL: https://issues.apache.org/jira/browse/CAMEL-12851
> Project: Camel
> Issue Type: Bug
> Components: tests
>Reporter: Aurélien Pupier
>Priority: Minor
> Fix For: 3.0.0.M5
>
>
> creating an issue to discuss a bit more about it.
> the code is:
> {quote} ValidatorComponent v = new ValidatorComponent();
> v.setCamelContext(context);
>
> v.createEndpoint("validator:org/apache/camel/component/validator/unsecuredSchema.xsd?schemaFactory=#MySchemaFactory");
>
> try {
>
> v.createEndpoint("validator:org/apache/camel/component/validator/unsecuredSchema.xsd");
> // we should get an security exception in JDK 7 with Oracle or
> Sun JDK
> String jdkVendor = System.getProperty("java.vm.vendor");
> if (jdkVendor != null && (jdkVendor.indexOf("Oracle") > 0 ||
> jdkVendor.indexOf("Sun") > 0)) {
> fail("Expect exception here");
> }
> } catch (Exception ex) {
> // do nothing here
> }{quote}
> in fact, it seems that there is never an exception that is thrown. it is not
> failing because jdkVendor.indexOf("oracle") returns 0 and the check is
> against > 0. i think it should be > -1
> So I would say that there is no exception thrown for a long time, perhaps
> even when it was added (would worth trying to set back to this almost years
> commit)
> There is no bug number so don't know why an exception was expected exactly
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (CAMEL-12845) Create a full Groovy DSL
[
https://issues.apache.org/jira/browse/CAMEL-12845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-12845:
Fix Version/s: (was: 3.0.0)
3.x
> Create a full Groovy DSL
>
>
> Key: CAMEL-12845
> URL: https://issues.apache.org/jira/browse/CAMEL-12845
> Project: Camel
> Issue Type: New Feature
> Components: camel-groovy
>Reporter: Luca Burgazzoli
>Priority: Minor
> Labels: scripting
> Fix For: 3.x
>
>
> It would be nice to have a nice dsl set up a camel context in groovy similar
> to what it is possible with Spring or Blueprint DSL, something like
> {code:java}
> context {
> restConfiguration {
>
> }
>registry {
>bind 'myKey', 'myValue'
>}
>beans {
>bean('myProcessor') {
>exchange -> exchange.in.body = 'hello'
>}
>}
> from(t'imer:tick')
> .to('log:end')
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAMEL-12620) CompletionAwareAggregationStrategy onCompletition method null exchange.
[
https://issues.apache.org/jira/browse/CAMEL-12620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897411#comment-16897411
]
Claus Ibsen commented on CAMEL-12620:
-
We need a much simpler reproducer of this issue you think there is.
> CompletionAwareAggregationStrategy onCompletition method null exchange.
> ---
>
> Key: CAMEL-12620
> URL: https://issues.apache.org/jira/browse/CAMEL-12620
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Luis Miguel
>Priority: Major
>
> Hello.
>
> We have a camel project to process some Csv files, we created a class
> implementing "CompletionAwareAggregationStrategy" in order to aggregate each
> row processed and we override the methods "aggregate" and "onCompletion" from
> it.
> The way we process the Csv file is parallelized with the "parallelProcessing"
> and indicating an "executorService" with 8 concurrently threads.
>
> We are having a weird issue that rarely happens, and is that in the middle of
> the process of the file, the method "onCompletion" is being called (even when
> the file is not complete yet) and it sets the argument "Exchange" as NULL so
> the whole camel route is messed up.
> As I said this rarely happens when we try to reprocess the file the error is
> gone.
>
>
>
> Here's the main route that process the CSV file, notice that for the split
> process we create an instance of "CsvAggregationStrategy"
>
> {code:java}
> @Qualifier("executorServicePublicationItemCsv")
> @Autowired
> private ExecutorService executorService;
> @Override
> public void configure() throws Exception {
> String[] header = Arrays.stream(PublicationItemCsvFields.values())
> .map(PublicationItemCsvFields::getText).toArray(String[]::new);
> Map csvFieldsByEntityAttribute = new HashMap<>();
> mapFields(csvFieldsByEntityAttribute);
> //@formatter:off
> from("file:publicationItemData?delete={{routes.push-csv-to-service.delete-source-file}}")
> .streamCaching()
> .routeId("push-publication-item-csv-to-service")
> .onException(Exception.class)
> .handled(true)
> .log(LoggingLevel.ERROR, "Error in publication item route, sending an email:
> ${exception.message} ${exception.stacktrace}")
> .to("direct:sendImportErrorReport")
> .end()
> .log(LoggingLevel.INFO, "Beginning to import publication item CSV:
> ${file:onlyname}")
> .unmarshal(new CsvDataFormat()
> .setSkipHeaderRecord(true)
> .setNullString(EMPTY)
> .setLazyLoad(true))
> .split(body(), new CsvAggregationStrategy())
> .streaming()
> .parallelProcessing().executorService(executorService)
> .to("direct:publication-item-splitter")
> .end()
> .choice()
> .when(simple("${exchangeProperty.aggregationError} != null"))
> .log("An error occurred when aggregating exchanges, sending an email with the
> error.")
> .setProperty("original_body", body())
> .to("direct:sendAggregationErrorEmail")
> .setBody(exchangeProperty("original_body"))
> .end()
> .choice()
> .when(simple("${exchangeProperty.badCsvData.size()} > 0"))
> .setBody(simple("${exchangeProperty.badCsvData}"))
> .marshal(new CsvDataFormat().setHeader(header))
> .setProperty("badRowsBody").simple("${body}")
> .end()
> .choice()
> .when(simple("${exchangeProperty.successfulRecords.size()} > 0"))
> .setBody(simple("${exchangeProperty.successfulRecords}"))
> .marshal(new CsvDataFormat().setHeader(header))
> .setProperty("successfulRowsBody").simple("${body}")
> .end()
> .to("direct:sendImportReport").end()
> .log("Completed import for publication item CSV: '${file:onlyname}'");
> from("direct:publication-item-splitter")
> .streamCaching()
> .routeId("push-publication-item-splitter")
> .onException(PublicationItemImportException.class)
> .handled(true)
> .log(LoggingLevel.ERROR, "Error importing publication item data:
> ${exception.message} ${exception.stacktrace}")
> .end()
> .onException(HttpHostConnectException.class)
> .handled(true)
> .log(LoggingLevel.ERROR, "Error connecting to publication item service host:
> ${exception.host}. Request body: ${body}")
> .end()
> .onException(HttpOperationFailedException.class)
> .handled(true)
> .log(LoggingLevel.ERROR, "Error received from publication item service: HTTP
> ${exception.statusCode}. Response body: ${exception.responseBody}. Request
> body: ${body}")
> .end()
> .onException(Exception.class)
> .handled(true)
> .log(LoggingLevel.ERROR, "Error: ${exception.message}
> ${exception.stacktrace}")
> .end()
> .setProperty("csvRowData").simple("${body}", List.class)
> .setProperty("csvFieldsByEntityAttribute").constant(csvFieldsByEntityAttribute)
> .bean(publicationItemCSVDataHandler)
> .marshal().json(JsonLibrary.Jackson)
> .setHeader(HttpHeaders.AUTHORIZATION, simple("Basic
> "+propertyServiceAuthorization))
> .log("Item ID: ${property.itemId}")
> .choice()
>
[jira] [Resolved] (CAMEL-12678) Unmarshalling with JAXBContext does not work: JAXB 2.3.0.1 in camel-spring-boot 2.22.0
[
https://issues.apache.org/jira/browse/CAMEL-12678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12678.
-
Resolution: Abandoned
> Unmarshalling with JAXBContext does not work: JAXB 2.3.0.1 in
> camel-spring-boot 2.22.0
> --
>
> Key: CAMEL-12678
> URL: https://issues.apache.org/jira/browse/CAMEL-12678
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
>Affects Versions: 2.22.0
>Reporter: storage
>Assignee: Zoran Regvart
>Priority: Minor
>
> * camel-spring-boot-starter 2.22.0
> ** camel-spring-boot 2.22.0
> *** jaxb-core 2.3.0.1
> *** jaxb-impl 2.3.0.1
> In some code we have we use JAXB to unmarschall some XML to a POJO class we
> have containing a RedeliveryPolicyDefinition as a property.
> This seems to fail without errors and the property remains null.
> When we replace _*jaxb-core*_ and _*jaxb-impl*_ version *2.3.0.1* to
> *2.2.11* the code seems to work again.
> Unmarshalling code:
> {code:java}
> JAXBContext ctx = JAXBContext.newInstance(ErrorHandler.class);
> JAXBElement errorHandler =
> ctx.createUnmarshaller().unmarshal(beanList.item(i), ErrorHandler.class);
> {code}
> Pojo:
> {code:java}
> @Getter
> @Setter
> @XmlRootElement(name = "errorHandler", namespace =
> "http://camel.apache.org/schema/spring;)
> @XmlAccessorType(XmlAccessType.FIELD)
> public class ErrorHandler {
> @XmlAttribute
> private String id;
> @XmlElement
> private RedeliveryPolicyDefinition redeliveryPolicy;
> @XmlAttribute
> private org.apache.camel.spring.ErrorHandlerType type;
> {code}
> XML:
> {code:xml}
>
> http://camel.apache.org/schema/spring; id="eh-http"
> type="DefaultErrorHandler">
> backOffMultiplier="2" useExponentialBackOff="true"/>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (CAMEL-12662) spring boot starter : auto generated starters with apt
[ https://issues.apache.org/jira/browse/CAMEL-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12662: Fix Version/s: (was: 3.0.0) 3.x > spring boot starter : auto generated starters with apt > -- > > Key: CAMEL-12662 > URL: https://issues.apache.org/jira/browse/CAMEL-12662 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot-starters, tooling >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 3.x > > > As today the auto generated auto configurations happen using a mix of camel > catalog, java source code parsing and other hacks which makes the process > hard to maintain. > In camel 3.0 we should improve annotations an leverage APT to generate the > starters. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-12202) FluentProducerTemplate: add withProper(y|ies) methods
[ https://issues.apache.org/jira/browse/CAMEL-12202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12202. - Resolution: Won't Fix > FluentProducerTemplate: add withProper(y|ies) methods > - > > Key: CAMEL-12202 > URL: https://issues.apache.org/jira/browse/CAMEL-12202 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Brett E. Meyer >Priority: Minor > Fix For: Future > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-12617) Upgrade ASM to 6.1 or newer
[
https://issues.apache.org/jira/browse/CAMEL-12617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12617.
-
Resolution: Fixed
Fix Version/s: 3.0.0
We use asm v7
> Upgrade ASM to 6.1 or newer
> ---
>
> Key: CAMEL-12617
> URL: https://issues.apache.org/jira/browse/CAMEL-12617
> Project: Camel
> Issue Type: Sub-task
> Components: camel-package-maven-plugin
>Reporter: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0
>
>
> ASM 6.1 brings in Java 10 support, 6.2 has experimental Java 11 support.
> camel-package-maven-plugin ASM issue on JDK 10 from the daily build:
> {code}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal
> org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT:prepare-readme
> (default) on project camel-catalog: Execution default of goal
> org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT:prepare-readme
> failed: An API incompatibility was encountered while executing
> org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT:prepare-readme:
> java.lang.VerifyError: (class: ASMAccessorImpl_108379339615305901704587,
> method: getKnownEgressType signature: ()Ljava/lang/Class;) Illegal type in
> constant pool
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-12595) Camel Kafka DEBUG level java.io.EOFException
[
https://issues.apache.org/jira/browse/CAMEL-12595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12595.
-
Resolution: Cannot Reproduce
Closing old ticket, try with newer version and looks not like a Camel issue
really
> Camel Kafka DEBUG level java.io.EOFException
>
>
> Key: CAMEL-12595
> URL: https://issues.apache.org/jira/browse/CAMEL-12595
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
>Affects Versions: 2.21.1
> Environment: * *ActiveMQ* v5.15.4
> * *Camel*: 2.21.1
> * *Kafka Clients*:1.1.0
> * *Server version*: Apache/2.4.6 (CentOS)
>Reporter: Lizuca Mihaescu
>Priority: Major
>
> I am trying to produce messages to Kafka (Cloudera) from an ActiveMQ-Camel
> bridge using *Kerberos* and I am getting at INFO level a warning and the
> messages are not delivered.
> {code:java}
> WARN | [Producer clientId=producer-1] Bootstrap broker 10.100.70.00:9092 (id:
> -1 rack: null) disconnected | org.apache.kafka.clients.NetworkClient |
> kafka-producer-network-thread | producer-1
> {code}
> {{At debug level I find the following error:}}
> {code:java}
> java.io.EOFException
> at
> org.apache.kafka.common.network.NetworkReceive.readFromReadableChannel(NetworkReceive.java:124)[kafka-clients-1.1.0.jar:]
> at
> org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:93)[kafka-clients-1.1.0.jar:]
> at
> org.apache.kafka.common.network.KafkaChannel.receive(KafkaChannel.java:235)[kafka-clients-1.1.0.jar:]
> at
> org.apache.kafka.common.network.KafkaChannel.read(KafkaChannel.java:196)[kafka-clients-1.1.0.jar:]
> at
> org.apache.kafka.common.network.Selector.attemptRead(Selector.java:557)[kafka-clients-1.1.0.jar:]
> at
> org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:495)[kafka-clients-1.1.0.jar:]
> at
> org.apache.kafka.common.network.Selector.poll(Selector.java:424)[kafka-clients-1.1.0.jar:]
> at
> org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:460)[kafka-clients-1.1.0.jar:]
> at
> org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:239)[kafka-clients-1.1.0.jar:]
> at
> org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:163)[kafka-clients-1.1.0.jar:]
> at java.lang.Thread.run(Thread.java:748)[:1.8.0_171
> {code}
> {{This is the kafka client config from log:}}
> {code:java}
> acks = 1
> batch.size = 16384
> bootstrap.servers = [10.148.70.74:9092]
> buffer.memory = 33554432
> client.id =
> compression.type = none
> connections.max.idle.ms = 54
> enable.idempotence = false
> interceptor.classes = []
> key.serializer = class
> org.apache.kafka.common.serialization.ByteArraySerializer
> linger.ms = 0
> max.block.ms = 6
> max.in.flight.requests.per.connection = 5
> max.request.size = 1048576
> metadata.max.age.ms = 30
> metric.reporters = []
> metrics.num.samples = 2
> metrics.recording.level = INFO
> metrics.sample.window.ms = 3
> partitioner.class = class
> org.apache.kafka.clients.producer.internals.DefaultPartitioner
> receive.buffer.bytes = 65536
> reconnect.backoff.max.ms = 1000
> reconnect.backoff.ms = 50
> request.timeout.ms = 305000
> retries = 3
> retry.backoff.ms = 100
> sasl.jaas.config = null
> sasl.kerberos.kinit.cmd = /usr/bin/kinit
> sasl.kerberos.min.time.before.relogin = 6
> sasl.kerberos.service.name = kafka
> sasl.kerberos.ticket.renew.jitter = 0.05
> sasl.kerberos.ticket.renew.window.factor = 0.8
> sasl.mechanism = GSSAPI
> security.protocol = PLAINTEXT
> send.buffer.bytes = 131072
> ssl.cipher.suites = null
> ssl.enabled.protocols = [TLSv1.2, TLSv1.1, TLSv1]
> ssl.endpoint.identification.algorithm = null
> ssl.key.password = null
> ssl.keymanager.algorithm = SunX509
> ssl.keystore.location = null
> ssl.keystore.password = null
> ssl.keystore.type = JKS
> ssl.protocol = TLS
> ssl.provider = null
> ssl.secure.random.implementation = null
> ssl.trustmanager.algorithm = PKIX
> ssl.truststore.location = null
> ssl.truststore.password = null
> ssl.truststore.type = JKS
> transaction.timeout.ms = 6
> transactional.id = null
> value.serializer = class
> org.apache.kafka.common.serialization.ByteArraySerializer
> {code}
> {{I am using Jaas file:}}
> {code:java}
> KafkaClient {
> com.sun.security.auth.module.Krb5LoginModule required
> useKeyTab=true
> storeKey=true
> keyTab="./user.keytab"
> useTicketCache=false
> serviceName="kafka"
> principal=" Group/u...@domain.lan";
> };
> {code}
> {{So, my problem here is that if the authentication fails in any way I shall
> receive an error with a meaningful explanation otherwise I cannot tell
> whether or not the messages were correctly routed and the
[jira] [Resolved] (CAMEL-5717) Allow use of Routebuilder in RouteContext in XML schema
[
https://issues.apache.org/jira/browse/CAMEL-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-5717.
Resolution: Won't Fix
> Allow use of Routebuilder in RouteContext in XML schema
> ---
>
> Key: CAMEL-5717
> URL: https://issues.apache.org/jira/browse/CAMEL-5717
> Project: Camel
> Issue Type: New Feature
> Components: camel-blueprint, camel-core, camel-spring
>Affects Versions: 2.10.1
>Reporter: Robert Stepanek
>Priority: Major
> Labels: context, route
> Fix For: Future, 3.0.0
>
>
> Currently, the XML schema does not permit use of RouteBuilders in a
> RouteContext.
> This has been discussed on the mailing list:
> [http://camel.465427.n5.nabble.com/RouteBuilder-not-allowed-in-RouteContext-why-td5721184.html]
> The improvement would add {{camelContext}}'s powerful feature of mixing Java
> DSL and XML based route declarations also to the {{routeContext}}.
> For illustration, the following XML does not validate since the
> {{camel:routeBuilder}} element is not allowed in a {{camel:routeContext}}:
> {code}
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-12413) Camel Tracer - Improve default formatting output
[ https://issues.apache.org/jira/browse/CAMEL-12413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12413. - Resolution: Fixed Assignee: Claus Ibsen Fix Version/s: (was: Future) 3.0.0 A new tracer has nicer formatting output > Camel Tracer - Improve default formatting output > > > Key: CAMEL-12413 > URL: https://issues.apache.org/jira/browse/CAMEL-12413 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > If you turn on tracing > [http://camel.apache.org/tracer] > Then the default logging output is a bit dense. We could look at improve the > formatting so the details is logged more nicely. > Some components has a lot of details stored in headers/exchange properties > and whatnot that makes the output very verbose, such as camel-cxf. > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (CAMEL-11391) Add camel:route-trace and camel:context-mdc commands
[
https://issues.apache.org/jira/browse/CAMEL-11391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-11391:
---
Assignee: (was: Jean-Baptiste Onofré)
> Add camel:route-trace and camel:context-mdc commands
>
>
> Key: CAMEL-11391
> URL: https://issues.apache.org/jira/browse/CAMEL-11391
> Project: Camel
> Issue Type: Improvement
> Components: karaf
>Reporter: Jean-Baptiste Onofré
>Priority: Minor
>
> In order to allow users to turn on/off the tracer on a route or the MDC on a
> Camel Context, it would be convenient to have corresponding
> {{camel:route-trace}} and {{camel:context-mdc}} Karaf commands.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (CAMEL-12003) FailFast mode for unit tests
[ https://issues.apache.org/jira/browse/CAMEL-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12003: Fix Version/s: 3.0.0.M5 3.0.0 > FailFast mode for unit tests > - > > Key: CAMEL-12003 > URL: https://issues.apache.org/jira/browse/CAMEL-12003 > Project: Camel > Issue Type: Wish > Components: camel-test >Reporter: Robert Half >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > > Is it possible to create a "fail fast" unit test for apache camel? > I'm using MockEndpoint in camel unit tests, provide some expectations like > message count. And do a call to assertIsSatisfied. > This waits until success or timeout, so if an exchange fails, my test waits > for timeout extending the duration. For most tests it's true that a failed > exchange means the test will fail. It would be nice that it fails fast - > after throwing the exception and not waiting for timeout. For reference > please check: > https://stackoverflow.com/questions/47202346/fail-fast-apache-camel-unit-test/47225454#47225454 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-12003) FailFast mode for unit tests
[ https://issues.apache.org/jira/browse/CAMEL-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12003: Component/s: (was: tests) camel-test > FailFast mode for unit tests > - > > Key: CAMEL-12003 > URL: https://issues.apache.org/jira/browse/CAMEL-12003 > Project: Camel > Issue Type: Wish > Components: camel-test >Reporter: Robert Half >Priority: Major > > Is it possible to create a "fail fast" unit test for apache camel? > I'm using MockEndpoint in camel unit tests, provide some expectations like > message count. And do a call to assertIsSatisfied. > This waits until success or timeout, so if an exchange fails, my test waits > for timeout extending the duration. For most tests it's true that a failed > exchange means the test will fail. It would be nice that it fails fast - > after throwing the exception and not waiting for timeout. For reference > please check: > https://stackoverflow.com/questions/47202346/fail-fast-apache-camel-unit-test/47225454#47225454 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (CAMEL-12003) FailFast mode for unit tests
[ https://issues.apache.org/jira/browse/CAMEL-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-12003: --- Assignee: Claus Ibsen > FailFast mode for unit tests > - > > Key: CAMEL-12003 > URL: https://issues.apache.org/jira/browse/CAMEL-12003 > Project: Camel > Issue Type: Wish > Components: camel-test >Reporter: Robert Half >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > > Is it possible to create a "fail fast" unit test for apache camel? > I'm using MockEndpoint in camel unit tests, provide some expectations like > message count. And do a call to assertIsSatisfied. > This waits until success or timeout, so if an exchange fails, my test waits > for timeout extending the duration. For most tests it's true that a failed > exchange means the test will fail. It would be nice that it fails fast - > after throwing the exception and not waiting for timeout. For reference > please check: > https://stackoverflow.com/questions/47202346/fail-fast-apache-camel-unit-test/47225454#47225454 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13809) many erroneous links in the doc
[ https://issues.apache.org/jira/browse/CAMEL-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-13809: -- Description: Hi, many erroneous links in the doc I manually passed all links on the page. I read the returns to make sure they were still valid. when there was manual redirection I followed the link to check it. here is the list of errors that I found. a not about fusesource. all fusesource links are redirected to www.jboss.org. this does not allow to find the targeted document. hoping that this can be helpful. [https://camel.apache.org/staging/community/articles/] videos Wild Flies and A Camel [https://www.youtube.com/watch?v=o8ZRE9DM3Es] video not found Camel in the cloud using Fuse Fabric [http://fuse.fusesource.org/fabric/] time out Getting started with Apache Camel - Video presentation from Javagruppen [https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus] 404 Apache Camel Essential Components by Christian Posta [http://blip.tv/dzone/apache-camel-essential-components-6511579] Error 523 CamelOne 2012 Videos - All the videos [http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/] and [http://fusesource.com/apache-camel-conference-2012] redirect to jboss.org CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all links redirected to jboss.org Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard [http://www.parleys.com/#id=2432=5=0] blank page Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles Moulliard [http://www.parleys.com/#id=2601=5] blank page Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix [https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF] blank page errors on html structure Devoxx 2010 talk [http://www.parleys.com/#id=2158=5] blank page errors on html structure at Øredev 2008 conference [http://www.oredev.com/] 404 not found Devoxx 2009 talk [http://www.parleys.com/#sl=11=5=1577] blank page Medium Resolution [http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/] unreachable High Resolution [http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/] unreachable Taking Camel for a ride [http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html] time out JavaZone Conference - Taking Apache Camel for a Rider [http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html] time out Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT [http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968] Not found Facebook integration Apache Camel [http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel] not found Advanced AEM Search - Consuming External Content [http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html] HTTP ERROR 503 Articles Integration with Apache Camel - Part I - Will get you over [http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05] not found Simple DSL OSGi bundle example by Andrej Koelewijn [http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/] not found Realization of EAI Patterns with Apache Camel by Pascal Kolb [http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf] OPUS-ID 3520 nicht gefunden! (redirect error) First step with Apache Camel by Lukasz Budnik [http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html] Sorry, the page you were looking for in this blog does not exist. LEGO Java: Apache Camel Context and Route Basics [http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/] not found LEGO® Java (II): Apache Camel Error Handling, [http://www.canoo.com/blog/2011/03/16/lego-java-ii-apache-camel-error-handling-java-beans-and-web-services/] not found What is Camel? a short blog [http://bushorn.com/what-is-camel/] Error establishing a database connection A bit more meat: Camel applied : JMS to File [http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/] not found Spring Remoting with JMS Example on Amin Abbaspour’s Weblog the second link [http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html] Le blog a été supprimé blog removed Camel routes and HL7 by Roger Searjeant [http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html] => blog removed Leverage EIP with Apache Camel and Twitter [http://blog.brunoborges.com.br/2009/03/leverage-eip-with-apache-camel-and.html] ERR_NAME_NOT_RESOLVED Camel, CXF and JMS by Example by Silvester van der Bijl [http://blog.software-art.nl/2009/11/15/camel-cxf-and-jms-by-example/] time out A simple file monitoring console with
[jira] [Updated] (CAMEL-13809) many erroneous links in the doc
[ https://issues.apache.org/jira/browse/CAMEL-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terrien Jean-Yves updated CAMEL-13809: -- Environment: (was: https://camel.apache.org/staging/community/articles/ videos Wild Flies and A Camel https://www.youtube.com/watch?v=o8ZRE9DM3Es video not found Camel in the cloud using Fuse Fabric http://fuse.fusesource.org/fabric/ time out Getting started with Apache Camel - Video presentation from Javagruppen https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus 404 Apache Camel Essential Components by Christian Posta http://blip.tv/dzone/apache-camel-essential-components-6511579 Error 523 CamelOne 2012 Videos - All the videos http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/ and http://fusesource.com/apache-camel-conference-2012 redirect to jboss.org CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all links redirected to jboss.org Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard http://www.parleys.com/#id=2432=5=0 blank page Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles Moulliard http://www.parleys.com/#id=2601=5 blank page Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF blank page errors on html structure Devoxx 2010 talk http://www.parleys.com/#id=2158=5 blank page errors on html structure at Øredev 2008 conference http://www.oredev.com/ 404 not found Devoxx 2009 talk http://www.parleys.com/#sl=11=5=1577 blank page Medium Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/ unreachable High Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/ unreachable Taking Camel for a ride http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html time out JavaZone Conference - Taking Apache Camel for a Rider http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html time out Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968 Not found Facebook integration Apache Camel http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel not found Advanced AEM Search - Consuming External Content http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html HTTP ERROR 503 Articles Integration with Apache Camel - Part I - Will get you over http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05 not found Simple DSL OSGi bundle example by Andrej Koelewijn http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/ not found Realization of EAI Patterns with Apache Camel by Pascal Kolb http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf OPUS-ID 3520 nicht gefunden! (redirect error) First step with Apache Camel by Lukasz Budnik http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html Sorry, the page you were looking for in this blog does not exist. LEGO Java: Apache Camel Context and Route Basics http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/ not found LEGO® Java (II): Apache Camel Error Handling, http://www.canoo.com/blog/2011/03/16/lego-java-ii-apache-camel-error-handling-java-beans-and-web-services/ not found What is Camel? a short blog http://bushorn.com/what-is-camel/ Error establishing a database connection A bit more meat: Camel applied : JMS to File http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/ not found Spring Remoting with JMS Example on Amin Abbaspour’s Weblog the second link http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html Le blog a été supprimé blog removed Camel routes and HL7 by Roger Searjeant http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html => blog removed Leverage EIP with Apache Camel and Twitter http://blog.brunoborges.com.br/2009/03/leverage-eip-with-apache-camel-and.html ERR_NAME_NOT_RESOLVED Camel, CXF and JMS by Example by Silvester van der Bijl http://blog.software-art.nl/2009/11/15/camel-cxf-and-jms-by-example/ time out A simple file monitoring console with camel, cometd and jquery http://www.andrejkoelewijn.com/wp/2009/10/27/simple-log-console-with-camel-and-cometd/ not found A composite REST service using Apache Camel by Andrej Koelewijn http://www.andrejkoelewijn.com/wp/2010/06/13/a-composite-rest-service-using-camel/ not found Using Apache Camel to route SOAP calls through message queues by Glen Mazza http://www.jroller.com/gmazza/entry/camel_jms_and_soap time out Using Apache Camel to route SOAP calls
[jira] [Created] (CAMEL-13809) many erroneous links in the doc
Terrien Jean-Yves created CAMEL-13809: - Summary: many erroneous links in the doc Key: CAMEL-13809 URL: https://issues.apache.org/jira/browse/CAMEL-13809 Project: Camel Issue Type: Bug Components: documentation Environment: https://camel.apache.org/staging/community/articles/ videos Wild Flies and A Camel https://www.youtube.com/watch?v=o8ZRE9DM3Es video not found Camel in the cloud using Fuse Fabric http://fuse.fusesource.org/fabric/ time out Getting started with Apache Camel - Video presentation from Javagruppen https://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus 404 Apache Camel Essential Components by Christian Posta http://blip.tv/dzone/apache-camel-essential-components-6511579 Error 523 CamelOne 2012 Videos - All the videos http://fusesource.com/apache-camel-conference-2012/camelone_speakers_2012/ and http://fusesource.com/apache-camel-conference-2012 redirect to jboss.org CamelOne 2011 Video presentations CamelOne 2011 conference (May 2011) all links redirected to jboss.org Paris JUG 2011 - Integration with Apache Camel and ESB by Charles Moulliard http://www.parleys.com/#id=2432=5=0 blank page Belgium JUG 2011 - Integration with Apache ServiceMix and Camel by Charles Moulliard http://www.parleys.com/#id=2601=5 blank page Devoxx 2011 - Introduction to Apache ActiveMQ, ServiceMix https://devoxx.com/display/DV11/Introduction+to+Apache+ActiveMQ,+ServiceMix,+Camel+and+CXF blank page errors on html structure Devoxx 2010 talk http://www.parleys.com/#id=2158=5 blank page errors on html structure at Øredev 2008 conference http://www.oredev.com/ 404 not found Devoxx 2009 talk http://www.parleys.com/#sl=11=5=1577 blank page Medium Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-medium-resolution/ unreachable High Resolution http://open.iona.com/resources/video-archived-webinars/camel-screencast-1-high-resolution/ unreachable Taking Camel for a ride http://bsnyderblog.blogspot.com/2008/05/activemq-and-servicemix-at-apachecon-us.html time out JavaZone Conference - Taking Apache Camel for a Rider http://www4.java.no/incogito/session/Taking+Apache+Camel+for+a+Ride.html time out Screencast/Demo of Smooks and Apache Camel processing UN/EDIFACT http://www.screencast.com/users/tfennelly/folders/Camtasia/media/c3cef9dd-e667-41ac-8597-74ca01d39968 Not found Facebook integration Apache Camel http://screencasts.chariotsolutions.com/facebook-integration-using-apache-camel not found Advanced AEM Search - Consuming External Content http://www.circuitdevcon.com/en/session-videos/aem-search-apache-camel.html HTTP ERROR 503 Articles Integration with Apache Camel - Part I - Will get you over http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05 not found Simple DSL OSGi bundle example by Andrej Koelewijn http://www.andrejkoelewijn.com/wp/2008/10/19/simple-camel-dsl-osgi-bundle-example/ not found Realization of EAI Patterns with Apache Camel by Pascal Kolb http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf OPUS-ID 3520 nicht gefunden! (redirect error) First step with Apache Camel by Lukasz Budnik http://jee-bpel-soa.blogspot.com/2009/12/first-steps-with-apache-camel.html Sorry, the page you were looking for in this blog does not exist. LEGO Java: Apache Camel Context and Route Basics http://www.canoo.com/blog/2011/03/14/lego-java-apache-camel-context-and-route-basics/ not found LEGO® Java (II): Apache Camel Error Handling, http://www.canoo.com/blog/2011/03/16/lego-java-ii-apache-camel-error-handling-java-beans-and-web-services/ not found What is Camel? a short blog http://bushorn.com/what-is-camel/ Error establishing a database connection A bit more meat: Camel applied : JMS to File http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/ not found Spring Remoting with JMS Example on Amin Abbaspour’s Weblog the second link http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html Le blog a été supprimé blog removed Camel routes and HL7 by Roger Searjeant http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html => blog removed Leverage EIP with Apache Camel and Twitter http://blog.brunoborges.com.br/2009/03/leverage-eip-with-apache-camel-and.html ERR_NAME_NOT_RESOLVED Camel, CXF and JMS by Example by Silvester van der Bijl http://blog.software-art.nl/2009/11/15/camel-cxf-and-jms-by-example/ time out A simple file monitoring console with camel, cometd and jquery http://www.andrejkoelewijn.com/wp/2009/10/27/simple-log-console-with-camel-and-cometd/ not found A composite REST service using Apache Camel by Andrej Koelewijn http://www.andrejkoelewijn.com/wp/2010/06/13/a-composite-rest-service-using-camel/ not found Using Apache Camel to route SOAP calls through message queues by
[jira] [Commented] (CAMEL-13792) Rename components to default names
[ https://issues.apache.org/jira/browse/CAMEL-13792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897266#comment-16897266 ] Andrea Cosentino commented on CAMEL-13792: -- camel-http4 to camel-http, done > Rename components to default names > -- > > Key: CAMEL-13792 > URL: https://issues.apache.org/jira/browse/CAMEL-13792 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > > camel-quartz2 > - camel-netty4 > - camel-netty4-http > - camel-mongodb3 > - camel-mina2 > - camel-hdfs2 > - camel-rxjava2 > - camel-sjms2 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-11246) camel-catalog : provide information about the uri support for expressions
[ https://issues.apache.org/jira/browse/CAMEL-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11246: Fix Version/s: (was: Future) 3.0.0.M5 3.0.0 > camel-catalog : provide information about the uri support for expressions > - > > Key: CAMEL-11246 > URL: https://issues.apache.org/jira/browse/CAMEL-11246 > Project: Camel > Issue Type: Improvement >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.0.0, 3.0.0.M5 > > > Some component like camel-sql support expressions to be used inside the uri > definition and this may cause troubles in environment like spring as the > simple language prefix/suffix clash with spring's property resolution. > By providing some information about what languages the endpoint supports in > the camel-catalog, tools like IDEs or validation plugins can provide some > hints or warning to the user/developer. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (CAMEL-11246) camel-catalog : provide information about the uri support for expressions
[ https://issues.apache.org/jira/browse/CAMEL-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-11246: --- Assignee: Claus Ibsen > camel-catalog : provide information about the uri support for expressions > - > > Key: CAMEL-11246 > URL: https://issues.apache.org/jira/browse/CAMEL-11246 > Project: Camel > Issue Type: Improvement >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: Future > > > Some component like camel-sql support expressions to be used inside the uri > definition and this may cause troubles in environment like spring as the > simple language prefix/suffix clash with spring's property resolution. > By providing some information about what languages the endpoint supports in > the camel-catalog, tools like IDEs or validation plugins can provide some > hints or warning to the user/developer. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-6132) camel-test-karaf - To allow end users more easily do Camel and Karaf integration test
[ https://issues.apache.org/jira/browse/CAMEL-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6132. Resolution: Fixed Fix Version/s: (was: Future) 3.0.0 > camel-test-karaf - To allow end users more easily do Camel and Karaf > integration test > - > > Key: CAMEL-6132 > URL: https://issues.apache.org/jira/browse/CAMEL-6132 > Project: Camel > Issue Type: New Feature > Components: karaf >Reporter: Claus Ibsen >Assignee: Quinn Stevenson >Priority: Major > Fix For: 3.0.0 > > > We should introduce a proper camel-test-karaf component that *end users* can > use to do Camel and Karaf integration tests. > The code we have in tests/camel-itest-karaf is for internal usage and testing > of Camel. The code is not polished and intended for end users. > We should create a new module for that, and take the good parts of > camel-itest-karaf and make it user friendly etc. And of course have docs to > go with as well. > And when its good, we can use that in camel-itest-karaf also (eat our own dog > food) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-11566) Unified events in CamelContext
[ https://issues.apache.org/jira/browse/CAMEL-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11566: Fix Version/s: (was: 3.0.0) 3.x > Unified events in CamelContext > -- > > Key: CAMEL-11566 > URL: https://issues.apache.org/jira/browse/CAMEL-11566 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.x > > > - Have a single and complete source fo events, as today we can listen > for events using different concepts: > - LifecycleStrategy > - StartupListener > - EventNotifier > - RoutePolicy > Some of them seems overlapping a little so we may create 'contextual' > listeners like RouteEventListener, ExchangeEventListener, etc and > then i.e. the RoutePolicy could extend only what make sense for the > context so for the camel context prospective only an event has to be > fired. Listeenrs can eventually throw an uncheckd "VetoedException" > if the operation should not be done (i.e. a policy may prevent to > stop or start a route if certain circumstances). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-11565) Modular DefaultCamelContext
[ https://issues.apache.org/jira/browse/CAMEL-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11565: Fix Version/s: (was: 3.0.0) 3.x > Modular DefaultCamelContext > --- > > Key: CAMEL-11565 > URL: https://issues.apache.org/jira/browse/CAMEL-11565 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.x > > > - Add a concept of RouteLoader which is in charge of building the route > definitions from a source, to eventually monitor the source for > changes and then refresh the contex so i.e. we can move the current > process of loading routes from xml to a dedicated XMLRouteLoader. It > should be possible to add more loaders so one can load routes from > different sources (yaml, json, groovy) > - Add a concept of RouteControler which is in charge of routes' > life-cycle, this is partially done by CAMEL-11443 but for 2.x it will > be more a placeholder that an concrete implementation as the > life-cycle of routes involves quite a bit of code and it is quite hard > to introduce a proper life-cycle manager without breaking the things. > In my mind the camel context should be a bridge between RouteLoader > and the RouteController then the specific route controller can do its > job like: > - start routes in parallel > - handle reoutes dependencies (CAMEL-8599) > - restart failing routes > - etc -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-11176) Remove @Ignore on Camel Catalog Maven tests
[ https://issues.apache.org/jira/browse/CAMEL-11176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-11176. - Resolution: Fixed > 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 (v7.6.14#76016)
[jira] [Updated] (CAMEL-10910) Revisit if Pipeline should wrap single processor or not
[ https://issues.apache.org/jira/browse/CAMEL-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-10910: Fix Version/s: (was: 3.0.0) Future > Revisit if Pipeline should wrap single processor or not > --- > > Key: CAMEL-10910 > URL: https://issues.apache.org/jira/browse/CAMEL-10910 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Tomohisa Igarashi >Assignee: Tomohisa Igarashi >Priority: Major > Fix For: Future > > > I noticed that if eventDrivenProcessors contains only one processor, IN > message is not copied to OUT even when exchange pattern is InOut while it > does if it contains multiple processors. > eventDrivenProcessors are wrapped with Pipeline here when initiating a camel > route here: > https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/impl/DefaultRouteContext.java#L161 > But if there's only one event driven processor, the processor itself is used > instead of wrapping with Pipeline: > https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/processor/Pipeline.java#L57 > Pipeline copies the IN message to OUT if it's InOut and OUT message doesn't > exist: > https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/processor/Pipeline.java#L107 > So the IN->OUT copy happens only if multiple processors exist. It means that > whether the response message is returned as OUT or IN depends on if the route > results in single processor or not. I think it looks a bit confusing and > wondering if we can just wrap it with the Pipleline even if there's single > processor. > Having said that as this has been same for 10 years, we can't change this > behavior in 2.x as it would break backward compatibility. Let's revisit in > 3.0. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-10910) Revisit if Pipeline should wrap single processor or not
[ https://issues.apache.org/jira/browse/CAMEL-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897256#comment-16897256 ] Claus Ibsen commented on CAMEL-10910: - Moving to future > Revisit if Pipeline should wrap single processor or not > --- > > Key: CAMEL-10910 > URL: https://issues.apache.org/jira/browse/CAMEL-10910 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Tomohisa Igarashi >Assignee: Tomohisa Igarashi >Priority: Major > Fix For: Future > > > I noticed that if eventDrivenProcessors contains only one processor, IN > message is not copied to OUT even when exchange pattern is InOut while it > does if it contains multiple processors. > eventDrivenProcessors are wrapped with Pipeline here when initiating a camel > route here: > https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/impl/DefaultRouteContext.java#L161 > But if there's only one event driven processor, the processor itself is used > instead of wrapping with Pipeline: > https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/processor/Pipeline.java#L57 > Pipeline copies the IN message to OUT if it's InOut and OUT message doesn't > exist: > https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/processor/Pipeline.java#L107 > So the IN->OUT copy happens only if multiple processors exist. It means that > whether the response message is returned as OUT or IN depends on if the route > results in single processor or not. I think it looks a bit confusing and > wondering if we can just wrap it with the Pipleline even if there's single > processor. > Having said that as this has been same for 10 years, we can't change this > behavior in 2.x as it would break backward compatibility. Let's revisit in > 3.0. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-5918) Add performance tests
[ https://issues.apache.org/jira/browse/CAMEL-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-5918. Resolution: Abandoned > Add performance tests > - > > Key: CAMEL-5918 > URL: https://issues.apache.org/jira/browse/CAMEL-5918 > Project: Camel > Issue Type: New Feature > Components: tests >Affects Versions: 2.9.5, 2.10.3 >Reporter: Christian Müller >Priority: Major > Fix For: Future > > > By working on the "ESB Performance Testing - Round 7" > (http://www.esbperformance.org/) to provide a good/optimal ServiceMix & Camel > test set up I figured out, the performance for most of the test cases are > worse by upgrading from ServiceMix 4.4.2 (which use Camel 2.8.5) to > ServiceMix 4.5.0-SNAPSHOT (which use Camel 2.10.3). > The reason for this does not have to be a worse performance in Camel, but it > could. In these performance tests, I use ServiceMix/Karaf, Jetty, CXF, ... > and Camel of course. > To make sure the performance is not getting worse in a new Camel release, I > will add a few different performance test in the next days/weeks for the most > relevant use cases and the tests made by esbperformance.org. These test > should not be executed by default on the CI server. But we should run the > tests regularly from time to time and before we cut a new release. We also > can use these tests to profile Camel and check we can improve the > performance, independently how good the performance already is. > I'm wondering what is the best place for this module. I suggest > camel/tests/camel-performance. I don't know what the intension was for the > existing camel/tests/camel-itest-performance module? It doesn't contain > performance tests... -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-10639) camel-zookeeper - Add RoutePolicyFactory to manage all routes easily
[ https://issues.apache.org/jira/browse/CAMEL-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-10639. - Resolution: Not A Problem Use zookeeper-master for master/slave stuff > camel-zookeeper - Add RoutePolicyFactory to manage all routes easily > > > Key: CAMEL-10639 > URL: https://issues.apache.org/jira/browse/CAMEL-10639 > Project: Camel > Issue Type: Improvement > Components: camel-zookeeper >Reporter: Claus Ibsen >Priority: Minor > Fix For: Future > > > To easily manage all the routes in the master/slave scenario with the > CuratorRoutePolicy. Today you need to configure this on every route you want > managed. > But with a RoutePolicyFactory we can configure this once and it manages all > the routes. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-10642) support input/result/path support when invoking a `to` endpoint
[
https://issues.apache.org/jira/browse/CAMEL-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-10642.
-
Resolution: Won't Fix
> support input/result/path support when invoking a `to` endpoint
> ---
>
> Key: CAMEL-10642
> URL: https://issues.apache.org/jira/browse/CAMEL-10642
> Project: Camel
> Issue Type: Improvement
>Reporter: james strachan
>Priority: Major
>
> there's an interesting concept in AWS Step Functions for input and output
> processing: https://states-language.net/spec.html#filters
> namely that given some raw in, you can specify an `input` expression for
> filtering the raw input before sending it to an endpoint; then a `result`
> path expression where the result can be stored in the raw input; then the
> `output` expression which is used to filter the resulting raw input & output
> for the next step.
> i.e. its a simple way to compose inputs and outputs into a single message
> using a path expression language (in this case JsonPath).
> It might be nice to add the same kind of mechanism to the DSL. e.g. right now
> we take the output and pass it to the next step in the route. However it
> might be nice if folks could specify where the output goes in the initial raw
> input; for example to compose the results from a number of endpoints into a
> single message.
> One issue with the current camel Expression API is there's no concept of
> storing a result at a `reference path`.
> e.g. if the raw input was
> {code:javascript}
> {
> "title": "Numbers to add",
> "numbers": { "val1": 3, "val2": 4 }
> }
> {code}
> and we used
> {code:javascript}
> "InputPath": "$.numbers",
> "ResultPath": "$.sum"
> {code}
> to then invoke an endpoint that sums the numbers, we'd get the result output:
> {code:javascript}
> {
> "title": "Numbers to add",
> "numbers": { "val1": 3, "val2": 4 },
> "sum": 7
> }
> {code}
> so it may only be a subset of Languages we can support this 'resultPath`
> behaviour. At least JsonPath supports this at the implementation. So in
> speudo code its something like {code}jsonpath.set(rawInput,
> endpointOutput){code}
> So we'd need to add a new interface that an Expression may support;
> UpdateExpression or something like that, along these lines:
> {code:java}
> /** takes the value and updates it inside the input exchange payload */
> public interface UpdateExpression extends Expression {
>public Object update(Exchange rawInput, Object value, Class clazz);
> }
> {code}
> Which for now we'd only implement with JsonPath but could support other
> languages over time (e.g. XPath should be fine too)
> In terms of a DSL we may want to have a `ToDefinition` like step which has a
> language and optional input, result, output expressions. Maybe something
> like...
> {code:java}
> from("foo").invoke().jsonPath().input("$").result("$").output("$").to("whatnot")
> {code}
> I'm not totally sure about the 'invoke' name here but figured we'd need
> something different from 'to' to differentiate it in the Java DSL? Then
> `invoke().jsonPath()` would return an InvokeExpression. Then for the
> 'InvokeDefinition' we'd need to specify a language along with optional
> expressions (input, output, result) then the "to" would be the last
> expression so that the DSL returns back to the usual DSL again.
> We may want to use the idea of default expressions; so that if nothing is
> provided then for jsonPath we assume $ so that if you wish to not send any
> input or output you use an explicit null for those expressions.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-10654) Camel catalog - Add grammar for simple language
[ https://issues.apache.org/jira/browse/CAMEL-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-10654. - Resolution: Won't Fix > Camel catalog - Add grammar for simple language > --- > > Key: CAMEL-10654 > URL: https://issues.apache.org/jira/browse/CAMEL-10654 > Project: Camel > Issue Type: Improvement > Components: camel-core, tooling >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > It would be good if we could provide in the catalog, the grammar for the > simple language so tooling can get hold of that, and understand which > functions et all the simple language provides -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-7543) camel-sql - Allow to specify the column type in the SQL query
[ https://issues.apache.org/jira/browse/CAMEL-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897236#comment-16897236 ] Claus Ibsen commented on CAMEL-7543: I think it should work with bodyAs(BigInteger)[0] > camel-sql - Allow to specify the column type in the SQL query > - > > Key: CAMEL-7543 > URL: https://issues.apache.org/jira/browse/CAMEL-7543 > Project: Camel > Issue Type: Improvement > Components: camel-sql >Affects Versions: 2.13.2 >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > See nabble > http://camel.465427.n5.nabble.com/Problem-with-inserting-database-from-camel-context-xml-tp5752810.html -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-7543) camel-sql - Allow to specify the column type in the SQL query
[ https://issues.apache.org/jira/browse/CAMEL-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7543. Resolution: Fixed > camel-sql - Allow to specify the column type in the SQL query > - > > Key: CAMEL-7543 > URL: https://issues.apache.org/jira/browse/CAMEL-7543 > Project: Camel > Issue Type: Improvement > Components: camel-sql >Affects Versions: 2.13.2 >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > See nabble > http://camel.465427.n5.nabble.com/Problem-with-inserting-database-from-camel-context-xml-tp5752810.html -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-7543) camel-sql - Allow to specify the column type in the SQL query
[ https://issues.apache.org/jira/browse/CAMEL-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897229#comment-16897229 ] Claus Ibsen commented on CAMEL-7543: There is a bodyAs you can use, but it gets more complex if you access it from a list/array etc. Lets not make the simple language too complex for this use-case. > camel-sql - Allow to specify the column type in the SQL query > - > > Key: CAMEL-7543 > URL: https://issues.apache.org/jira/browse/CAMEL-7543 > Project: Camel > Issue Type: Improvement > Components: camel-sql >Affects Versions: 2.13.2 >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > See nabble > http://camel.465427.n5.nabble.com/Problem-with-inserting-database-from-camel-context-xml-tp5752810.html -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-9025) Programatically view properties loaded via properties file
[ https://issues.apache.org/jira/browse/CAMEL-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9025. Resolution: Fixed Fix Version/s: 3.0.0.M4 3.0.0 There is a loadProperties method now on properties component > Programatically view properties loaded via properties file > -- > > Key: CAMEL-9025 > URL: https://issues.apache.org/jira/browse/CAMEL-9025 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.15.2 > Environment: Any >Reporter: Shaishav Parekh >Priority: Minor > Labels: PropertiesComponent > Fix For: 3.0.0, 3.0.0.M4 > > > Currently there is no way to view properties loaded via a file on the > classpath if one is using the PropertiesComponent. It would be useful if one > can programatically access the properties loaded via the classpath for > reporting reasons. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-7684) camel-netty4 - Apply best practices to 4.x
[ https://issues.apache.org/jira/browse/CAMEL-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Istomin updated CAMEL-7684: - Component/s: camel-netty4-http camel-netty4 > camel-netty4 - Apply best practices to 4.x > --- > > Key: CAMEL-7684 > URL: https://issues.apache.org/jira/browse/CAMEL-7684 > Project: Camel > Issue Type: Improvement > Components: camel-netty4, camel-netty4-http >Affects Versions: 2.14.0 >Reporter: Claus Ibsen >Assignee: Denis Istomin >Priority: Major > Fix For: Future > > > This video from Norman > https://twitter.com/normanmaurer/status/498922171658682369 > Has some great practices how to utilize netty 4.x for better performance. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-13808) Intercept - Should only be configurable one time per route builder / camelcontext
[ https://issues.apache.org/jira/browse/CAMEL-13808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13808. - Resolution: Not A Problem Ah I forgot you can add a when predicate and therefore you can have multiple intercepts that react differently on the when > Intercept - Should only be configurable one time per route builder / > camelcontext > - > > Key: CAMEL-13808 > URL: https://issues.apache.org/jira/browse/CAMEL-13808 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > > The DSL make it possible to setup 2+ intercept, but it does not make sense as > you then intercept also the intercept. We should only allow to set 1 per > route builder / camel-context and 1 per route. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-13808) Intercept - Should only be configurable one time per route builder / camelcontext
[ https://issues.apache.org/jira/browse/CAMEL-13808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897151#comment-16897151 ] Claus Ibsen commented on CAMEL-13808: - You can have mutliple interceptFrom and sendTo as they can trigger on different endpoints. > Intercept - Should only be configurable one time per route builder / > camelcontext > - > > Key: CAMEL-13808 > URL: https://issues.apache.org/jira/browse/CAMEL-13808 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > > The DSL make it possible to setup 2+ intercept, but it does not make sense as > you then intercept also the intercept. We should only allow to set 1 per > route builder / camel-context and 1 per route. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (CAMEL-13808) Intercept - Should only be configurable one time per route builder / camelcontext
Claus Ibsen created CAMEL-13808: --- Summary: Intercept - Should only be configurable one time per route builder / camelcontext Key: CAMEL-13808 URL: https://issues.apache.org/jira/browse/CAMEL-13808 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Fix For: 3.0.0, 3.0.0.M5 The DSL make it possible to setup 2+ intercept, but it does not make sense as you then intercept also the intercept. We should only allow to set 1 per route builder / camel-context and 1 per route. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13795) TokenXMLExpressionIterator with inheritNamespaceToken creates duplicate default namespace definition
[
https://issues.apache.org/jira/browse/CAMEL-13795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13795:
Fix Version/s: 2.24.2
2.23.4
> TokenXMLExpressionIterator with inheritNamespaceToken creates duplicate
> default namespace definition
>
>
> Key: CAMEL-13795
> URL: https://issues.apache.org/jira/browse/CAMEL-13795
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.21.5, 2.23.3, 2.22.5, 2.24.1, 3.0.0.M4
>Reporter: Christian Pieczewski
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.M5
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> If a sub-item also contains the default namespace definition the splitter
> will duplicate it.
>
> {code:java|title=route definition}
> from("file:target/pair?initialDelay=0=10")
> // split the order child tags, and inherit namespaces
> from the orders root tag
> .split().tokenizeXML("order", "orders")
> .to("mock:split");
> {code}
>
>
> {code:xml|title=input}
>
> Camel in Action
> ActiveMQ in Action
> DSL in Action
> "
> {code}
> {code:xml|title=output[1]}
> Camel in
> Action
> {code}
> {code:xml|title=expected[1]}
> Camel in Action
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (CAMEL-13795) TokenXMLExpressionIterator with inheritNamespaceToken creates duplicate default namespace definition
[
https://issues.apache.org/jira/browse/CAMEL-13795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13795:
Fix Version/s: 3.0.0.M5
2.25.0
3.0.0
> TokenXMLExpressionIterator with inheritNamespaceToken creates duplicate
> default namespace definition
>
>
> Key: CAMEL-13795
> URL: https://issues.apache.org/jira/browse/CAMEL-13795
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.21.5, 2.23.3, 2.22.5, 2.24.1, 3.0.0.M4
>Reporter: Christian Pieczewski
>Priority: Minor
> Fix For: 3.0.0, 2.25.0, 3.0.0.M5
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> If a sub-item also contains the default namespace definition the splitter
> will duplicate it.
>
> {code:java|title=route definition}
> from("file:target/pair?initialDelay=0=10")
> // split the order child tags, and inherit namespaces
> from the orders root tag
> .split().tokenizeXML("order", "orders")
> .to("mock:split");
> {code}
>
>
> {code:xml|title=input}
>
> Camel in Action
> ActiveMQ in Action
> DSL in Action
> "
> {code}
> {code:xml|title=output[1]}
> Camel in
> Action
> {code}
> {code:xml|title=expected[1]}
> Camel in Action
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-13795) TokenXMLExpressionIterator with inheritNamespaceToken creates duplicate default namespace definition
[
https://issues.apache.org/jira/browse/CAMEL-13795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13795.
-
Resolution: Fixed
Assignee: Claus Ibsen
Thanks for reporting and the PR
> TokenXMLExpressionIterator with inheritNamespaceToken creates duplicate
> default namespace definition
>
>
> Key: CAMEL-13795
> URL: https://issues.apache.org/jira/browse/CAMEL-13795
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.21.5, 2.23.3, 2.22.5, 2.24.1, 3.0.0.M4
>Reporter: Christian Pieczewski
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 2.25.0, 3.0.0.M5
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> If a sub-item also contains the default namespace definition the splitter
> will duplicate it.
>
> {code:java|title=route definition}
> from("file:target/pair?initialDelay=0=10")
> // split the order child tags, and inherit namespaces
> from the orders root tag
> .split().tokenizeXML("order", "orders")
> .to("mock:split");
> {code}
>
>
> {code:xml|title=input}
>
> Camel in Action
> ActiveMQ in Action
> DSL in Action
> "
> {code}
> {code:xml|title=output[1]}
> Camel in
> Action
> {code}
> {code:xml|title=expected[1]}
> Camel in Action
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (CAMEL-13795) TokenXMLExpressionIterator with inheritNamespaceToken creates duplicate default namespace definition
[
https://issues.apache.org/jira/browse/CAMEL-13795?focusedWorklogId=285716=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-285716
]
ASF GitHub Bot logged work on CAMEL-13795:
--
Author: ASF GitHub Bot
Created on: 31/Jul/19 12:29
Start Date: 31/Jul/19 12:29
Worklog Time Spent: 10m
Work Description: davsclaus commented on pull request #3070: CAMEL-13795:
Fixing the issue of already declared namespaces within the child
URL: https://github.com/apache/camel/pull/3070
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: 285716)
Time Spent: 1h 40m (was: 1.5h)
> TokenXMLExpressionIterator with inheritNamespaceToken creates duplicate
> default namespace definition
>
>
> Key: CAMEL-13795
> URL: https://issues.apache.org/jira/browse/CAMEL-13795
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.21.5, 2.23.3, 2.22.5, 2.24.1, 3.0.0.M4
>Reporter: Christian Pieczewski
>Priority: Minor
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> If a sub-item also contains the default namespace definition the splitter
> will duplicate it.
>
> {code:java|title=route definition}
> from("file:target/pair?initialDelay=0=10")
> // split the order child tags, and inherit namespaces
> from the orders root tag
> .split().tokenizeXML("order", "orders")
> .to("mock:split");
> {code}
>
>
> {code:xml|title=input}
>
> Camel in Action
> ActiveMQ in Action
> DSL in Action
> "
> {code}
> {code:xml|title=output[1]}
> Camel in
> Action
> {code}
> {code:xml|title=expected[1]}
> Camel in Action
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (CAMEL-13795) TokenXMLExpressionIterator with inheritNamespaceToken creates duplicate default namespace definition
[
https://issues.apache.org/jira/browse/CAMEL-13795?focusedWorklogId=285715=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-285715
]
ASF GitHub Bot logged work on CAMEL-13795:
--
Author: ASF GitHub Bot
Created on: 31/Jul/19 12:28
Start Date: 31/Jul/19 12:28
Worklog Time Spent: 10m
Work Description: davsclaus commented on pull request #3071: CAMEL-13795:
Fixing the issue of already declared namespaces within the child
URL: https://github.com/apache/camel/pull/3071
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: 285715)
Time Spent: 1.5h (was: 1h 20m)
> TokenXMLExpressionIterator with inheritNamespaceToken creates duplicate
> default namespace definition
>
>
> Key: CAMEL-13795
> URL: https://issues.apache.org/jira/browse/CAMEL-13795
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.21.5, 2.23.3, 2.22.5, 2.24.1, 3.0.0.M4
>Reporter: Christian Pieczewski
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> If a sub-item also contains the default namespace definition the splitter
> will duplicate it.
>
> {code:java|title=route definition}
> from("file:target/pair?initialDelay=0=10")
> // split the order child tags, and inherit namespaces
> from the orders root tag
> .split().tokenizeXML("order", "orders")
> .to("mock:split");
> {code}
>
>
> {code:xml|title=input}
>
> Camel in Action
> ActiveMQ in Action
> DSL in Action
> "
> {code}
> {code:xml|title=output[1]}
> Camel in
> Action
> {code}
> {code:xml|title=expected[1]}
> Camel in Action
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-10126) Aggregate - Has name clash for some options
[ https://issues.apache.org/jira/browse/CAMEL-10126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-10126. - Resolution: Fixed > Aggregate - Has name clash for some options > --- > > Key: CAMEL-10126 > URL: https://issues.apache.org/jira/browse/CAMEL-10126 > Project: Camel > Issue Type: Improvement > Components: camel-core, eip >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > Attachments: Screen Shot 2016-07-06 at 9.50.34 AM.png > > > The aggregate EIP has two option you can set as both attributes and > expressions, and this causes a name clash. > See screenshot -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (CAMEL-7684) camel-netty4 - Apply best practices to 4.x
[ https://issues.apache.org/jira/browse/CAMEL-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Istomin reassigned CAMEL-7684: Assignee: Denis Istomin > camel-netty4 - Apply best practices to 4.x > --- > > Key: CAMEL-7684 > URL: https://issues.apache.org/jira/browse/CAMEL-7684 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.14.0 >Reporter: Claus Ibsen >Assignee: Denis Istomin >Priority: Major > Fix For: Future > > > This video from Norman > https://twitter.com/normanmaurer/status/498922171658682369 > Has some great practices how to utilize netty 4.x for better performance. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-13806) camel-ejb - Deprecate and remove
[ https://issues.apache.org/jira/browse/CAMEL-13806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13806. -- Resolution: Fixed > camel-ejb - Deprecate and remove > > > Key: CAMEL-13806 > URL: https://issues.apache.org/jira/browse/CAMEL-13806 > Project: Camel > Issue Type: Task > Components: camel-ejb >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > > See talk at > http://camel.465427.n5.nabble.com/DISCUSS-Camel-3-Deprecate-camel-ejb-tp5839933.html -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-10126) Aggregate - Has name clash for some options
[ https://issues.apache.org/jira/browse/CAMEL-10126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-10126: Fix Version/s: 3.0.0.M5 > Aggregate - Has name clash for some options > --- > > Key: CAMEL-10126 > URL: https://issues.apache.org/jira/browse/CAMEL-10126 > Project: Camel > Issue Type: Improvement > Components: camel-core, eip >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > Attachments: Screen Shot 2016-07-06 at 9.50.34 AM.png > > > The aggregate EIP has two option you can set as both attributes and > expressions, and this causes a name clash. > See screenshot -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-10126) Aggregate - Has name clash for some options
[ https://issues.apache.org/jira/browse/CAMEL-10126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896981#comment-16896981 ] Claus Ibsen commented on CAMEL-10126: - We need to get this done before 3.0 GA > Aggregate - Has name clash for some options > --- > > Key: CAMEL-10126 > URL: https://issues.apache.org/jira/browse/CAMEL-10126 > Project: Camel > Issue Type: Improvement > Components: camel-core, eip >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > Attachments: Screen Shot 2016-07-06 at 9.50.34 AM.png > > > The aggregate EIP has two option you can set as both attributes and > expressions, and this causes a name clash. > See screenshot -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (CAMEL-10126) Aggregate - Has name clash for some options
[ https://issues.apache.org/jira/browse/CAMEL-10126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-10126: --- Assignee: Claus Ibsen > Aggregate - Has name clash for some options > --- > > Key: CAMEL-10126 > URL: https://issues.apache.org/jira/browse/CAMEL-10126 > Project: Camel > Issue Type: Improvement > Components: camel-core, eip >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > Attachments: Screen Shot 2016-07-06 at 9.50.34 AM.png > > > The aggregate EIP has two option you can set as both attributes and > expressions, and this causes a name clash. > See screenshot -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-10126) Aggregate - Has name clash for some options
[ https://issues.apache.org/jira/browse/CAMEL-10126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-10126: Fix Version/s: (was: Future) > Aggregate - Has name clash for some options > --- > > Key: CAMEL-10126 > URL: https://issues.apache.org/jira/browse/CAMEL-10126 > Project: Camel > Issue Type: Improvement > Components: camel-core, eip >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > Attachments: Screen Shot 2016-07-06 at 9.50.34 AM.png > > > The aggregate EIP has two option you can set as both attributes and > expressions, and this causes a name clash. > See screenshot -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-9814) Support a parent configuration for routes to inherit properties for the CamelContext
[ https://issues.apache.org/jira/browse/CAMEL-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-9814: --- Component/s: (was: camel-osgi) > Support a parent configuration for routes to inherit properties for the > CamelContext > > > Key: CAMEL-9814 > URL: https://issues.apache.org/jira/browse/CAMEL-9814 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Matt Pavlovich >Priority: Major > Fix For: 3.0.0 > > > It would be really handy to have a top-level configuration that Contexts and > Routes can inherit a set of default values. > This would allow developers to reduce the complexity and verboseness of > routes as well as allow administrators to set defaults for an environment. > Types of settings: > Tracing: on/off > Jmx Enabled, mbean port, URL, etc > DefaultShutdownStrategy timeout > etc. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-9814) Support a parent configuration for routes to inherit properties for the CamelContext
[ https://issues.apache.org/jira/browse/CAMEL-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-9814: --- Fix Version/s: (was: 3.0.0) Future > Support a parent configuration for routes to inherit properties for the > CamelContext > > > Key: CAMEL-9814 > URL: https://issues.apache.org/jira/browse/CAMEL-9814 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Matt Pavlovich >Priority: Major > Fix For: Future > > > It would be really handy to have a top-level configuration that Contexts and > Routes can inherit a set of default values. > This would allow developers to reduce the complexity and verboseness of > routes as well as allow administrators to set defaults for an environment. > Types of settings: > Tracing: on/off > Jmx Enabled, mbean port, URL, etc > DefaultShutdownStrategy timeout > etc. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-9754) Convert from maven-bundle-plugin to bnd-maven-plugin
[ https://issues.apache.org/jira/browse/CAMEL-9754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9754. Resolution: Won't Fix > Convert from maven-bundle-plugin to bnd-maven-plugin > > > Key: CAMEL-9754 > URL: https://issues.apache.org/jira/browse/CAMEL-9754 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Quinn Stevenson >Priority: Minor > > Currently, the v2.3.7 of the maven-bundle-plugin is used to generate the OSGi > Manifests for the Camel libraries. The project cannot upgrade to a later > version of the maven-bundle-plugin because the newer versions break the build. > The bnd-maven-plugin is maintained by the same group that maintains the BND > libraries (which both plugins use internally) expedites updates to the plugin > when the underlying libraries change. Also, the bnd-maven-plugin uses the > same BND configuration file format as BND, which eliminates the complex > mapping from XML to BND configuration that the maven-bundle-plugin has to > deal with. > The goals are: > - change from the maven-bundle-plugin to the bnd-maven-plugin > - upgrade the OSGi version > - upgrade the default OSGi dependencies in the parent POM -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-9562) OSGi classloader problem
[
https://issues.apache.org/jira/browse/CAMEL-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9562.
Resolution: Abandoned
> OSGi classloader problem
>
>
> Key: CAMEL-9562
> URL: https://issues.apache.org/jira/browse/CAMEL-9562
> Project: Camel
> Issue Type: Improvement
> Components: camel-osgi
>Affects Versions: 2.16.2
>Reporter: Brad Johnson
>Priority: Minor
>
> At least: OSGiClassResolver and OSGiPackageScanner but probably others. A
> strict mode flag should be added to enforce using the OSGi classloader. By
> default it could be false to be backwardly compatible but when it set to true
> then the secondary attempt at using the application context classloader would
> be circumvented. This should really be the default behavior in an OSGi
> environment but because of backward compatibility issues that might not be
> possible.
> This fix should be relatively easy and unnoticeable by most. But for those
> working OSGi environments we usually want the strict mode in order to be in
> compliance with OSGi. Without it the current design reflects a classloader
> leak that shouldn't be allowed. If a class can't be found then it isn't
> being exported correctly or a bundle is hiding a class it shouldn't or Camel
> blueprint isn't being set up correctly or But in all cases it should
> fail.
> The OSGi classloader mechanics includes a fall back mechanism that uses the
> global classloader to find classes if it can't find them in OSGi registry it
> cheats with SU.
> OSGiClassResolver:
> if (clazz == null && camelContext != null) {
> // fallback and load class using the application context
> classloader
> clazz = super.loadClass(name,
> camelContext.getApplicationContextClassLoader());
> if (LOG.isTraceEnabled()) {
> LOG.trace("Loading class {} using CamelContext {} -> {}", new
> Object[]{name, camelContext, clazz});
> }
> }
> OSGiPackageScanClassResolver.
> // if we did not find any new, then fallback to use regular non bundle class
> loading
> if (classes.size() == classesSize) {
> // Using the non-OSGi classloaders as a fallback
> // this is necessary when use JBI packaging for servicemix-camel
> SU
> // so that we get chance to use SU classloader to scan packages
> in the SU
> log.trace("Cannot find any classes in bundles, not trying regular
> classloaders scanning: {}", packageName);
> for (ClassLoader classLoader : super.getClassLoaders()) {
> if (!isOsgiClassloader(classLoader)) {
> find(test, packageName, classLoader, classes);
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-9570) Blueprint Proxies are not used when injected into Java RouteBuilders
[ https://issues.apache.org/jira/browse/CAMEL-9570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9570. Resolution: Won't Fix > Blueprint Proxies are not used when injected into Java RouteBuilders > > > Key: CAMEL-9570 > URL: https://issues.apache.org/jira/browse/CAMEL-9570 > Project: Camel > Issue Type: Bug > Components: camel-blueprint, camel-core >Affects Versions: 2.16.2 >Reporter: Quinn Stevenson >Priority: Minor > > Basic Conditions: > - Java interface used for OSGi Services > - Implementation of the Java interface registered as a OSGi service. Note > that the package containing implementation is NOT exported > - A Java RouteBuilder that uses the Java interface via bean(...) DSL calls, > with a setter for the bean implementing the interface > - Wire everything together with Blueprint - create a for the > service, a for the RouteBuilder and inject the service reference, > and use the RouteBuilder in a CamelContext. > After all this is deployed, stop the bundle implementing the service. A > ServiceUnavailableException should be thrown after a timeout, but the object > that was injected into the RouteBuilder process the request - so the > Blueprint Proxy is not used. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-9477) Camel test examples are not working
[ https://issues.apache.org/jira/browse/CAMEL-9477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9477. Resolution: Cannot Reproduce > Camel test examples are not working > --- > > Key: CAMEL-9477 > URL: https://issues.apache.org/jira/browse/CAMEL-9477 > Project: Camel > Issue Type: Task > Components: documentation >Affects Versions: 2.16.1 >Reporter: Serge Smertin >Priority: Minor > Fix For: Future > > > While preparing internal demo of Camel i've tried to go over examples on test > page and most of them are not actually working - > http://camel.apache.org/spring-testing.html. I've seen [~davsclaus] writing > about > http://www.davsclaus.com/2015/12/my-thoughts-on-buying-professional.html, so > i find this issue as important. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-9370) Support for async/deferred content
[
https://issues.apache.org/jira/browse/CAMEL-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9370.
Resolution: Abandoned
> Support for async/deferred content
> --
>
> Key: CAMEL-9370
> URL: https://issues.apache.org/jira/browse/CAMEL-9370
> Project: Camel
> Issue Type: Improvement
> Components: camel-jetty
>Affects Versions: 2.16.1
>Reporter: Tuomas Kiviaho
>Priority: Major
>
> I'm receiving {{text/event-stream}} and to my surprise there was no support
> of anykind for {{AsyncContentProvider}}.
> Hence here are my dealings with the issue in a form of a patch. Some of the
> bits would work out of the box as-is, but others (such as {{jettyBinding
> instanceof Response.ResponseListener}}). I've rammed in just to get it
> working. It would be nice if this type of streaming could be enabled without
> having to declare {{jettyBinding}}. A new option for instance would be more
> practical solution.
> {code:title=org/apache/camel/component/jetty/DefaultJettyHttpBinding.java}
> @@ -191,7 +191,8 @@
> }
> } else {
> // just grab the raw content body
> -return httpExchange.getBody();
> +byte[] body = httpExchange.getBody();
> +return body == null ? httpExchange.getResponseContentProvider()
> : body;
> }
> }
>
> {code}
> {code:title=org/apache/camel/component/jetty/JettyContentExchange.java}
> @@ -25,6 +25,7 @@
> import org.apache.camel.AsyncCallback;
> import org.apache.camel.Exchange;
> import org.eclipse.jetty.client.HttpClient;
> +import org.eclipse.jetty.client.api.ContentProvider;
>
> public interface JettyContentExchange {
>
> @@ -44,6 +45,8 @@
> void setRequestContent(String data, String charset) throws
> UnsupportedEncodingException;
>
> void setRequestContent(InputStream ins);
> +
> +void setRequestContent(ContentProvider contentProvider);
>
> void addRequestHeader(String key, String s);
>
> @@ -63,6 +66,8 @@
> int getResponseStatus();
>
> byte[] getResponseContentBytes();
> +
> +ContentProvider getResponseContentProvider();
>
> Map> getResponseHeaders();
>
> {code}
> {code:title=org/apache/camel/component/jetty/JettyHttpProducer.java}
> @@ -32,7 +32,6 @@
> import org.apache.camel.Message;
> import org.apache.camel.http.common.HttpConstants;
> import org.apache.camel.http.common.HttpHelper;
> -import org.apache.camel.http.common.HttpMethods;
> import org.apache.camel.impl.DefaultAsyncProducer;
> import org.apache.camel.spi.HeaderFilterStrategy;
> import org.apache.camel.util.ExchangeHelper;
> @@ -40,6 +39,7 @@
> import org.apache.camel.util.ObjectHelper;
> import org.apache.camel.util.URISupport;
> import org.eclipse.jetty.client.HttpClient;
> +import org.eclipse.jetty.client.api.ContentProvider;
> import org.eclipse.jetty.util.component.LifeCycle;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> @@ -160,6 +160,9 @@
> // (for example application/x-www-form-urlencoded forms
> being sent)
> String charset = IOHelper.getCharsetName(exchange,
> false);
> httpExchange.setRequestContent(data, charset);
> +} else if (body instanceof ContentProvider) {
> +ContentProvider contentProvider = (ContentProvider) body;
> +httpExchange.setRequestContent(contentProvider);
> } else {
> // then fallback to input stream
> InputStream is =
> exchange.getContext().getTypeConverter().mandatoryConvertTo(InputStream.class,
> exchange, exchange.getIn().getBody());
> {code}
> {code:title=org/apache/camel/component/jetty9/JettyContentExchange9.java}
> @@ -21,6 +21,7 @@
> import java.io.InputStream;
> import java.io.UnsupportedEncodingException;
> import java.net.MalformedURLException;
> +import java.nio.ByteBuffer;
> import java.util.Collection;
> import java.util.Map;
> import java.util.TreeMap;
> @@ -35,14 +36,18 @@
> import org.apache.camel.component.jetty.JettyContentExchange;
> import org.apache.camel.component.jetty.JettyHttpBinding;
> import org.eclipse.jetty.client.HttpClient;
> +import org.eclipse.jetty.client.Synchronizable;
> +import org.eclipse.jetty.client.api.ContentProvider;
> import org.eclipse.jetty.client.api.Request;
> import org.eclipse.jetty.client.api.Response;
> import org.eclipse.jetty.client.api.Result;
> import org.eclipse.jetty.client.util.BufferingResponseListener;
> import org.eclipse.jetty.client.util.BytesContentProvider;
> +import org.eclipse.jetty.client.util.DeferredContentProvider;
> import org.eclipse.jetty.client.util.InputStreamContentProvider;
> import
[jira] [Resolved] (CAMEL-9322) Add getDataFormat(name) to CamelContext
[ https://issues.apache.org/jira/browse/CAMEL-9322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9322. Resolution: Won't Fix > Add getDataFormat(name) to CamelContext > --- > > Key: CAMEL-9322 > URL: https://issues.apache.org/jira/browse/CAMEL-9322 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > So we have it like for getComponent(name) getEndpoint(uri) so you can lookup > an existing data format to reuse, or create a default dataformat based on the > name. > Today there is a resolveDataFormat that creates a new instance if none has > explicit added to the registry beforehand. But an end user may want to share > a dataformat in a CamelContext like you can do with component / endpoints. > See CAMEL-9320 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (CAMEL-9268) camel-okhttp - Using the popular okhttp client
[ https://issues.apache.org/jira/browse/CAMEL-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-9268: -- Assignee: (was: Tomohisa Igarashi) > camel-okhttp - Using the popular okhttp client > -- > > Key: CAMEL-9268 > URL: https://issues.apache.org/jira/browse/CAMEL-9268 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > A camel-okhttp component that uses the okhttp client > http://square.github.io/okhttp/ > http://square.github.io/okhttp/ -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-9253) Adding spi ManagementNamingStrategyAware
[ https://issues.apache.org/jira/browse/CAMEL-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9253. Resolution: Won't Fix > Adding spi ManagementNamingStrategyAware > > > Key: CAMEL-9253 > URL: https://issues.apache.org/jira/browse/CAMEL-9253 > Project: Camel > Issue Type: New Feature > Components: camel-core >Affects Versions: 2.16.0 >Reporter: Howard Nguyen >Priority: Major > > Non-singleton instance ObjectName has identity hash in the name. Make it > difficult for monitoring infrastructure or documentation to identify which > JMX interface to monitor / operate. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-9147) camel-swagger2markup - To generate api in other report like formats
[ https://issues.apache.org/jira/browse/CAMEL-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9147. Resolution: Won't Fix That project is now dead > camel-swagger2markup - To generate api in other report like formats > --- > > Key: CAMEL-9147 > URL: https://issues.apache.org/jira/browse/CAMEL-9147 > Project: Camel > Issue Type: Improvement > Components: camel-swagger >Reporter: Claus Ibsen >Priority: Major > > This project > https://swagger2markup.readme.io/ > Could be nice to have it integrated with camel-swagger-java so you can report > the api in markup format -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-8878) Problem is occurring in 2.15.2
[ https://issues.apache.org/jira/browse/CAMEL-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8878. Resolution: Abandoned Closing old ticket > Problem is occurring in 2.15.2 > -- > > Key: CAMEL-8878 > URL: https://issues.apache.org/jira/browse/CAMEL-8878 > Project: Camel > Issue Type: Sub-task > Components: camel-rabbitmq >Affects Versions: 2.15.2 >Reporter: Hieu Nguyen >Priority: Minor > > I'm camel-rabbitmq component as as rabbitmq consumer. The consumer is > consuming message from a default exchange "" with a routing key. When I > started up the app, I got the exception "Caused by: > java.lang.IllegalArgumentException: No URI path as the exchangeName for the > RabbitMQEndpoint". > The camel version I'm using is 2.15.2. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-9000) More friendly names for consumer and producer mbean names
[ https://issues.apache.org/jira/browse/CAMEL-9000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9000. Resolution: Won't Fix > More friendly names for consumer and producer mbean names > - > > Key: CAMEL-9000 > URL: https://issues.apache.org/jira/browse/CAMEL-9000 > Project: Camel > Issue Type: Improvement > Components: camel-core, jmx >Reporter: Claus Ibsen >Priority: Major > Fix For: Future, 3.0.0 > > > They use identity hashcode as part of mbean name to make sure they are > unique. But if they are part of routes, we can use the route id, node id, as > they are unique, and its more understandable by end users. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-8599) Support a dependsOn="" route attribute.
[
https://issues.apache.org/jira/browse/CAMEL-8599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8599.
Resolution: Won't Fix
> Support a dependsOn="" route attribute.
> -
>
> Key: CAMEL-8599
> URL: https://issues.apache.org/jira/browse/CAMEL-8599
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Affects Versions: 2.15.1
>Reporter: Aaron Whiteside
>Priority: Minor
>
> Support a dependsOn="" route attribute
> Much like spring's depends-on bean attribute.
> Calculate the start order based on the dependsOn graphs. Using startupOrder
> in a dynamic route environment is hard because the startupOrder must be
> unique across all routes.
> {code:xml}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-8610) Add support for dynamic XML route templates
[
https://issues.apache.org/jira/browse/CAMEL-8610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8610.
Resolution: Won't Fix
> Add support for dynamic XML route templates
> ---
>
> Key: CAMEL-8610
> URL: https://issues.apache.org/jira/browse/CAMEL-8610
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Affects Versions: 2.15.1
>Reporter: Aaron Whiteside
>Priority: Major
> Fix For: Future
>
>
> Add support for dynamic route templates
> {code:xml}
>
>
>
>
> {code}
> {code:java}
> CamelContext.startRouteFromTemplate(String templateRouteId, String
> newRouteId, Map templateProperties);
> {code}
> Usage would be something like:
> {code:java}
> Map map = new HashMap<>();
> map.put("myendpoint", "direct:hello");
> map.put("seda.name", "test");
> camelContext.startRouteFromTemplate("my-template", "my-new-route-1", map);
> // or
> camelContext.startRouteFromTemplate("my-template", null, null); // auto
> assign new route id and supply no specific properties.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-8529) ScriptEngine usage optimizations
[ https://issues.apache.org/jira/browse/CAMEL-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8529. Resolution: Won't Fix camel-script is deprecated and removed in camel 3 > ScriptEngine usage optimizations > > > Key: CAMEL-8529 > URL: https://issues.apache.org/jira/browse/CAMEL-8529 > Project: Camel > Issue Type: Improvement > Components: camel-script >Affects Versions: 2.15.0 >Reporter: gui >Priority: Minor > Attachments: scriptbuilder.patch > > > When a script is compiled (eg in case of js), the scriptbuilder is (re) > creating a new engine instance on every invocation, although the compiled > script has already an engine attached. > This cause a lot of unnecessary engine initialization on every invocation. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-8388) camel-jpa - Do not store CamelEntityManager as a header
[
https://issues.apache.org/jira/browse/CAMEL-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8388.
Resolution: Won't Fix
Okay so there is an option on the endpoint you can turn on|off for this
> camel-jpa - Do not store CamelEntityManager as a header
> ---
>
> Key: CAMEL-8388
> URL: https://issues.apache.org/jira/browse/CAMEL-8388
> Project: Camel
> Issue Type: Improvement
> Components: camel-jpa
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
>
> We should try to avoid storing headers with are transient such as
> JpaEntityManager and other kinds. But instead allow access to them using a
> JpaMessage type that has a getter method to it,
> Then ppl can access it using
> {code}
> EntityManager em = exchange.getIn(JpaMessage.class).getEntityManager();
> {code}
> See SO for a problem when using as a header
> http://stackoverflow.com/questions/28608301/apache-camel-aggregate-persistence-and-hibernate
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (CAMEL-13807) Component DSL - To configure components like endpoint DSL
Claus Ibsen created CAMEL-13807: --- Summary: Component DSL - To configure components like endpoint DSL Key: CAMEL-13807 URL: https://issues.apache.org/jira/browse/CAMEL-13807 Project: Camel Issue Type: New Feature Reporter: Claus Ibsen Fix For: 3.x Some components can also be configured, and today you can configure them via - spring boot auto configuration - camel main configuration - java code manually via setter/getter - xml syntax via We should look at generating a Java component DSL with fluent builder like camel-endpointdsl. Then its similar and you can configure them component().jms().concurrentConsumers(5).keepAlive(6000) And then later if/when we do a XML version of endpoint DSL we can do one for components too. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
