[jira] [Resolved] (CAMEL-14500) camel-core - spi-annotations is not optional
[ https://issues.apache.org/jira/browse/CAMEL-14500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14500. - Assignee: Claus Ibsen Resolution: Fixed > camel-core - spi-annotations is not optional > > > Key: CAMEL-14500 > URL: https://issues.apache.org/jira/browse/CAMEL-14500 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > They are no longer optional for running camel. As we look for @Component to > grab scheme name. > Caused by: java.lang.NoClassDefFoundError: > org/apache/camel/spi/annotations/Component > at org.apache.camel.support.DefaultComponent.doInit > (DefaultComponent.java:406) > at org.apache.camel.support.service.ServiceSupport.init > (ServiceSupport.java:82) > at org.apache.camel.support.service.ServiceHelper.initService > (ServiceHelper.java:55) > at org.apache.camel.impl.engine.AbstractCamelContext.initComponent > (AbstractCamelContext.java:576) > at org.apache.camel.impl.engine.AbstractCamelContext.access$000 > (AbstractCamelContext.java:170) > at org.apache.camel.impl.engine.AbstractCamelContext$2.apply > (AbstractCamelContext.java:505) > at org.apache.camel.impl.engine.AbstractCamelContext$2.apply > (AbstractCamelContext.java:501) > at java.util.concurrent.ConcurrentHashMap.computeIfAbsent > (ConcurrentHashMap.java:1660) > at org.apache.camel.impl.engine.AbstractCamelContext.getComponent > (AbstractCamelContext.java:501) > at org.apache.camel.impl.engine.AbstractCamelContext.getComponent > (AbstractCamelContext.java:477) > at org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint > (AbstractCamelContext.java:748) > at org.apache.camel.support.CamelContextHelper.getMandatoryEndpoint > (CamelContextHelper.java:57) > at org.apache.camel.impl.engine.DefaultRouteContext.resolveEndpoint > (DefaultRouteContext.java:120) > at org.apache.camel.reifier.RouteReifier.doCreateRoute > (RouteReifier.java:364) > at org.apache.camel.reifier.RouteReifier.createRoute > (RouteReifier.java:107) > at org.apache.camel.impl.DefaultModel.start (DefaultModel.java:356) > at org.apache.camel.impl.DefaultModel.startRoute (DefaultModel.java:330) > at org.apache.camel.impl.DefaultModel.startRouteDefinitions > (DefaultModel.java:323) > at org.apache.camel.impl.DefaultModel.startRouteDefinitions > (DefaultModel.java:302) > at org.apache.camel.impl.AbstractModelCamelContext.startRouteDefinitions > (AbstractModelCamelContext.java:317) > at org.apache.camel.impl.engine.AbstractCamelContext.doStartCamel > (AbstractCamelContext.java:2590) > at org.apache.camel.impl.engine.AbstractCamelContext.lambda$doStart$2 > (AbstractCamelContext.java:2442) > at > org.apache.camel.impl.engine.AbstractCamelContext.doWithDefinedClassLoader > (AbstractCamelContext.java:2459) > at org.apache.camel.impl.engine.AbstractCamelContext.doStart > (AbstractCamelContext.java:2440) > at org.apache.camel.support.service.ServiceSupport.start > (ServiceSupport.java:120) > at org.apache.camel.impl.engine.AbstractCamelContext.start > (AbstractCamelContext.java:2349) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14505) Remove meta-annotations
Claus Ibsen created CAMEL-14505: --- Summary: Remove meta-annotations Key: CAMEL-14505 URL: https://issues.apache.org/jira/browse/CAMEL-14505 Project: Camel Issue Type: Task Components: camel-core Reporter: Claus Ibsen Fix For: 3.1.0 Lets avoid a single JAR with @Experimental annotation. We can find a place to this in camel-api instead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14504) camel-apt - No longer used replaced by camel-package-maven-plugin
Claus Ibsen created CAMEL-14504: --- Summary: camel-apt - No longer used replaced by camel-package-maven-plugin Key: CAMEL-14504 URL: https://issues.apache.org/jira/browse/CAMEL-14504 Project: Camel Issue Type: Task Components: documentation Reporter: Claus Ibsen Fix For: 3.1.0 We need to update the 3.x upgrade guide, and also the other parts in the docs where we mention camel-apt. Now you can just use the camel-maven-package-plugin that has a single goal that generates all needed stuff. Also our maven archetypes must be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14481) camel-spring-boot: Remove camel-management to disable JMX by default
[ https://issues.apache.org/jira/browse/CAMEL-14481?focusedWorklogId=382753=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-382753 ] ASF GitHub Bot logged work on CAMEL-14481: -- Author: ASF GitHub Bot Created on: 06/Feb/20 06:50 Start Date: 06/Feb/20 06:50 Worklog Time Spent: 10m Work Description: davsclaus commented on pull request #3549: CAMEL-14481: camel-spring-boot: Remove camel-management to disable JM… URL: https://github.com/apache/camel/pull/3549 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: 382753) Time Spent: 40m (was: 0.5h) > camel-spring-boot: Remove camel-management to disable JMX by default > > > Key: CAMEL-14481 > URL: https://issues.apache.org/jira/browse/CAMEL-14481 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Pascal Schumacher >Assignee: Pascal Schumacher >Priority: Major > Fix For: 3.1.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Spring Boot 2.2 disables JMX by default (see: > https://github.com/spring-projects/spring-boot/issues/16090, > https://github.com/spring-projects/spring-boot/issues/16498). > We should follow suit and remove the camel-management compile dependency from > camel-spring-boot to disable JMX by default. > See discussion on the mailing list: > http://mail-archives.apache.org/mod_mbox/camel-dev/202002.mbox/%3Caa3aef09-5ff9-d60b-7ef4-2c4c9c30153f%40gmx.net%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14459) camel-webhook - RAW() parameter value handling in delegated URI
[
https://issues.apache.org/jira/browse/CAMEL-14459?focusedWorklogId=382752=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-382752
]
ASF GitHub Bot logged work on CAMEL-14459:
--
Author: ASF GitHub Bot
Created on: 06/Feb/20 06:44
Start Date: 06/Feb/20 06:44
Worklog Time Spent: 10m
Work Description: tadayosi commented on pull request #3550: CAMEL-14459 -
camel-webhook - RAW() parameter value handling in delegated URI
URL: https://github.com/apache/camel/pull/3550
https://issues.apache.org/jira/browse/CAMEL-14459
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: 382752)
Remaining Estimate: 0h
Time Spent: 10m
> camel-webhook - RAW() parameter value handling in delegated URI
> ---
>
> Key: CAMEL-14459
> URL: https://issues.apache.org/jira/browse/CAMEL-14459
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Tadayoshi Sato
>Assignee: Tadayoshi Sato
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It's possible that camel-webhook has the same issue as CAMEL-14456 with
> camel-master on handling {{RAW()}} parameter in the delegated URI. Let's
> check if it really has the issue or not.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14503) camel-package-maven-plugin:generate fails with NPE for component outside the camel source tree
[ https://issues.apache.org/jira/browse/CAMEL-14503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031030#comment-17031030 ] Luca Burgazzoli commented on CAMEL-14503: - /cc [~gnodet] > camel-package-maven-plugin:generate fails with NPE for component outside the > camel source tree > -- > > Key: CAMEL-14503 > URL: https://issues.apache.org/jira/browse/CAMEL-14503 > Project: Camel > Issue Type: Bug > Components: tooling >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.1.0 > > > The mojo camel-package-maven-plugin:generate assumes that components are all > belonging to the camel source tree so when it is applied to external > components, it fails with NPE here: > https://github.com/apache/camel/blob/master/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/EndpointSchemaGeneratorMojo.java#L1230-L1231 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14503) camel-package-maven-plugin:generate fails with NPE for component outside the camel source tree
[ https://issues.apache.org/jira/browse/CAMEL-14503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated CAMEL-14503: Fix Version/s: 3.1.0 > camel-package-maven-plugin:generate fails with NPE for component outside the > camel source tree > -- > > Key: CAMEL-14503 > URL: https://issues.apache.org/jira/browse/CAMEL-14503 > Project: Camel > Issue Type: Bug > Components: tooling >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.1.0 > > > The mojo camel-package-maven-plugin:generate assumes that components are all > belonging to the camel source tree so when it is applied to external > components, it fails with NPE here: > https://github.com/apache/camel/blob/master/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/EndpointSchemaGeneratorMojo.java#L1230-L1231 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14503) camel-package-maven-plugin:generate fails with NPE for component outside the camel source tree
Luca Burgazzoli created CAMEL-14503: --- Summary: camel-package-maven-plugin:generate fails with NPE for component outside the camel source tree Key: CAMEL-14503 URL: https://issues.apache.org/jira/browse/CAMEL-14503 Project: Camel Issue Type: Bug Components: tooling Reporter: Luca Burgazzoli The mojo camel-package-maven-plugin:generate assumes that components are all belonging to the camel source tree so when it is applied to external components, it fails with NPE here: https://github.com/apache/camel/blob/master/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/EndpointSchemaGeneratorMojo.java#L1230-L1231 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14481) camel-spring-boot: Remove camel-management to disable JMX by default
[ https://issues.apache.org/jira/browse/CAMEL-14481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Schumacher resolved CAMEL-14481. --- Resolution: Fixed > camel-spring-boot: Remove camel-management to disable JMX by default > > > Key: CAMEL-14481 > URL: https://issues.apache.org/jira/browse/CAMEL-14481 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Pascal Schumacher >Assignee: Pascal Schumacher >Priority: Major > Fix For: 3.1.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Spring Boot 2.2 disables JMX by default (see: > https://github.com/spring-projects/spring-boot/issues/16090, > https://github.com/spring-projects/spring-boot/issues/16498). > We should follow suit and remove the camel-management compile dependency from > camel-spring-boot to disable JMX by default. > See discussion on the mailing list: > http://mail-archives.apache.org/mod_mbox/camel-dev/202002.mbox/%3Caa3aef09-5ff9-d60b-7ef4-2c4c9c30153f%40gmx.net%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14481) camel-spring-boot: Remove camel-management to disable JMX by default
[ https://issues.apache.org/jira/browse/CAMEL-14481?focusedWorklogId=382442=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-382442 ] ASF GitHub Bot logged work on CAMEL-14481: -- Author: ASF GitHub Bot Created on: 05/Feb/20 18:54 Start Date: 05/Feb/20 18:54 Worklog Time Spent: 10m Work Description: asfgit commented on pull request #4: CAMEL-14481: camel-spring-boot: Remove camel-management to disable JM… URL: https://github.com/apache/camel-spring-boot/pull/4 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: 382442) Time Spent: 0.5h (was: 20m) > camel-spring-boot: Remove camel-management to disable JMX by default > > > Key: CAMEL-14481 > URL: https://issues.apache.org/jira/browse/CAMEL-14481 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Pascal Schumacher >Assignee: Pascal Schumacher >Priority: Major > Fix For: 3.1.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Spring Boot 2.2 disables JMX by default (see: > https://github.com/spring-projects/spring-boot/issues/16090, > https://github.com/spring-projects/spring-boot/issues/16498). > We should follow suit and remove the camel-management compile dependency from > camel-spring-boot to disable JMX by default. > See discussion on the mailing list: > http://mail-archives.apache.org/mod_mbox/camel-dev/202002.mbox/%3Caa3aef09-5ff9-d60b-7ef4-2c4c9c30153f%40gmx.net%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14481) camel-spring-boot: Remove camel-management to disable JMX by default
[ https://issues.apache.org/jira/browse/CAMEL-14481?focusedWorklogId=382440=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-382440 ] ASF GitHub Bot logged work on CAMEL-14481: -- Author: ASF GitHub Bot Created on: 05/Feb/20 18:52 Start Date: 05/Feb/20 18:52 Worklog Time Spent: 10m Work Description: PascalSchumacher commented on pull request #3549: CAMEL-14481: camel-spring-boot: Remove camel-management to disable JM… URL: https://github.com/apache/camel/pull/3549 …X by default Add a note to the 3.1 upgrade guide. Not sure if this is the best way to phrase this. Suggestions welcome! 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: 382440) Time Spent: 20m (was: 10m) > camel-spring-boot: Remove camel-management to disable JMX by default > > > Key: CAMEL-14481 > URL: https://issues.apache.org/jira/browse/CAMEL-14481 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Pascal Schumacher >Assignee: Pascal Schumacher >Priority: Major > Fix For: 3.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Spring Boot 2.2 disables JMX by default (see: > https://github.com/spring-projects/spring-boot/issues/16090, > https://github.com/spring-projects/spring-boot/issues/16498). > We should follow suit and remove the camel-management compile dependency from > camel-spring-boot to disable JMX by default. > See discussion on the mailing list: > http://mail-archives.apache.org/mod_mbox/camel-dev/202002.mbox/%3Caa3aef09-5ff9-d60b-7ef4-2c4c9c30153f%40gmx.net%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14074) http - Allow restricted headers
[ https://issues.apache.org/jira/browse/CAMEL-14074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030858#comment-17030858 ] Claus Ibsen commented on CAMEL-14074: - Yeah you are welcome to send a PR then we can take a look > http - Allow restricted headers > --- > > Key: CAMEL-14074 > URL: https://issues.apache.org/jira/browse/CAMEL-14074 > Project: Camel > Issue Type: Improvement > Components: camel-http >Reporter: Djordje Bajic >Assignee: Omar Al-Safi >Priority: Major > Fix For: 3.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Hello! > It would be nice to have a feature to override any of restricted http > headers. I noticed that it's not available to set custom "Host" header. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14074) http - Allow restricted headers
[ https://issues.apache.org/jira/browse/CAMEL-14074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030848#comment-17030848 ] Djordje Bajic commented on CAMEL-14074: --- [~davsclaus] - This option is merged into master but didn't make it into 3.1.0 because I created it in 2.x.x HTTP component which is deprecated. Is it okay to checkout the branch from 3.1.0 and implement this option in it so it can be used with Camel 3? > http - Allow restricted headers > --- > > Key: CAMEL-14074 > URL: https://issues.apache.org/jira/browse/CAMEL-14074 > Project: Camel > Issue Type: Improvement > Components: camel-http >Reporter: Djordje Bajic >Assignee: Omar Al-Safi >Priority: Major > Fix For: 3.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Hello! > It would be nice to have a feature to override any of restricted http > headers. I noticed that it's not available to set custom "Host" header. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14502) JSR 356 Websocket component does not work properly on Spring Boot
James Netherton created CAMEL-14502: --- Summary: JSR 356 Websocket component does not work properly on Spring Boot Key: CAMEL-14502 URL: https://issues.apache.org/jira/browse/CAMEL-14502 Project: Camel Issue Type: Improvement Reporter: James Netherton Assignee: James Netherton The component uses a ServletContainerListener to perform some custom logic when the webapp is deployed / undeployed. Unfortunately ServletContainerListener is ignored when Spring Boot runs in an embedded web container and hence the required logic is never executed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14501) gain fully control of xml parser used by saxon
[
https://issues.apache.org/jira/browse/CAMEL-14501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Yue Fang updated CAMEL-14501:
-
Description:
currently we can configure TransformerFactory used by saxon by specifying
features/attributes there. However, this can only take effect on an XML parser
that Saxon creates. It has no effect if camel application creates the XML
parser (that is, if the input is supplied to Saxon as a Source object)
[Per saxon community discussion here|https://saxonica.plan.io/issues/2457] ,
{code}
If you want detailed control over parsing, the best way is to create an
XMLReader yourself and supply it to Saxon within a SAXSource object.
{code}
So we need to saxonReaderProperties option to camel-xslt-saxon endpoint, if
saxonReaderProperties isn't null, create a XMLReader and specify features on
it, so that we can gain fully control of xml parsed used by saxon. This is
important to prevent XXE attack when using saxon to do xslt transform. Like by
disabling uri=http://xml.org/sax/features/external-general-entities; to not
access sensitive local files.
was:
currently we can configure TransformerFactory used by saxon by specifying
features/attributes there. However, this can only take effect on an XML parser
that Saxon creates. It has no effect if camel application creates the XML
parser (that is, if the input is supplied to Saxon as a Source object)
Per saxon community discussion here ,
If you want detailed control over parsing, the best way is to create an
XMLReader yourself and supply it to Saxon within a SAXSource object.
So we need to saxonReaderProperties option to camel-xslt-saxon endpoint, if
saxonReaderProperties isn't null, create a XMLReader and specify features on
it, so that we can gain fully control of xml parsed used by saxon. This is
important to prevent XXE attack when using saxon to do xslt transform. Like by
disabling uri=http://xml.org/sax/features/external-general-entities; to not
access sensitive local files.
> gain fully control of xml parser used by saxon
> --
>
> Key: CAMEL-14501
> URL: https://issues.apache.org/jira/browse/CAMEL-14501
> Project: Camel
> Issue Type: Improvement
> Components: camel-xslt
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
>
> currently we can configure TransformerFactory used by saxon by specifying
> features/attributes there. However, this can only take effect on an XML
> parser that Saxon creates. It has no effect if camel application creates the
> XML parser (that is, if the input is supplied to Saxon as a Source object)
> [Per saxon community discussion here|https://saxonica.plan.io/issues/2457] ,
> {code}
> If you want detailed control over parsing, the best way is to create an
> XMLReader yourself and supply it to Saxon within a SAXSource object.
> {code}
> So we need to saxonReaderProperties option to camel-xslt-saxon endpoint, if
> saxonReaderProperties isn't null, create a XMLReader and specify features on
> it, so that we can gain fully control of xml parsed used by saxon. This is
> important to prevent XXE attack when using saxon to do xslt transform. Like
> by disabling uri=http://xml.org/sax/features/external-general-entities; to
> not access sensitive local files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14501) gain fully control of xml parser used by saxon
[
https://issues.apache.org/jira/browse/CAMEL-14501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Yue Fang updated CAMEL-14501:
-
Description:
currently we can configure TransformerFactory used by saxon by specifying
features/attributes there. However, this can only take effect on an XML parser
that Saxon creates. It has no effect if camel application creates the XML
parser (that is, if the input is supplied to Saxon as a Source object)
Per saxon community discussion here ,
If you want detailed control over parsing, the best way is to create an
XMLReader yourself and supply it to Saxon within a SAXSource object.
So we need to saxonReaderProperties option to camel-xslt-saxon endpoint, if
saxonReaderProperties isn't null, create a XMLReader and specify features on
it, so that we can gain fully control of xml parsed used by saxon. This is
important to prevent XXE attack when using saxon to do xslt transform. Like by
disabling uri=http://xml.org/sax/features/external-general-entities; to not
access sensitive local files.
> gain fully control of xml parser used by saxon
> --
>
> Key: CAMEL-14501
> URL: https://issues.apache.org/jira/browse/CAMEL-14501
> Project: Camel
> Issue Type: Improvement
> Components: camel-xslt
> Environment: currently we can configure TransformerFactory used by
> saxon by specifying features/attributes there. However, this can only take
> effect on an XML parser that Saxon creates. It has no effect if camel
> application creates the XML parser (that is, if the input is supplied to
> Saxon as a Source object)
> Per [saxon community discussion here|https://saxonica.plan.io/issues/2457m] ,
> {code}
> If you want detailed control over parsing, the best way is to create an
> XMLReader yourself and supply it to Saxon within a SAXSource object.
> {code}
> So we need to saxonReaderProperties option to camel-xslt-saxon endpoint, if
> saxonReaderProperties isn't null, create a XMLReader and specify features on
> it, so that we can gain fully control of xml parsed used by saxon. This is
> important to prevent XXE attack when using saxon to do xslt transform. Like
> by disabling uri=http://xml.org/sax/features/external-general-entities; to
> not access sensitive local files.
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
>
> currently we can configure TransformerFactory used by saxon by specifying
> features/attributes there. However, this can only take effect on an XML
> parser that Saxon creates. It has no effect if camel application creates the
> XML parser (that is, if the input is supplied to Saxon as a Source object)
> Per saxon community discussion here ,
> If you want detailed control over parsing, the best way is to create an
> XMLReader yourself and supply it to Saxon within a SAXSource object.
> So we need to saxonReaderProperties option to camel-xslt-saxon endpoint, if
> saxonReaderProperties isn't null, create a XMLReader and specify features on
> it, so that we can gain fully control of xml parsed used by saxon. This is
> important to prevent XXE attack when using saxon to do xslt transform. Like
> by disabling uri=http://xml.org/sax/features/external-general-entities; to
> not access sensitive local files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14501) gain fully control of xml parser used by saxon
[
https://issues.apache.org/jira/browse/CAMEL-14501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Yue Fang updated CAMEL-14501:
-
Environment: (was: currently we can configure TransformerFactory used
by saxon by specifying features/attributes there. However, this can only take
effect on an XML parser that Saxon creates. It has no effect if camel
application creates the XML parser (that is, if the input is supplied to Saxon
as a Source object)
Per [saxon community discussion here|https://saxonica.plan.io/issues/2457m] ,
{code}
If you want detailed control over parsing, the best way is to create an
XMLReader yourself and supply it to Saxon within a SAXSource object.
{code}
So we need to saxonReaderProperties option to camel-xslt-saxon endpoint, if
saxonReaderProperties isn't null, create a XMLReader and specify features on
it, so that we can gain fully control of xml parsed used by saxon. This is
important to prevent XXE attack when using saxon to do xslt transform. Like by
disabling uri=http://xml.org/sax/features/external-general-entities; to not
access sensitive local files.)
> gain fully control of xml parser used by saxon
> --
>
> Key: CAMEL-14501
> URL: https://issues.apache.org/jira/browse/CAMEL-14501
> Project: Camel
> Issue Type: Improvement
> Components: camel-xslt
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
>
> currently we can configure TransformerFactory used by saxon by specifying
> features/attributes there. However, this can only take effect on an XML
> parser that Saxon creates. It has no effect if camel application creates the
> XML parser (that is, if the input is supplied to Saxon as a Source object)
> Per saxon community discussion here ,
> If you want detailed control over parsing, the best way is to create an
> XMLReader yourself and supply it to Saxon within a SAXSource object.
> So we need to saxonReaderProperties option to camel-xslt-saxon endpoint, if
> saxonReaderProperties isn't null, create a XMLReader and specify features on
> it, so that we can gain fully control of xml parsed used by saxon. This is
> important to prevent XXE attack when using saxon to do xslt transform. Like
> by disabling uri=http://xml.org/sax/features/external-general-entities; to
> not access sensitive local files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14501) gain fully control of xml parser used by saxon
Freeman Yue Fang created CAMEL-14501:
Summary: gain fully control of xml parser used by saxon
Key: CAMEL-14501
URL: https://issues.apache.org/jira/browse/CAMEL-14501
Project: Camel
Issue Type: Improvement
Components: camel-xslt
Environment: currently we can configure TransformerFactory used by
saxon by specifying features/attributes there. However, this can only take
effect on an XML parser that Saxon creates. It has no effect if camel
application creates the XML parser (that is, if the input is supplied to Saxon
as a Source object)
Per [saxon community discussion here|https://saxonica.plan.io/issues/2457m] ,
{code}
If you want detailed control over parsing, the best way is to create an
XMLReader yourself and supply it to Saxon within a SAXSource object.
{code}
So we need to saxonReaderProperties option to camel-xslt-saxon endpoint, if
saxonReaderProperties isn't null, create a XMLReader and specify features on
it, so that we can gain fully control of xml parsed used by saxon. This is
important to prevent XXE attack when using saxon to do xslt transform. Like by
disabling uri=http://xml.org/sax/features/external-general-entities; to not
access sensitive local files.
Reporter: Freeman Yue Fang
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-14501) gain fully control of xml parser used by saxon
[
https://issues.apache.org/jira/browse/CAMEL-14501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Yue Fang reassigned CAMEL-14501:
Assignee: Freeman Yue Fang
> gain fully control of xml parser used by saxon
> --
>
> Key: CAMEL-14501
> URL: https://issues.apache.org/jira/browse/CAMEL-14501
> Project: Camel
> Issue Type: Improvement
> Components: camel-xslt
> Environment: currently we can configure TransformerFactory used by
> saxon by specifying features/attributes there. However, this can only take
> effect on an XML parser that Saxon creates. It has no effect if camel
> application creates the XML parser (that is, if the input is supplied to
> Saxon as a Source object)
> Per [saxon community discussion here|https://saxonica.plan.io/issues/2457m] ,
> {code}
> If you want detailed control over parsing, the best way is to create an
> XMLReader yourself and supply it to Saxon within a SAXSource object.
> {code}
> So we need to saxonReaderProperties option to camel-xslt-saxon endpoint, if
> saxonReaderProperties isn't null, create a XMLReader and specify features on
> it, so that we can gain fully control of xml parsed used by saxon. This is
> important to prevent XXE attack when using saxon to do xslt transform. Like
> by disabling uri=http://xml.org/sax/features/external-general-entities; to
> not access sensitive local files.
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14500) camel-core - spi-annotations is not optional
[ https://issues.apache.org/jira/browse/CAMEL-14500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030780#comment-17030780 ] Claus Ibsen commented on CAMEL-14500: - As spi-annotations is set in camel-core-engine, we can remove it from other places where its just duplciated > camel-core - spi-annotations is not optional > > > Key: CAMEL-14500 > URL: https://issues.apache.org/jira/browse/CAMEL-14500 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > They are no longer optional for running camel. As we look for @Component to > grab scheme name. > Caused by: java.lang.NoClassDefFoundError: > org/apache/camel/spi/annotations/Component > at org.apache.camel.support.DefaultComponent.doInit > (DefaultComponent.java:406) > at org.apache.camel.support.service.ServiceSupport.init > (ServiceSupport.java:82) > at org.apache.camel.support.service.ServiceHelper.initService > (ServiceHelper.java:55) > at org.apache.camel.impl.engine.AbstractCamelContext.initComponent > (AbstractCamelContext.java:576) > at org.apache.camel.impl.engine.AbstractCamelContext.access$000 > (AbstractCamelContext.java:170) > at org.apache.camel.impl.engine.AbstractCamelContext$2.apply > (AbstractCamelContext.java:505) > at org.apache.camel.impl.engine.AbstractCamelContext$2.apply > (AbstractCamelContext.java:501) > at java.util.concurrent.ConcurrentHashMap.computeIfAbsent > (ConcurrentHashMap.java:1660) > at org.apache.camel.impl.engine.AbstractCamelContext.getComponent > (AbstractCamelContext.java:501) > at org.apache.camel.impl.engine.AbstractCamelContext.getComponent > (AbstractCamelContext.java:477) > at org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint > (AbstractCamelContext.java:748) > at org.apache.camel.support.CamelContextHelper.getMandatoryEndpoint > (CamelContextHelper.java:57) > at org.apache.camel.impl.engine.DefaultRouteContext.resolveEndpoint > (DefaultRouteContext.java:120) > at org.apache.camel.reifier.RouteReifier.doCreateRoute > (RouteReifier.java:364) > at org.apache.camel.reifier.RouteReifier.createRoute > (RouteReifier.java:107) > at org.apache.camel.impl.DefaultModel.start (DefaultModel.java:356) > at org.apache.camel.impl.DefaultModel.startRoute (DefaultModel.java:330) > at org.apache.camel.impl.DefaultModel.startRouteDefinitions > (DefaultModel.java:323) > at org.apache.camel.impl.DefaultModel.startRouteDefinitions > (DefaultModel.java:302) > at org.apache.camel.impl.AbstractModelCamelContext.startRouteDefinitions > (AbstractModelCamelContext.java:317) > at org.apache.camel.impl.engine.AbstractCamelContext.doStartCamel > (AbstractCamelContext.java:2590) > at org.apache.camel.impl.engine.AbstractCamelContext.lambda$doStart$2 > (AbstractCamelContext.java:2442) > at > org.apache.camel.impl.engine.AbstractCamelContext.doWithDefinedClassLoader > (AbstractCamelContext.java:2459) > at org.apache.camel.impl.engine.AbstractCamelContext.doStart > (AbstractCamelContext.java:2440) > at org.apache.camel.support.service.ServiceSupport.start > (ServiceSupport.java:120) > at org.apache.camel.impl.engine.AbstractCamelContext.start > (AbstractCamelContext.java:2349) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14497) camel-core - Avoid camel-util-json if not needed
[ https://issues.apache.org/jira/browse/CAMEL-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14497. - Resolution: Fixed > camel-core - Avoid camel-util-json if not needed > > > Key: CAMEL-14497 > URL: https://issues.apache.org/jira/browse/CAMEL-14497 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > Looks like its used for the tooling and runtime catalog, so lets see if we > can move it to be only there -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14491) Create an AWS-IAM component based on SDK v2
[ https://issues.apache.org/jira/browse/CAMEL-14491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-14491. -- Resolution: Fixed > Create an AWS-IAM component based on SDK v2 > --- > > Key: CAMEL-14491 > URL: https://issues.apache.org/jira/browse/CAMEL-14491 > Project: Camel > Issue Type: Sub-task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14500) camel-core - spi-annotations is not optional
Claus Ibsen created CAMEL-14500: --- Summary: camel-core - spi-annotations is not optional Key: CAMEL-14500 URL: https://issues.apache.org/jira/browse/CAMEL-14500 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 3.1.0 They are no longer optional for running camel. As we look for @Component to grab scheme name. Caused by: java.lang.NoClassDefFoundError: org/apache/camel/spi/annotations/Component at org.apache.camel.support.DefaultComponent.doInit (DefaultComponent.java:406) at org.apache.camel.support.service.ServiceSupport.init (ServiceSupport.java:82) at org.apache.camel.support.service.ServiceHelper.initService (ServiceHelper.java:55) at org.apache.camel.impl.engine.AbstractCamelContext.initComponent (AbstractCamelContext.java:576) at org.apache.camel.impl.engine.AbstractCamelContext.access$000 (AbstractCamelContext.java:170) at org.apache.camel.impl.engine.AbstractCamelContext$2.apply (AbstractCamelContext.java:505) at org.apache.camel.impl.engine.AbstractCamelContext$2.apply (AbstractCamelContext.java:501) at java.util.concurrent.ConcurrentHashMap.computeIfAbsent (ConcurrentHashMap.java:1660) at org.apache.camel.impl.engine.AbstractCamelContext.getComponent (AbstractCamelContext.java:501) at org.apache.camel.impl.engine.AbstractCamelContext.getComponent (AbstractCamelContext.java:477) at org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint (AbstractCamelContext.java:748) at org.apache.camel.support.CamelContextHelper.getMandatoryEndpoint (CamelContextHelper.java:57) at org.apache.camel.impl.engine.DefaultRouteContext.resolveEndpoint (DefaultRouteContext.java:120) at org.apache.camel.reifier.RouteReifier.doCreateRoute (RouteReifier.java:364) at org.apache.camel.reifier.RouteReifier.createRoute (RouteReifier.java:107) at org.apache.camel.impl.DefaultModel.start (DefaultModel.java:356) at org.apache.camel.impl.DefaultModel.startRoute (DefaultModel.java:330) at org.apache.camel.impl.DefaultModel.startRouteDefinitions (DefaultModel.java:323) at org.apache.camel.impl.DefaultModel.startRouteDefinitions (DefaultModel.java:302) at org.apache.camel.impl.AbstractModelCamelContext.startRouteDefinitions (AbstractModelCamelContext.java:317) at org.apache.camel.impl.engine.AbstractCamelContext.doStartCamel (AbstractCamelContext.java:2590) at org.apache.camel.impl.engine.AbstractCamelContext.lambda$doStart$2 (AbstractCamelContext.java:2442) at org.apache.camel.impl.engine.AbstractCamelContext.doWithDefinedClassLoader (AbstractCamelContext.java:2459) at org.apache.camel.impl.engine.AbstractCamelContext.doStart (AbstractCamelContext.java:2440) at org.apache.camel.support.service.ServiceSupport.start (ServiceSupport.java:120) at org.apache.camel.impl.engine.AbstractCamelContext.start (AbstractCamelContext.java:2349) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13830) Move examples to a new camel-examples git repo
[ https://issues.apache.org/jira/browse/CAMEL-13830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13830: Fix Version/s: (was: 3.x) 3.1.0 > Move examples to a new camel-examples git repo > -- > > Key: CAMEL-13830 > URL: https://issues.apache.org/jira/browse/CAMEL-13830 > Project: Camel > Issue Type: Improvement > Components: examples >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > I think it may be quicker and easier for new users to try our examples if we > put them in a separate repo, so there is less source code. The git repo for > Camel is very big, and it takes a longer time to checkout, and users may get > lost in the source code. > If we have a camel-examples git repo with just examples we can refer people > to this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13830) Move examples to a new camel-examples git repo
[ https://issues.apache.org/jira/browse/CAMEL-13830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030676#comment-17030676 ] Claus Ibsen commented on CAMEL-13830: - The git repo is ready https://github.com/apache/camel-examples > Move examples to a new camel-examples git repo > -- > > Key: CAMEL-13830 > URL: https://issues.apache.org/jira/browse/CAMEL-13830 > Project: Camel > Issue Type: Improvement > Components: examples >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > I think it may be quicker and easier for new users to try our examples if we > put them in a separate repo, so there is less source code. The git repo for > Camel is very big, and it takes a longer time to checkout, and users may get > lost in the source code. > If we have a camel-examples git repo with just examples we can refer people > to this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14499) camel-core - SendDynamicAware avoid camel-core-catalog dependency
[ https://issues.apache.org/jira/browse/CAMEL-14499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030669#comment-17030669 ] Claus Ibsen commented on CAMEL-14499: - This affects - camel-file - camel-ftp and all the http components > camel-core - SendDynamicAware avoid camel-core-catalog dependency > - > > Key: CAMEL-14499 > URL: https://issues.apache.org/jira/browse/CAMEL-14499 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > Find out a way by source code generate for these components the parts we need > for this to work, or have a base class in camel-support they can use -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14499) camel-core - SendDynamicAware avoid camel-core-catalog dependency
Claus Ibsen created CAMEL-14499: --- Summary: camel-core - SendDynamicAware avoid camel-core-catalog dependency Key: CAMEL-14499 URL: https://issues.apache.org/jira/browse/CAMEL-14499 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.1.0 Find out a way by source code generate for these components the parts we need for this to work, or have a base class in camel-support they can use -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14498) camel-core - Make RuntimeCamelCatalog a simpler API
Claus Ibsen created CAMEL-14498: --- Summary: camel-core - Make RuntimeCamelCatalog a simpler API Key: CAMEL-14498 URL: https://issues.apache.org/jira/browse/CAMEL-14498 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.1.0 We should only have a limited API for the pieces we need. Then camel-catalog can have a bigger API for 3rd party tooling and our own tooling can use. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14496) Add a Kotlin DSL to camel
[ https://issues.apache.org/jira/browse/CAMEL-14496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030662#comment-17030662 ] Omar Al-Safi commented on CAMEL-14496: -- I am honestly neutral about it, however we can start this discussion in the dev mailing list > Add a Kotlin DSL to camel > - > > Key: CAMEL-14496 > URL: https://issues.apache.org/jira/browse/CAMEL-14496 > Project: Camel > Issue Type: New Feature > Components: camel-kotlin >Affects Versions: 3.0.1 >Reporter: Omar Al-Safi >Priority: Minor > Fix For: Future > > > When we were in FOSDEM, we got asked few times if we have a kotlin DSL. Hence > I decided to create this ticket as a placeholder. However I am not really > sure about its feasibility and longer term plans. What do you guys thought of > this? [~acosentino] [~davsclaus] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14497) camel-core - Avoid camel-util-json if not needed
Claus Ibsen created CAMEL-14497: --- Summary: camel-core - Avoid camel-util-json if not needed Key: CAMEL-14497 URL: https://issues.apache.org/jira/browse/CAMEL-14497 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.1.0 Looks like its used for the tooling and runtime catalog, so lets see if we can move it to be only there -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14496) Add a Kotlin DSL to camel
[ https://issues.apache.org/jira/browse/CAMEL-14496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030660#comment-17030660 ] Andrea Cosentino commented on CAMEL-14496: -- Maybe we can have a discussion on the dev mailing list.. In the past this kind of stuff wasn't easy to mantain... This is my first thought :D > Add a Kotlin DSL to camel > - > > Key: CAMEL-14496 > URL: https://issues.apache.org/jira/browse/CAMEL-14496 > Project: Camel > Issue Type: New Feature > Components: camel-kotlin >Affects Versions: 3.0.1 >Reporter: Omar Al-Safi >Priority: Minor > Fix For: Future > > > When we were in FOSDEM, we got asked few times if we have a kotlin DSL. Hence > I decided to create this ticket as a placeholder. However I am not really > sure about its feasibility and longer term plans. What do you guys thought of > this? [~acosentino] [~davsclaus] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14496) Add a Kotlin DSL to camel
Omar Al-Safi created CAMEL-14496: Summary: Add a Kotlin DSL to camel Key: CAMEL-14496 URL: https://issues.apache.org/jira/browse/CAMEL-14496 Project: Camel Issue Type: New Feature Components: camel-kotlin Affects Versions: 3.0.1 Reporter: Omar Al-Safi Fix For: Future When we were in FOSDEM, we got asked few times if we have a kotlin DSL. Hence I decided to create this ticket as a placeholder. However I am not really sure about its feasibility and longer term plans. What do you guys thought of this? [~acosentino] [~davsclaus] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14495) OPC UA Client samplingInterval parameter seems not take any effect
[
https://issues.apache.org/jira/browse/CAMEL-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hobbert updated CAMEL-14495:
Description:
When I set the *samplingInterval* parameter on a Milo OPC UA Client route, the
interval not changes on the real OPC application! Remains 1000 mili seconds
even after configuring!! Can anyone confirm that??
Heres my route
http://camel.apache.org/schema/spring; >
${in.body}
Thanks
was:
When I set the *samplingInterval* parameter on a Milo OPC UA Client route, the
interval not changes on the real OPC application! Remains 1000 mili seconds
even before configuring!! Can anyone confirm that??
Heres my route
http://camel.apache.org/schema/spring; >
${in.body}
Thanks
> OPC UA Client samplingInterval parameter seems not take any effect
> --
>
> Key: CAMEL-14495
> URL: https://issues.apache.org/jira/browse/CAMEL-14495
> Project: Camel
> Issue Type: Test
> Components: camel-milo
>Affects Versions: 2.25.0
>Reporter: Hobbert
>Priority: Major
>
> When I set the *samplingInterval* parameter on a Milo OPC UA Client route,
> the interval not changes on the real OPC application! Remains 1000 mili
> seconds even after configuring!! Can anyone confirm that??
> Heres my route
> http://camel.apache.org/schema/spring; >
>
> uri="milo-client:tcp://192.168.0.2:4840?samplingInterval=50=RAW(ns=4;i=12)"/>
>
> ${in.body}
>
>
>
> Thanks
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14495) OPC UA Client samplingInterval parameter seems not take any effect
[
https://issues.apache.org/jira/browse/CAMEL-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hobbert updated CAMEL-14495:
Description:
When I set the *samplingInterval* parameter on a Milo OPC UA Client route, the
interval not changes on the real OPC application! Remains 1000 mili seconds
even before configuring!! Can anyone confirm that??
Heres my route
http://camel.apache.org/schema/spring; >
${in.body}
Thanks
was:
When I set the *samplingInterval* parameter on a Milo OPC UA Client route, the
interval not changes on the real OPC application! Remais 1000 mili seconds even
before configuring!! Can anyone confirm that??
Heres my route
http://camel.apache.org/schema/spring; >
${in.body}
Thanks
> OPC UA Client samplingInterval parameter seems not take any effect
> --
>
> Key: CAMEL-14495
> URL: https://issues.apache.org/jira/browse/CAMEL-14495
> Project: Camel
> Issue Type: Test
> Components: camel-milo
>Affects Versions: 2.25.0
>Reporter: Hobbert
>Priority: Major
>
> When I set the *samplingInterval* parameter on a Milo OPC UA Client route,
> the interval not changes on the real OPC application! Remains 1000 mili
> seconds even before configuring!! Can anyone confirm that??
> Heres my route
> http://camel.apache.org/schema/spring; >
>
> uri="milo-client:tcp://192.168.0.2:4840?samplingInterval=50=RAW(ns=4;i=12)"/>
>
> ${in.body}
>
>
>
> Thanks
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14495) OPC UA Client samplingInterval parameter seems not take any effect
Hobbert created CAMEL-14495:
---
Summary: OPC UA Client samplingInterval parameter seems not take
any effect
Key: CAMEL-14495
URL: https://issues.apache.org/jira/browse/CAMEL-14495
Project: Camel
Issue Type: Test
Components: camel-milo
Affects Versions: 2.25.0
Reporter: Hobbert
When I set the *samplingInterval* parameter on a Milo OPC UA Client route, the
interval not changes on the real OPC application! Remais 1000 mili seconds even
before configuring!! Can anyone confirm that??
Heres my route
http://camel.apache.org/schema/spring; >
${in.body}
Thanks
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (CAMEL-14344) camel-milo - Upgrade to newer milo version
[ https://issues.apache.org/jira/browse/CAMEL-14344?focusedWorklogId=382256=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-382256 ] ASF GitHub Bot logged work on CAMEL-14344: -- Author: ASF GitHub Bot Created on: 05/Feb/20 12:55 Start Date: 05/Feb/20 12:55 Worklog Time Spent: 10m Work Description: JiriOndrusek commented on pull request #3548: CAMEL-14344 camel-milo - Upgrade to newer milo version URL: https://github.com/apache/camel/pull/3548 Issue: https://issues.apache.org/jira/browse/CAMEL-14344 Upgrade of Milo from version 0.2.5 to version 0.3.7. Configuration has been refactored because it was changed in Milo library. Java 9 is now required. Several tests are ignored for execution on jdk 8. 1 property on server Milo component was removed (as it was removed in milo library): strictEndpointUrlsEnabled - eclipse/milo#277 2 properties were changed: serverName was replaced by path. hostName (it was the same property as serverName) was replaced by path too. Endpoint syntax was changed from ..:tcp:.. to ..:opc.tcp:.. according to the milo library. All changes are mentioned in 3x-upgrade-guide. Replaces https://github.com/apache/camel/pull/3539 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: 382256) Time Spent: 50m (was: 40m) > camel-milo - Upgrade to newer milo version > -- > > Key: CAMEL-14344 > URL: https://issues.apache.org/jira/browse/CAMEL-14344 > Project: Camel > Issue Type: Improvement > Components: camel-milo > Environment: There is a 0.3.6 release >Reporter: Claus Ibsen >Assignee: Jiri Ondrusek >Priority: Minor > Fix For: 3.x > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14494) Breakdown azure-component into multiple components similar to the aws component
[ https://issues.apache.org/jira/browse/CAMEL-14494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omar Al-Safi updated CAMEL-14494: - Issue Type: Task (was: New Feature) > Breakdown azure-component into multiple components similar to the aws > component > --- > > Key: CAMEL-14494 > URL: https://issues.apache.org/jira/browse/CAMEL-14494 > Project: Camel > Issue Type: Task > Components: camel-azure >Affects Versions: 3.0.1 >Reporter: Omar Al-Safi >Priority: Minor > Fix For: 3.x > > > Similar to the aws component, we can break down the azure component into > multiple components so it will be easier to add more azure services as > components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14494) Breakdown azure-component into multiple components similar to the aws component
Omar Al-Safi created CAMEL-14494: Summary: Breakdown azure-component into multiple components similar to the aws component Key: CAMEL-14494 URL: https://issues.apache.org/jira/browse/CAMEL-14494 Project: Camel Issue Type: New Feature Components: camel-azure Affects Versions: 3.0.1 Reporter: Omar Al-Safi Fix For: 3.x Similar to the aws component, we can break down the azure component into multiple components so it will be easier to add more azure services as components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth closed CAMEL-14493. - > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 2.25.1 > > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) > > Thanks @cmonmous for reporting the issue ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-14493. --- Resolution: Fixed [https://github.com/apache/camel/pull/3546] > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 2.25.1 > > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) > > Thanks @cmonmous for reporting the issue ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-14493: -- Fix Version/s: 2.25.1 > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 2.25.1 > > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) > > Thanks @cmonmous for reporting the issue ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-14493: -- Description: java.lang.ClassNotFoundException: org.apache.camel.spring.Main at java.net.URLClassLoader.findClass (URLClassLoader.java:382) at java.lang.ClassLoader.loadClass (ClassLoader.java:418) at java.lang.ClassLoader.loadClass (ClassLoader.java:351) at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) at java.lang.Thread.run (Thread.java:748) Thanks @cmonmous for reporting the issue ! was: java.lang.ClassNotFoundException: org.apache.camel.spring.Main at java.net.URLClassLoader.findClass (URLClassLoader.java:382) at java.lang.ClassLoader.loadClass (ClassLoader.java:418) at java.lang.ClassLoader.loadClass (ClassLoader.java:351) at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) at java.lang.Thread.run (Thread.java:748) Thanks @cmou > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) > > Thanks @cmonmous for reporting the issue ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-11947) Race condition in iec60870 producer
[ https://issues.apache.org/jira/browse/CAMEL-11947?focusedWorklogId=382202=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-382202 ] ASF GitHub Bot logged work on CAMEL-11947: -- Author: ASF GitHub Bot Created on: 05/Feb/20 11:27 Start Date: 05/Feb/20 11:27 Worklog Time Spent: 10m Work Description: tdiesler commented on pull request #3547: [CAMEL-11947] Race condition in iec60870 producer URL: https://github.com/apache/camel/pull/3547 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: 382202) Time Spent: 50m (was: 40m) > Race condition in iec60870 producer > --- > > Key: CAMEL-11947 > URL: https://issues.apache.org/jira/browse/CAMEL-11947 > Project: Camel > Issue Type: Bug > Components: camel-iec60870 >Affects Versions: 2.20.0 >Reporter: James Netherton >Assignee: Thomas Diesler >Priority: Minor > Fix For: 3.1.0 > > Time Spent: 50m > Remaining Estimate: 0h > > I've been working on integrating the iec60870 component with WIldFly. I have > an integration test > [here|https://github.com/wildfly-extras/wildfly-camel/blob/master/itests/standalone/basic/src/test/java/org/wildfly/camel/test/iec60870/Iec60870IntegrationTest.java]. > When it's executed on its own, everything works fine. When it runs with the > entire test suite, I encounter a NullPointerException in the Neoscada > [Client.writeCommand()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L259] > method. > It seems that the Netty channel that it's trying to write to is null and that > initialisation of the channel happens async in > [Client.handleOperationComplete()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L138]. > When I debug, I see the channel gets initialised after the call to > writeCommand(). > Not sure if there's any way to detect whether the client connection has been > established before trying to use it in the > [ClientProducer|https://github.com/apache/camel/blob/master/components/camel-iec60870/src/main/java/org/apache/camel/component/iec60870/client/ClientProducer.java#L49]. > Or maybe this ticket would be better placed with the neoscada project? > > CrossRef > [https://github.com/wildfly-extras/wildfly-camel/issues/2236] > [https://issues.redhat.com/browse/ENTESB-12557] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-14493: -- Description: java.lang.ClassNotFoundException: org.apache.camel.spring.Main at java.net.URLClassLoader.findClass (URLClassLoader.java:382) at java.lang.ClassLoader.loadClass (ClassLoader.java:418) at java.lang.ClassLoader.loadClass (ClassLoader.java:351) at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) at java.lang.Thread.run (Thread.java:748) Thanks @cmou was: java.lang.ClassNotFoundException: org.apache.camel.spring.Main at java.net.URLClassLoader.findClass (URLClassLoader.java:382) at java.lang.ClassLoader.loadClass (ClassLoader.java:418) at java.lang.ClassLoader.loadClass (ClassLoader.java:351) at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) at java.lang.Thread.run (Thread.java:748) > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) > > Thanks @cmou -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14448) Move all generated source code in git
[ https://issues.apache.org/jira/browse/CAMEL-14448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030569#comment-17030569 ] Andrea Cosentino commented on CAMEL-14448: -- They should, yes. > Move all generated source code in git > - > > Key: CAMEL-14448 > URL: https://issues.apache.org/jira/browse/CAMEL-14448 > Project: Camel > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14448) Move all generated source code in git
[ https://issues.apache.org/jira/browse/CAMEL-14448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030562#comment-17030562 ] Omar Al-Safi commented on CAMEL-14448: -- [~gnodet] [~acosentino] If not mistaken, if we have all the generated source files in git, should they contain the license headers? > Move all generated source code in git > - > > Key: CAMEL-14448 > URL: https://issues.apache.org/jira/browse/CAMEL-14448 > Project: Camel > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14485) camel-componentdsl - Sort the component in the pom.xml and ComponentsBuilderFactory
[ https://issues.apache.org/jira/browse/CAMEL-14485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omar Al-Safi resolved CAMEL-14485. -- Resolution: Fixed > camel-componentdsl - Sort the component in the pom.xml and > ComponentsBuilderFactory > --- > > Key: CAMEL-14485 > URL: https://issues.apache.org/jira/browse/CAMEL-14485 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Omar Al-Safi >Priority: Minor > Fix For: 3.1.0 > > > They are in random order, we should sort them a..z so its easier to see the > list in the pom.xml of camel-componentdsl -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-14493: - Assignee: John Poth > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
John Poth created CAMEL-14493: - Summary: camel 2: mvn camel:run fails on spring projects Key: CAMEL-14493 URL: https://issues.apache.org/jira/browse/CAMEL-14493 Project: Camel Issue Type: Bug Affects Versions: 2.25.0 Reporter: John Poth java.lang.ClassNotFoundException: org.apache.camel.spring.Main at java.net.URLClassLoader.findClass (URLClassLoader.java:382) at java.lang.ClassLoader.loadClass (ClassLoader.java:418) at java.lang.ClassLoader.loadClass (ClassLoader.java:351) at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) at java.lang.Thread.run (Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14492) EtcdKeysEndpoint cannot be cast to AbstractEtcdPollingEndpoint
[
https://issues.apache.org/jira/browse/CAMEL-14492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-14492:
---
Description:
{code:java}
Caused by: org.apache.camel.PropertyBindingException: Error binding property
(uris=http://192.168.178.30:23379,http://192.168.178.30:40001) with name: uris
on bean:
etcd://keys?uris=http%3A%2F%2F192.168.178.30%3A23379%2Chttp%3A%2F%2F192.168.178.30%3A40001
with value: http://192.168.178.30:23379,http://192.168.178.30:40001
at
org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:502)
at
org.apache.camel.support.PropertyBindingSupport.access$000(PropertyBindingSupport.java:62)
at
org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:250)
at
org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:513)
at
org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:482)
at
org.apache.camel.component.etcd.EtcdComponent.createEndpoint(EtcdComponent.java:153)
at
org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:245)
at
org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:756)
... 168 more
Caused by: java.lang.ClassCastException:
org.apache.camel.component.etcd.EtcdKeysEndpoint cannot be cast to
org.apache.camel.component.etcd.AbstractEtcdPollingEndpoint
at
org.apache.camel.component.etcd.AbstractEtcdPollingEndpointConfigurer.doConfigure(AbstractEtcdPollingEndpointConfigurer.java:28)
at
org.apache.camel.component.etcd.AbstractEtcdPollingEndpointConfigurer.configure(AbstractEtcdPollingEndpointConfigurer.java:19)
at
org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:497)
... 175 more
{code}
Shows with this test:
https://github.com/wildfly-extras/wildfly-camel/blob/master/itests/standalone/docker/src/test/java/org/wildfly/camel/test/etcd/EtcdIntegrationTest.java
was:
{code}
Caused by: org.apache.camel.PropertyBindingException: Error binding property
(uris=http://192.168.178.30:23379,http://192.168.178.30:40001) with name: uris
on bean:
etcd://keys?uris=http%3A%2F%2F192.168.178.30%3A23379%2Chttp%3A%2F%2F192.168.178.30%3A40001
with value: http://192.168.178.30:23379,http://192.168.178.30:40001
at
org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:502)
at
org.apache.camel.support.PropertyBindingSupport.access$000(PropertyBindingSupport.java:62)
at
org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:250)
at
org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:513)
at
org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:482)
at
org.apache.camel.component.etcd.EtcdComponent.createEndpoint(EtcdComponent.java:153)
at
org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:245)
at
org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:756)
... 168 more
Caused by: java.lang.ClassCastException:
org.apache.camel.component.etcd.EtcdKeysEndpoint cannot be cast to
org.apache.camel.component.etcd.AbstractEtcdPollingEndpoint
at
org.apache.camel.component.etcd.AbstractEtcdPollingEndpointConfigurer.doConfigure(AbstractEtcdPollingEndpointConfigurer.java:28)
at
org.apache.camel.component.etcd.AbstractEtcdPollingEndpointConfigurer.configure(AbstractEtcdPollingEndpointConfigurer.java:19)
at
org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:497)
... 175 more
{code}
> EtcdKeysEndpoint cannot be cast to AbstractEtcdPollingEndpoint
> --
>
> Key: CAMEL-14492
> URL: https://issues.apache.org/jira/browse/CAMEL-14492
> Project: Camel
> Issue Type: Bug
> Components: camel-etcd
>Affects Versions: 3.x
>Reporter: Thomas Diesler
>Priority: Major
>
> {code:java}
> Caused by: org.apache.camel.PropertyBindingException: Error binding property
> (uris=http://192.168.178.30:23379,http://192.168.178.30:40001) with name:
> uris on bean:
> etcd://keys?uris=http%3A%2F%2F192.168.178.30%3A23379%2Chttp%3A%2F%2F192.168.178.30%3A40001
> with value: http://192.168.178.30:23379,http://192.168.178.30:40001
> at
> org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:502)
> at
> org.apache.camel.support.PropertyBindingSupport.access$000(PropertyBindingSupport.java:62)
> at
> org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:250)
> at
> org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:513)
> at
>
[jira] [Updated] (CAMEL-14492) EtcdKeysEndpoint cannot be cast to AbstractEtcdPollingEndpoint
[
https://issues.apache.org/jira/browse/CAMEL-14492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-14492:
---
Summary: EtcdKeysEndpoint cannot be cast to AbstractEtcdPollingEndpoint
(was: CCE: EtcdKeysEndpoint cannot be cast to AbstractEtcdPollingEndpoint)
> EtcdKeysEndpoint cannot be cast to AbstractEtcdPollingEndpoint
> --
>
> Key: CAMEL-14492
> URL: https://issues.apache.org/jira/browse/CAMEL-14492
> Project: Camel
> Issue Type: Bug
> Components: camel-etcd
>Affects Versions: 3.x
>Reporter: Thomas Diesler
>Priority: Major
>
> {code}
> Caused by: org.apache.camel.PropertyBindingException: Error binding property
> (uris=http://192.168.178.30:23379,http://192.168.178.30:40001) with name:
> uris on bean:
> etcd://keys?uris=http%3A%2F%2F192.168.178.30%3A23379%2Chttp%3A%2F%2F192.168.178.30%3A40001
> with value: http://192.168.178.30:23379,http://192.168.178.30:40001
> at
> org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:502)
> at
> org.apache.camel.support.PropertyBindingSupport.access$000(PropertyBindingSupport.java:62)
> at
> org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:250)
> at
> org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:513)
> at
> org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:482)
> at
> org.apache.camel.component.etcd.EtcdComponent.createEndpoint(EtcdComponent.java:153)
> at
> org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:245)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:756)
> ... 168 more
> Caused by: java.lang.ClassCastException:
> org.apache.camel.component.etcd.EtcdKeysEndpoint cannot be cast to
> org.apache.camel.component.etcd.AbstractEtcdPollingEndpoint
> at
> org.apache.camel.component.etcd.AbstractEtcdPollingEndpointConfigurer.doConfigure(AbstractEtcdPollingEndpointConfigurer.java:28)
> at
> org.apache.camel.component.etcd.AbstractEtcdPollingEndpointConfigurer.configure(AbstractEtcdPollingEndpointConfigurer.java:19)
> at
> org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:497)
> ... 175 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14492) CCE: EtcdKeysEndpoint cannot be cast to AbstractEtcdPollingEndpoint
Thomas Diesler created CAMEL-14492:
--
Summary: CCE: EtcdKeysEndpoint cannot be cast to
AbstractEtcdPollingEndpoint
Key: CAMEL-14492
URL: https://issues.apache.org/jira/browse/CAMEL-14492
Project: Camel
Issue Type: Bug
Components: camel-etcd
Affects Versions: 3.x
Reporter: Thomas Diesler
{code}
Caused by: org.apache.camel.PropertyBindingException: Error binding property
(uris=http://192.168.178.30:23379,http://192.168.178.30:40001) with name: uris
on bean:
etcd://keys?uris=http%3A%2F%2F192.168.178.30%3A23379%2Chttp%3A%2F%2F192.168.178.30%3A40001
with value: http://192.168.178.30:23379,http://192.168.178.30:40001
at
org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:502)
at
org.apache.camel.support.PropertyBindingSupport.access$000(PropertyBindingSupport.java:62)
at
org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:250)
at
org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:513)
at
org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:482)
at
org.apache.camel.component.etcd.EtcdComponent.createEndpoint(EtcdComponent.java:153)
at
org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:245)
at
org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:756)
... 168 more
Caused by: java.lang.ClassCastException:
org.apache.camel.component.etcd.EtcdKeysEndpoint cannot be cast to
org.apache.camel.component.etcd.AbstractEtcdPollingEndpoint
at
org.apache.camel.component.etcd.AbstractEtcdPollingEndpointConfigurer.doConfigure(AbstractEtcdPollingEndpointConfigurer.java:28)
at
org.apache.camel.component.etcd.AbstractEtcdPollingEndpointConfigurer.configure(AbstractEtcdPollingEndpointConfigurer.java:19)
at
org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:497)
... 175 more
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-14461) camel-core - Make RuntimeCatalog optional and in its own module
[ https://issues.apache.org/jira/browse/CAMEL-14461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-14461: --- Assignee: Claus Ibsen > camel-core - Make RuntimeCatalog optional and in its own module > --- > > Key: CAMEL-14461 > URL: https://issues.apache.org/jira/browse/CAMEL-14461 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > Lets see if we can move RuntimeCamelCatalog to its own module and make it > optional. > Its used by component extension verifiers and components that use dynamic to > optimization like toD with http components. But we can look at source code > generate what they may need for this, so it can be more optional. > The new tooling model classes can then also become optional so we can keep > plain Camel JARs to less JARs and classes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14461) camel-core - Make RuntimeCatalog optional and in its own module
[ https://issues.apache.org/jira/browse/CAMEL-14461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14461: Fix Version/s: (was: 3.x) 3.1.0 > camel-core - Make RuntimeCatalog optional and in its own module > --- > > Key: CAMEL-14461 > URL: https://issues.apache.org/jira/browse/CAMEL-14461 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > Lets see if we can move RuntimeCamelCatalog to its own module and make it > optional. > Its used by component extension verifiers and components that use dynamic to > optimization like toD with http components. But we can look at source code > generate what they may need for this, so it can be more optional. > The new tooling model classes can then also become optional so we can keep > plain Camel JARs to less JARs and classes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14478) Create an AWS-KMS component based on SDK v2
[ https://issues.apache.org/jira/browse/CAMEL-14478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-14478. -- Resolution: Fixed > Create an AWS-KMS component based on SDK v2 > --- > > Key: CAMEL-14478 > URL: https://issues.apache.org/jira/browse/CAMEL-14478 > Project: Camel > Issue Type: Sub-task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14491) Create an AWS-IAM component based on SDK v2
Andrea Cosentino created CAMEL-14491: Summary: Create an AWS-IAM component based on SDK v2 Key: CAMEL-14491 URL: https://issues.apache.org/jira/browse/CAMEL-14491 Project: Camel Issue Type: Sub-task Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.1.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14483) camel-endpointdsl dependency on camel-jaxp and camel-util-json
[ https://issues.apache.org/jira/browse/CAMEL-14483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030515#comment-17030515 ] Claus Ibsen commented on CAMEL-14483: - Yeah it should only depend on camel-core-engine (due to route builder) > camel-endpointdsl dependency on camel-jaxp and camel-util-json > -- > > Key: CAMEL-14483 > URL: https://issues.apache.org/jira/browse/CAMEL-14483 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-endpointdsl >Affects Versions: 3.0.1 >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.1.0 > > > camel-endpointdsl has direct dependencies on camel-jaxp and camel-util-json, > see: > * > https://github.com/apache/camel/blob/master/core/camel-endpointdsl/pom.xml#L60 > * > https://github.com/apache/camel/blob/master/core/camel-endpointdsl/pom.xml#L64 > Both dependencies do not seem really needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14483) camel-endpointdsl dependency on camel-jaxp and camel-util-json
[ https://issues.apache.org/jira/browse/CAMEL-14483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14483. - Assignee: Claus Ibsen Resolution: Fixed > camel-endpointdsl dependency on camel-jaxp and camel-util-json > -- > > Key: CAMEL-14483 > URL: https://issues.apache.org/jira/browse/CAMEL-14483 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-endpointdsl >Affects Versions: 3.0.1 >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.1.0 > > > camel-endpointdsl has direct dependencies on camel-jaxp and camel-util-json, > see: > * > https://github.com/apache/camel/blob/master/core/camel-endpointdsl/pom.xml#L60 > * > https://github.com/apache/camel/blob/master/core/camel-endpointdsl/pom.xml#L64 > Both dependencies do not seem really needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14487) camel-jaxp - Rename to camel-xml-jaxp
[ https://issues.apache.org/jira/browse/CAMEL-14487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14487. - Resolution: Fixed > camel-jaxp - Rename to camel-xml-jaxp > - > > Key: CAMEL-14487 > URL: https://issues.apache.org/jira/browse/CAMEL-14487 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > So it has xml in its name and similar to camel-xml-jaxb and camel-xml-io -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14459) camel-webhook - RAW() parameter value handling in delegated URI
[
https://issues.apache.org/jira/browse/CAMEL-14459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030481#comment-17030481
]
Tadayoshi Sato commented on CAMEL-14459:
Worse, for camel-webhook {{RAW()}} wrapper seems to be stripped and thus
ignored at all. I'll take care of it here.
> camel-webhook - RAW() parameter value handling in delegated URI
> ---
>
> Key: CAMEL-14459
> URL: https://issues.apache.org/jira/browse/CAMEL-14459
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Tadayoshi Sato
>Assignee: Tadayoshi Sato
>Priority: Major
>
> It's possible that camel-webhook has the same issue as CAMEL-14456 with
> camel-master on handling {{RAW()}} parameter in the delegated URI. Let's
> check if it really has the issue or not.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (CAMEL-14459) camel-webhook - RAW() parameter value handling in delegated URI
[
https://issues.apache.org/jira/browse/CAMEL-14459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-14459 started by Tadayoshi Sato.
--
> camel-webhook - RAW() parameter value handling in delegated URI
> ---
>
> Key: CAMEL-14459
> URL: https://issues.apache.org/jira/browse/CAMEL-14459
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Tadayoshi Sato
>Assignee: Tadayoshi Sato
>Priority: Major
>
> It's possible that camel-webhook has the same issue as CAMEL-14456 with
> camel-master on handling {{RAW()}} parameter in the delegated URI. Let's
> check if it really has the issue or not.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14440) Add Workday report as a service component.
[ https://issues.apache.org/jira/browse/CAMEL-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030447#comment-17030447 ] Fernando Avalos commented on CAMEL-14440: - Hi, [~dmvolod] I just merge the code and tested the new syntax and it works perfectly. I did take a look to the code and you clarify some doubts I had. I will work on top of the changes, and I will create a Jira when I am ready to start working on the addition of the queue. I am planning to write a post about how to use the component and the test I did. Thank you so much, > Add Workday report as a service component. > -- > > Key: CAMEL-14440 > URL: https://issues.apache.org/jira/browse/CAMEL-14440 > Project: Camel > Issue Type: New Feature > Components: camel-workday >Reporter: Fernando Avalos >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.1.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Create a Workday component to consume Workday report as a service in Camel. > The component must be ready to work with a Workday Client API for > Integrations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
