[jira] [Created] (CAMEL-15597) camel-servicenow: consider replacing cxf with vert.x web
Luca Burgazzoli created CAMEL-15597: --- Summary: camel-servicenow: consider replacing cxf with vert.x web Key: CAMEL-15597 URL: https://issues.apache.org/jira/browse/CAMEL-15597 Project: Camel Issue Type: Improvement Components: camel-salesforce Reporter: Luca Burgazzoli As today we use CXF behind the scenes but we can explore a replacement with a modern reactive web client such as Vert.x HTTP -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15596) camel-jacksonxml feature install failed due to stax2 version
Xilai Dai created CAMEL-15596:
-
Summary: camel-jacksonxml feature install failed due to stax2
version
Key: CAMEL-15596
URL: https://issues.apache.org/jira/browse/CAMEL-15596
Project: Camel
Issue Type: Bug
Components: osgi
Affects Versions: 2.25.2, 2.24.2
Reporter: Xilai Dai
Start karaf 4.2.9 OSGi container, execute:
karaf@root()> feature:repo-add camel 2.25.2
karaf@root()> feature:install camel-jacksonxml
{code}
Error executing command: Unable to resolve root: missing requirement [root]
osgi.identity; osgi.identity=camel-jacksonxml; type=karaf.feature;
version="[2.25.2,2.25.2]";
filter:="(&(osgi.identity=camel-jacksonxml)(type=karaf.feature)(version>=2.25.2)(version<=2.25.2))"
[caused by: Unable to resolve camel-jacksonxml/2.25.2: missing requirement
[camel-jacksonxml/2.25.2] osgi.identity;
osgi.identity=org.apache.camel.camel-jacksonxml; type=osgi.bundle;
version="[2.25.2,2.25.2]"; resolution:=mandatory [caused by: Unable to resolve
org.apache.camel.camel-jacksonxml/2.25.2: missing requirement
[org.apache.camel.camel-jacksonxml/2.25.2] osgi.wiring.package;
filter:="(&(osgi.wiring.package=com.fasterxml.jackson.dataformat.xml)(version>=2.3.0)(!(version>=3.0.0)))"
[caused by: Unable to resolve
com.fasterxml.jackson.dataformat.jackson-dataformat-xml/2.9.10: missing
requirement [com.fasterxml.jackson.dataformat.jackson-dataformat-xml/2.9.10]
osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.codehaus.stax2)(version>=4.2.0)(!(version>=5.0.0)))"]]]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-15595) Extend math operators in Simple language
[ https://issues.apache.org/jira/browse/CAMEL-15595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Bednar updated CAMEL-15595: --- Issue Type: New Feature (was: Bug) Priority: Minor (was: Major) Summary: Extend math operators in Simple language (was: math (and other) calculation in route) > Extend math operators in Simple language > > > Key: CAMEL-15595 > URL: https://issues.apache.org/jira/browse/CAMEL-15595 > Project: Camel > Issue Type: New Feature > Components: came-core >Reporter: Luca Ferrari >Priority: Minor > > at the moment simple calculations with maths operators like: > * addition > * multiplication > * division > * subtraction > * modulus > are not supported in simple language. It is true that you could use groovy or > javascript, but given simple syntax overall prevalence in camel it would make > it easier to support this directly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15595) math (and other) calculation in route
Luca Ferrari created CAMEL-15595: Summary: math (and other) calculation in route Key: CAMEL-15595 URL: https://issues.apache.org/jira/browse/CAMEL-15595 Project: Camel Issue Type: Bug Components: came-core Reporter: Luca Ferrari at the moment simple calculations with maths operators like: * addition * multiplication * division * subtraction * modulus are not supported in simple language. It is true that you could use groovy or javascript, but given simple syntax overall prevalence in camel it would make it easier to support this directly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-4169) simple calculations in route
[
https://issues.apache.org/jira/browse/CAMEL-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17204164#comment-17204164
]
Claus Ibsen commented on CAMEL-4169:
You can use 3rd party languages like groovy, or mvel (that is java) that is
more powerful.
But the simple parser has since this JIRA been rewritten and it can potentially
be improved to have more operators. But lets create a new JIRA ticket for this
and we can look at what the community asks for, to add in simple language.
> simple calculations in route
>
>
> Key: CAMEL-4169
> URL: https://issues.apache.org/jira/browse/CAMEL-4169
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Affects Versions: 2.7.2
>Reporter: Marco Westermann
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.9.0
>
>
> create calculation possibilities in simple language. For example to increment
> a header property: ${header.counter}++
> example:
> from("direct:getLastValueFromCache")
> .transform().simple("${header.lastProcessedOrder}++")
> .to("direct:createNewOrderWithNewProcessingNumber");
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-4169) simple calculations in route
[
https://issues.apache.org/jira/browse/CAMEL-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17204111#comment-17204111
]
Luca Ferrari commented on CAMEL-4169:
-
are other math operators tracked in other JIRAs? I feel this is an important
requirement especially if you want to manipulate the payload for quick math
expressions
> simple calculations in route
>
>
> Key: CAMEL-4169
> URL: https://issues.apache.org/jira/browse/CAMEL-4169
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Affects Versions: 2.7.2
>Reporter: Marco Westermann
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.9.0
>
>
> create calculation possibilities in simple language. For example to increment
> a header property: ${header.counter}++
> example:
> from("direct:getLastValueFromCache")
> .transform().simple("${header.lastProcessedOrder}++")
> .to("direct:createNewOrderWithNewProcessingNumber");
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-15594) incorrect bundle.symbolicName in camel-example-servlet-rest-karaf-jaas
[ https://issues.apache.org/jira/browse/CAMEL-15594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang resolved CAMEL-15594. -- Resolution: Fixed > incorrect bundle.symbolicName in camel-example-servlet-rest-karaf-jaas > -- > > Key: CAMEL-15594 > URL: https://issues.apache.org/jira/browse/CAMEL-15594 > Project: Camel > Issue Type: Task > Components: examples, karaf >Affects Versions: 3.5.0, 3.4.4 >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.6.0, 3.4.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15594) incorrect bundle.symbolicName in camel-example-servlet-rest-karaf-jaas
[ https://issues.apache.org/jira/browse/CAMEL-15594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang reassigned CAMEL-15594: Assignee: Freeman Yue Fang > incorrect bundle.symbolicName in camel-example-servlet-rest-karaf-jaas > -- > > Key: CAMEL-15594 > URL: https://issues.apache.org/jira/browse/CAMEL-15594 > Project: Camel > Issue Type: Task > Components: examples, karaf >Affects Versions: 3.5.0, 3.4.4 >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.6.0, 3.4.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15594) incorrect bundle.symbolicName in camel-example-servlet-rest-karaf-jaas
Freeman Yue Fang created CAMEL-15594: Summary: incorrect bundle.symbolicName in camel-example-servlet-rest-karaf-jaas Key: CAMEL-15594 URL: https://issues.apache.org/jira/browse/CAMEL-15594 Project: Camel Issue Type: Task Components: examples, karaf Affects Versions: 3.4.4, 3.5.0 Reporter: Freeman Yue Fang Fix For: 3.6.0, 3.4.5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15593) Camel-cxf: problem with version alignment and hibernate
[ https://issues.apache.org/jira/browse/CAMEL-15593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-15593. - Resolution: Invalid > Camel-cxf: problem with version alignment and hibernate > --- > > Key: CAMEL-15593 > URL: https://issues.apache.org/jira/browse/CAMEL-15593 > Project: Camel > Issue Type: Bug > Components: came-cxf >Affects Versions: 3.5.0 >Reporter: Borodina Valery >Priority: Minor > > I am used camel-cxf(3.5.0) and hibernate in karaf. > camel-cxf 3.5.0 - > cxf 3.4.0 -> woodstox 6.2.1 -> stax2 API 4.2.1 > hubernate -> woodstox 4.4.1 -> stax2 API 3.1.4 > When I try get SessionFactory I get > org/codehaus/stax2/ri/EmptyIterator.getInstance()Lorg/codehaus/stax2/ri/EmptyIterator; > (loaded from jar:bundle://327.0:0/!/ by stax2-api [327]) called from class > com.ctc.wstx.util.EmptyNamespaceContext (loaded from jar:bundle://330.0:0/!/ > by woodstox-core-asl [330]). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15593) Camel-cxf: problem with version alignment and hibernate
[ https://issues.apache.org/jira/browse/CAMEL-15593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203934#comment-17203934 ] Andrea Cosentino commented on CAMEL-15593: -- Use the 3.4.4 release which it's an LTS, for the moment. 3.5.0 is a development release and non LTS. > Camel-cxf: problem with version alignment and hibernate > --- > > Key: CAMEL-15593 > URL: https://issues.apache.org/jira/browse/CAMEL-15593 > Project: Camel > Issue Type: Bug > Components: came-cxf >Affects Versions: 3.5.0 >Reporter: Borodina Valery >Priority: Minor > > I am used camel-cxf(3.5.0) and hibernate in karaf. > camel-cxf 3.5.0 - > cxf 3.4.0 -> woodstox 6.2.1 -> stax2 API 4.2.1 > hubernate -> woodstox 4.4.1 -> stax2 API 3.1.4 > When I try get SessionFactory I get > org/codehaus/stax2/ri/EmptyIterator.getInstance()Lorg/codehaus/stax2/ri/EmptyIterator; > (loaded from jar:bundle://327.0:0/!/ by stax2-api [327]) called from class > com.ctc.wstx.util.EmptyNamespaceContext (loaded from jar:bundle://330.0:0/!/ > by woodstox-core-asl [330]). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15593) Camel-cxf: problem with version alignment and hibernate
[ https://issues.apache.org/jira/browse/CAMEL-15593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203932#comment-17203932 ] Borodina Valery commented on CAMEL-15593: - Before version 3.4 all work, but cxf update to Woodstox 6.2.x (https://issues.apache.org/jira/browse/CXF-8129) > Camel-cxf: problem with version alignment and hibernate > --- > > Key: CAMEL-15593 > URL: https://issues.apache.org/jira/browse/CAMEL-15593 > Project: Camel > Issue Type: Bug > Components: came-cxf >Affects Versions: 3.5.0 >Reporter: Borodina Valery >Priority: Minor > > I am used camel-cxf(3.5.0) and hibernate in karaf. > camel-cxf 3.5.0 - > cxf 3.4.0 -> woodstox 6.2.1 -> stax2 API 4.2.1 > hubernate -> woodstox 4.4.1 -> stax2 API 3.1.4 > When I try get SessionFactory I get > org/codehaus/stax2/ri/EmptyIterator.getInstance()Lorg/codehaus/stax2/ri/EmptyIterator; > (loaded from jar:bundle://327.0:0/!/ by stax2-api [327]) called from class > com.ctc.wstx.util.EmptyNamespaceContext (loaded from jar:bundle://330.0:0/!/ > by woodstox-core-asl [330]). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15593) Camel-cxf: problem with version alignment and hibernate
[ https://issues.apache.org/jira/browse/CAMEL-15593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-15593: - Summary: Camel-cxf: problem with version alignment and hibernate (was: Dependency hell) > Camel-cxf: problem with version alignment and hibernate > --- > > Key: CAMEL-15593 > URL: https://issues.apache.org/jira/browse/CAMEL-15593 > Project: Camel > Issue Type: Bug > Components: came-cxf >Affects Versions: 3.5.0 >Reporter: Borodina Valery >Priority: Minor > > I am used camel-cxf(3.5.0) and hibernate in karaf. > camel-cxf 3.5.0 - > cxf 3.4.0 -> woodstox 6.2.1 -> stax2 API 4.2.1 > hubernate -> woodstox 4.4.1 -> stax2 API 3.1.4 > When I try get SessionFactory I get > org/codehaus/stax2/ri/EmptyIterator.getInstance()Lorg/codehaus/stax2/ri/EmptyIterator; > (loaded from jar:bundle://327.0:0/!/ by stax2-api [327]) called from class > com.ctc.wstx.util.EmptyNamespaceContext (loaded from jar:bundle://330.0:0/!/ > by woodstox-core-asl [330]). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15593) Camel-cxf: problem with version alignment and hibernate
[ https://issues.apache.org/jira/browse/CAMEL-15593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203929#comment-17203929 ] Andrea Cosentino commented on CAMEL-15593: -- Please use a descriptive title. > Camel-cxf: problem with version alignment and hibernate > --- > > Key: CAMEL-15593 > URL: https://issues.apache.org/jira/browse/CAMEL-15593 > Project: Camel > Issue Type: Bug > Components: came-cxf >Affects Versions: 3.5.0 >Reporter: Borodina Valery >Priority: Minor > > I am used camel-cxf(3.5.0) and hibernate in karaf. > camel-cxf 3.5.0 - > cxf 3.4.0 -> woodstox 6.2.1 -> stax2 API 4.2.1 > hubernate -> woodstox 4.4.1 -> stax2 API 3.1.4 > When I try get SessionFactory I get > org/codehaus/stax2/ri/EmptyIterator.getInstance()Lorg/codehaus/stax2/ri/EmptyIterator; > (loaded from jar:bundle://327.0:0/!/ by stax2-api [327]) called from class > com.ctc.wstx.util.EmptyNamespaceContext (loaded from jar:bundle://330.0:0/!/ > by woodstox-core-asl [330]). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15593) Dependency hell
[ https://issues.apache.org/jira/browse/CAMEL-15593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-15593: - Priority: Minor (was: Critical) > Dependency hell > --- > > Key: CAMEL-15593 > URL: https://issues.apache.org/jira/browse/CAMEL-15593 > Project: Camel > Issue Type: Bug > Components: came-cxf >Affects Versions: 3.5.0 >Reporter: Borodina Valery >Priority: Minor > > I am used camel-cxf(3.5.0) and hibernate in karaf. > camel-cxf 3.5.0 - > cxf 3.4.0 -> woodstox 6.2.1 -> stax2 API 4.2.1 > hubernate -> woodstox 4.4.1 -> stax2 API 3.1.4 > When I try get SessionFactory I get > org/codehaus/stax2/ri/EmptyIterator.getInstance()Lorg/codehaus/stax2/ri/EmptyIterator; > (loaded from jar:bundle://327.0:0/!/ by stax2-api [327]) called from class > com.ctc.wstx.util.EmptyNamespaceContext (loaded from jar:bundle://330.0:0/!/ > by woodstox-core-asl [330]). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15593) Dependency hell
Borodina Valery created CAMEL-15593: --- Summary: Dependency hell Key: CAMEL-15593 URL: https://issues.apache.org/jira/browse/CAMEL-15593 Project: Camel Issue Type: Bug Components: came-cxf Affects Versions: 3.5.0 Reporter: Borodina Valery I am used camel-cxf(3.5.0) and hibernate in karaf. camel-cxf 3.5.0 - > cxf 3.4.0 -> woodstox 6.2.1 -> stax2 API 4.2.1 hubernate -> woodstox 4.4.1 -> stax2 API 3.1.4 When I try get SessionFactory I get org/codehaus/stax2/ri/EmptyIterator.getInstance()Lorg/codehaus/stax2/ri/EmptyIterator; (loaded from jar:bundle://327.0:0/!/ by stax2-api [327]) called from class com.ctc.wstx.util.EmptyNamespaceContext (loaded from jar:bundle://330.0:0/!/ by woodstox-core-asl [330]). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15577) Camel-stringtemplate: Misleading and incorrect implementation of parameter 'allowTemplateFromHeader'
[
https://issues.apache.org/jira/browse/CAMEL-15577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-15577.
-
Fix Version/s: 3.6.0
Resolution: Fixed
> Camel-stringtemplate: Misleading and incorrect implementation of parameter
> 'allowTemplateFromHeader'
>
>
> Key: CAMEL-15577
> URL: https://issues.apache.org/jira/browse/CAMEL-15577
> Project: Camel
> Issue Type: Bug
> Components: camel-stringtemplate
>Affects Versions: 3.5.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Major
> Fix For: 3.6.0
>
>
> There is a difference in implementation of parameter
> `*allowTemplateFromHeader*` in various templating components and missing
> implementation in stringtemplate component.
> Description from documentation (of "*allowTemplateFromHeader*"):
> {quote}Whether to allow to use resource template from header or not (default
> false). Enabling this allows to specify dynamic templates via message header.
> However this can be seen as a potential security vulnerability if the header
> is coming from a malicious user, so use this with care.
> {quote}
> Common sense says that with this parameter I can send template via header.
> Which is implemented for example in velocity component (see
> [https://github.com/apache/camel/blob/master/components/camel-velocity/src/main/java/org/apache/camel/component/velocity/VelocityEndpoint.java#L185])
> In stringtemplate component there is only functionality about providing own
> variable map (see
> [https://github.com/apache/camel/blob/master/components/camel-stringtemplate/src/main/java/org/apache/camel/component/stringtemplate/StringTemplateEndpoint.java#L104])
> - the same functionality in velocity is called 'supplementalContext'
> In stringtemplate documentation is a described usage of this custom context
> map:
> {quote}You can define the custom context map by setting the message header
> "*CamelStringTemplateVariableMap*" just like the below code.
> {quote}
> Errors:
> # -parameter "*CamelStringTemplateVariableMap*" is applied only when
> "*allowTemplateFromHeader*" is set to true-
> # there is no way of providing template via header.
>
> Fix should
> # -remove dependency between "*CamelStringTemplateVariableMap*" and
> "*allowTemplateFromHeader*"-
> # -add a new parameter to allow definition of template via header- Fix
> problem with template via header based on other templating components (e.g.
> velocity)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-15592) Broken links for 3.3.0
[ https://issues.apache.org/jira/browse/CAMEL-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-15592: Component/s: website > Broken links for 3.3.0 > -- > > Key: CAMEL-15592 > URL: https://issues.apache.org/jira/browse/CAMEL-15592 > Project: Camel > Issue Type: Task > Components: website >Reporter: Sebb >Priority: Minor > > The links for 3.3.0 are all broken; either remove from the download page or > change the links to point to the archive server. > https://camel.apache.org/download/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15592) Broken links for 3.3.0
[ https://issues.apache.org/jira/browse/CAMEL-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-15592: Priority: Minor (was: Major) > Broken links for 3.3.0 > -- > > Key: CAMEL-15592 > URL: https://issues.apache.org/jira/browse/CAMEL-15592 > Project: Camel > Issue Type: Task >Reporter: Sebb >Priority: Minor > > The links for 3.3.0 are all broken; either remove from the download page or > change the links to point to the archive server. > https://camel.apache.org/download/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15592) Broken links for 3.3.0
[ https://issues.apache.org/jira/browse/CAMEL-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-15592: Issue Type: Task (was: Bug) > Broken links for 3.3.0 > -- > > Key: CAMEL-15592 > URL: https://issues.apache.org/jira/browse/CAMEL-15592 > Project: Camel > Issue Type: Task >Reporter: Sebb >Priority: Major > > The links for 3.3.0 are all broken; either remove from the download page or > change the links to point to the archive server. > https://camel.apache.org/download/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15592) Broken links for 3.3.0
Sebb created CAMEL-15592: Summary: Broken links for 3.3.0 Key: CAMEL-15592 URL: https://issues.apache.org/jira/browse/CAMEL-15592 Project: Camel Issue Type: Bug Reporter: Sebb The links for 3.3.0 are all broken; either remove from the download page or change the links to point to the archive server. https://camel.apache.org/download/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15590) route templates: add an hook to further customize the RouteDefinition computed out of a template
[ https://issues.apache.org/jira/browse/CAMEL-15590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli resolved CAMEL-15590. - Resolution: Fixed > route templates: add an hook to further customize the RouteDefinition > computed out of a template > > > Key: CAMEL-15590 > URL: https://issues.apache.org/jira/browse/CAMEL-15590 > Project: Camel > Issue Type: Improvement > Components: camel-core-engine >Affects Versions: 3.5.0 >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 3.6.0 > > > To have better control over the route template creation process we should add > a consumer to the CamelContext::addRouteFromTemplate that is invoked with the > result of RouteTemplateDefinition::asRouteDefinition to post process the > route generated by the template before it is added to the Camel Context -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-15591) Put a configurable limit on the size of unzipped data using camel-zipfile + camel-tarfile
[ https://issues.apache.org/jira/browse/CAMEL-15591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15591 started by Colm O hEigeartaigh. --- > Put a configurable limit on the size of unzipped data using camel-zipfile + > camel-tarfile > - > > Key: CAMEL-15591 > URL: https://issues.apache.org/jira/browse/CAMEL-15591 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.6.0, 3.4.5 > > > For camel-zipfile + camel-tarfile, there is no limit on the size of > uncompressed data, potentially leading to an OOM Error. Instead we should > have a configurable limit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15591) Put a configurable limit on the size of unzipped data using camel-zipfile + camel-tarfile
Colm O hEigeartaigh created CAMEL-15591: --- Summary: Put a configurable limit on the size of unzipped data using camel-zipfile + camel-tarfile Key: CAMEL-15591 URL: https://issues.apache.org/jira/browse/CAMEL-15591 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.6.0, 3.4.5 For camel-zipfile + camel-tarfile, there is no limit on the size of uncompressed data, potentially leading to an OOM Error. Instead we should have a configurable limit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15585) Camel-health - small refactor
[ https://issues.apache.org/jira/browse/CAMEL-15585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-15585. - Fix Version/s: 3.6.0 Resolution: Fixed > Camel-health - small refactor > - > > Key: CAMEL-15585 > URL: https://issues.apache.org/jira/browse/CAMEL-15585 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Djordje Bajic >Priority: Minor > Fix For: 3.6.0 > > > Hello! > I found some small things that can be refactored. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15589) EhCache Exception on startup when using Apache Camel
[
https://issues.apache.org/jira/browse/CAMEL-15589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-15589.
-
Resolution: Information Provided
Camel 2.x is EOL and this is just a WARN and not an error.
Camel 3 does not do the update check, and is using a newer version where they
dont do this anymore.
> EhCache Exception on startup when using Apache Camel
>
>
> Key: CAMEL-15589
> URL: https://issues.apache.org/jira/browse/CAMEL-15589
> Project: Camel
> Issue Type: Bug
> Components: camel-cache
>Affects Versions: 2.24.3
>Reporter: Sreejesh
>Priority: Minor
> Attachments: camel-cache-test-master.zip
>
>
> I was trying to use EhCache with Apache Camel using Sprin Boot. While it
> works as expected. there is an exception on startup. It does not cause any
> issues in the functionality I guess (according to my test, everything works
> as expected). But is there any way to avoid that exception?
> {{}}
>
> 2020-09-28 23:46:38,397 [main][DEBUG]
> org.apache.camel.component.cache.CacheManagerFactory - Turning off EHCache
> update checker ...
> 2020-09-28 23:46:38,400 [main][WARN ]
> org.apache.camel.component.cache.CacheManagerFactory - Error turning off
> EHCache update checker. Beware information sent over the internet!
> java.lang.NoSuchFieldException: updateCheck
> at java.base/java.lang.Class.getDeclaredField(Class.java:2411)
> at
> org.apache.camel.component.cache.CacheManagerFactory.getInstance(CacheManagerFactory.java:40)
> at
> org.apache.camel.component.cache.CacheEndpoint.initializeCache(CacheEndpoint.java:120)
> at
> org.apache.camel.component.cache.CacheProducer.doStart(CacheProducer.java:45)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:72
>
> My EhCache Configuration XML:
>
>
> {{http://www.w3.org/2001/XMLSchema-instance;
> xsi:noNamespaceSchemaLocation="ehcache.xsd" updateCheck="false"
> monitoring="autodetect" dynamicConfig="true">
> maxEntriesLocalHeap="1"
> maxEntriesLocalDisk="1000"
> eternal="false"
> diskSpoolBufferSizeMB="20"
> timeToIdleSeconds="300" timeToLiveSeconds="600"
> memoryStoreEvictionPolicy="LFU"
> transactionalMode="off">
>
>
> }}
>
> I have tried to set the updateCheck as false, no luck. I even tried to remove
> the updateCheck field itself from the XML, even that did not help (though it
> started fine with the same exception).
> Thanks for your time.
> I have uploaded sample code to test.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14542) camel-core - Optimize simple language
[ https://issues.apache.org/jira/browse/CAMEL-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14542. - Resolution: Fixed > camel-core - Optimize simple language > - > > Key: CAMEL-14542 > URL: https://issues.apache.org/jira/browse/CAMEL-14542 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.6.0 > > > There are potentially some improvements we can for simple language. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15577) Camel-stringtemplate: Misleading and incorrect implementation of parameter 'allowTemplateFromHeader'
[
https://issues.apache.org/jira/browse/CAMEL-15577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Ondrusek updated CAMEL-15577:
--
Description:
There is a difference in implementation of parameter
`*allowTemplateFromHeader*` in various templating components and missing
implementation in stringtemplate component.
Description from documentation (of "*allowTemplateFromHeader*"):
{quote}Whether to allow to use resource template from header or not (default
false). Enabling this allows to specify dynamic templates via message header.
However this can be seen as a potential security vulnerability if the header is
coming from a malicious user, so use this with care.
{quote}
Common sense says that with this parameter I can send template via header.
Which is implemented for example in velocity component (see
[https://github.com/apache/camel/blob/master/components/camel-velocity/src/main/java/org/apache/camel/component/velocity/VelocityEndpoint.java#L185])
In stringtemplate component there is only functionality about providing own
variable map (see
[https://github.com/apache/camel/blob/master/components/camel-stringtemplate/src/main/java/org/apache/camel/component/stringtemplate/StringTemplateEndpoint.java#L104])
- the same functionality in velocity is called 'supplementalContext'
In stringtemplate documentation is a described usage of this custom context
map:
{quote}You can define the custom context map by setting the message header
"*CamelStringTemplateVariableMap*" just like the below code.
{quote}
Errors:
# -parameter "*CamelStringTemplateVariableMap*" is applied only when
"*allowTemplateFromHeader*" is set to true-
# there is no way of providing template via header.
Fix should
# -remove dependency between "*CamelStringTemplateVariableMap*" and
"*allowTemplateFromHeader*"-
# -add a new parameter to allow definition of template via header- Fix
problem with template via header based on other templating components (e.g.
velocity)
was:
There is a difference in implementation of parameter
`*allowTemplateFromHeader*` in various templating components and missing
implementation in stringtemplate component.
Description from documentation (of "*allowTemplateFromHeader*"):
{quote}Whether to allow to use resource template from header or not (default
false). Enabling this allows to specify dynamic templates via message header.
However this can be seen as a potential security vulnerability if the header is
coming from a malicious user, so use this with care.
{quote}
Common sense says that with this parameter I can send template via header.
Which is implemented for example in velocity component (see
[https://github.com/apache/camel/blob/master/components/camel-velocity/src/main/java/org/apache/camel/component/velocity/VelocityEndpoint.java#L185])
In stringtemplate component there is only functionality about providing own
variable map (see
[https://github.com/apache/camel/blob/master/components/camel-stringtemplate/src/main/java/org/apache/camel/component/stringtemplate/StringTemplateEndpoint.java#L104])
- the same functionality in velocity is called 'supplementalContext'
In stringtemplate documentation is a described usage of this custom context
map:
{quote}You can define the custom context map by setting the message header
"*CamelStringTemplateVariableMap*" just like the below code.
{quote}
Errors:
# -parameter "*CamelStringTemplateVariableMap*" is applied only when
"*allowTemplateFromHeader*" is set to true-
# there is no way of providing template via header.
Fix should
# r-emove dependency between "*CamelStringTemplateVariableMap*" and
"*allowTemplateFromHeader*"-
# -add a new parameter to allow definition of template via header- Fix
problem with template via header based on other templating components (e.g.
velocity)
> Camel-stringtemplate: Misleading and incorrect implementation of parameter
> 'allowTemplateFromHeader'
>
>
> Key: CAMEL-15577
> URL: https://issues.apache.org/jira/browse/CAMEL-15577
> Project: Camel
> Issue Type: Bug
> Components: camel-stringtemplate
>Affects Versions: 3.5.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Major
>
> There is a difference in implementation of parameter
> `*allowTemplateFromHeader*` in various templating components and missing
> implementation in stringtemplate component.
> Description from documentation (of "*allowTemplateFromHeader*"):
> {quote}Whether to allow to use resource template from header or not (default
> false). Enabling this allows to specify dynamic templates via message header.
> However this can be seen as a potential security vulnerability if the header
> is coming from a malicious user, so use
[jira] [Updated] (CAMEL-15577) Camel-stringtemplate: Misleading and incorrect implementation of parameter 'allowTemplateFromHeader'
[
https://issues.apache.org/jira/browse/CAMEL-15577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Ondrusek updated CAMEL-15577:
--
Description:
There is a difference in implementation of parameter
`*allowTemplateFromHeader*` in various templating components and missing
implementation in stringtemplate component.
Description from documentation (of "*allowTemplateFromHeader*"):
{quote}Whether to allow to use resource template from header or not (default
false). Enabling this allows to specify dynamic templates via message header.
However this can be seen as a potential security vulnerability if the header is
coming from a malicious user, so use this with care.
{quote}
Common sense says that with this parameter I can send template via header.
Which is implemented for example in velocity component (see
[https://github.com/apache/camel/blob/master/components/camel-velocity/src/main/java/org/apache/camel/component/velocity/VelocityEndpoint.java#L185])
In stringtemplate component there is only functionality about providing own
variable map (see
[https://github.com/apache/camel/blob/master/components/camel-stringtemplate/src/main/java/org/apache/camel/component/stringtemplate/StringTemplateEndpoint.java#L104])
- the same functionality in velocity is called 'supplementalContext'
In stringtemplate documentation is a described usage of this custom context
map:
{quote}You can define the custom context map by setting the message header
"*CamelStringTemplateVariableMap*" just like the below code.
{quote}
Errors:
# -parameter "*CamelStringTemplateVariableMap*" is applied only when
"*allowTemplateFromHeader*" is set to true-
# there is no way of providing template via header.
Fix should
# r-emove dependency between "*CamelStringTemplateVariableMap*" and
"*allowTemplateFromHeader*"-
# -add a new parameter to allow definition of template via header- Fix
problem with template via header based on other templating components (e.g.
velocity)
was:
There is a difference in implementation of parameter
`*allowTemplateFromHeader*` in various templating components and missing
implementation in stringtemplate component.
Description from documentation (of "*allowTemplateFromHeader*"):
{quote}Whether to allow to use resource template from header or not (default
false). Enabling this allows to specify dynamic templates via message header.
However this can be seen as a potential security vulnerability if the header is
coming from a malicious user, so use this with care.
{quote}
Common sense says that with this parameter I can send template via header.
Which is implemented for example in velocity component (see
[https://github.com/apache/camel/blob/master/components/camel-velocity/src/main/java/org/apache/camel/component/velocity/VelocityEndpoint.java#L185])
In stringtemplate component there is only functionality about providing own
variable map (see
[https://github.com/apache/camel/blob/master/components/camel-stringtemplate/src/main/java/org/apache/camel/component/stringtemplate/StringTemplateEndpoint.java#L104])
- the same functionality in velocity is called 'supplementalContext'
In stringtemplate documentation is a described usage of this custom context
map:
{quote}You can define the custom context map by setting the message header
"*CamelStringTemplateVariableMap*" just like the below code.
{quote}
Errors:
# parameter "*CamelStringTemplateVariableMap*" is applied only when
"*allowTemplateFromHeader*" is set to true
# there is no way of providing template via header.
Fix should
# remove dependency between "*CamelStringTemplateVariableMap*" and
"*allowTemplateFromHeader*"
# add a new parameter to allow definition of template via header
> Camel-stringtemplate: Misleading and incorrect implementation of parameter
> 'allowTemplateFromHeader'
>
>
> Key: CAMEL-15577
> URL: https://issues.apache.org/jira/browse/CAMEL-15577
> Project: Camel
> Issue Type: Bug
> Components: camel-stringtemplate
>Affects Versions: 3.5.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Major
>
> There is a difference in implementation of parameter
> `*allowTemplateFromHeader*` in various templating components and missing
> implementation in stringtemplate component.
> Description from documentation (of "*allowTemplateFromHeader*"):
> {quote}Whether to allow to use resource template from header or not (default
> false). Enabling this allows to specify dynamic templates via message header.
> However this can be seen as a potential security vulnerability if the header
> is coming from a malicious user, so use this with care.
> {quote}
> Common sense says that with this parameter I can send template via
[jira] [Comment Edited] (CAMEL-14542) camel-core - Optimize simple language
[ https://issues.apache.org/jira/browse/CAMEL-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203725#comment-17203725 ] Claus Ibsen edited comment on CAMEL-14542 at 9/29/20, 8:40 AM: --- Optimize when comparing numeric values to favour using existing type as-is, eg if right side is integer, instead of using long comparision first. *DONE* was (Author: davsclaus): Optimize when comparing numeric values to favour using existing type as-is, eg if right side is integer, instead of using long comparision first. > camel-core - Optimize simple language > - > > Key: CAMEL-14542 > URL: https://issues.apache.org/jira/browse/CAMEL-14542 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.6.0 > > > There are potentially some improvements we can for simple language. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15590) route templates: add an hook to further customize the RouteDefinition computed out of a template
[ https://issues.apache.org/jira/browse/CAMEL-15590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-15590: --- Assignee: Luca Burgazzoli > route templates: add an hook to further customize the RouteDefinition > computed out of a template > > > Key: CAMEL-15590 > URL: https://issues.apache.org/jira/browse/CAMEL-15590 > Project: Camel > Issue Type: Improvement > Components: camel-core-engine >Affects Versions: 3.5.0 >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 3.6.0 > > > To have better control over the route template creation process we should add > a consumer to the CamelContext::addRouteFromTemplate that is invoked with the > result of RouteTemplateDefinition::asRouteDefinition to post process the > route generated by the template before it is added to the Camel Context -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15590) route templates: add an hook to further customize the RouteDefinition computed out of a template
Luca Burgazzoli created CAMEL-15590: --- Summary: route templates: add an hook to further customize the RouteDefinition computed out of a template Key: CAMEL-15590 URL: https://issues.apache.org/jira/browse/CAMEL-15590 Project: Camel Issue Type: Improvement Components: camel-core-engine Affects Versions: 3.5.0 Reporter: Luca Burgazzoli Fix For: 3.6.0 To have better control over the route template creation process we should add a consumer to the CamelContext::addRouteFromTemplate that is invoked with the result of RouteTemplateDefinition::asRouteDefinition to post process the route generated by the template before it is added to the Camel Context -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14542) camel-core - Optimize simple language
[ https://issues.apache.org/jira/browse/CAMEL-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203725#comment-17203725 ] Claus Ibsen commented on CAMEL-14542: - Optimize when comparing numeric values to favour using existing type as-is, eg if right side is integer, instead of using long comparision first. > camel-core - Optimize simple language > - > > Key: CAMEL-14542 > URL: https://issues.apache.org/jira/browse/CAMEL-14542 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.6.0 > > > There are potentially some improvements we can for simple language. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14542) camel-core - Optimize simple language
[ https://issues.apache.org/jira/browse/CAMEL-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203501#comment-17203501 ] Claus Ibsen edited comment on CAMEL-14542 at 9/29/20, 6:49 AM: --- Optimize simple for numeric values which we can avoid some type conversions, and also make the binary operator more natural when working with numeric types vs string texts *DONE* was (Author: davsclaus): Optimize simple for numeric values which we can avoid some type conversions, and also make the binary operator more natural when working with numeric types vs string texts > camel-core - Optimize simple language > - > > Key: CAMEL-14542 > URL: https://issues.apache.org/jira/browse/CAMEL-14542 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.6.0 > > > There are potentially some improvements we can for simple language. -- This message was sent by Atlassian Jira (v8.3.4#803005)
