[jira] [Updated] (CAMEL-19006) XML IO DSL do not load templatedRoutes without XML namespace
[
https://issues.apache.org/jira/browse/CAMEL-19006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Turek updated CAMEL-19006:
Affects Version/s: 3.18.3
(was: 2.18.3)
> XML IO DSL do not load templatedRoutes without XML namespace
>
>
> Key: CAMEL-19006
> URL: https://issues.apache.org/jira/browse/CAMEL-19006
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.18.3
>Reporter: Tomas Turek
>Priority: Major
>
> XML IO DSL do not load templatedRoutes without XML namespace like this:
> {code}
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19006) XML IO DSL do not load templatedRoutes without XML namespace
Tomas Turek created CAMEL-19006:
---
Summary: XML IO DSL do not load templatedRoutes without XML
namespace
Key: CAMEL-19006
URL: https://issues.apache.org/jira/browse/CAMEL-19006
Project: Camel
Issue Type: Bug
Affects Versions: 2.18.3
Reporter: Tomas Turek
XML IO DSL do not load templatedRoutes without XML namespace like this:
{code}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19004) XML IO DSL do not parse route configuration with XML namespace
[
https://issues.apache.org/jira/browse/CAMEL-19004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683835#comment-17683835
]
Tomas Turek commented on CAMEL-19004:
-
https://github.com/apache/camel/pull/9293 should fix it
> XML IO DSL do not parse route configuration with XML namespace
> --
>
> Key: CAMEL-19004
> URL: https://issues.apache.org/jira/browse/CAMEL-19004
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.18.3
>Reporter: Tomas Turek
>Priority: Major
>
> XML IO DSL do not load {{routeConfiguration}} if it uses XML namespace like
> this:
> {code}
> http://camel.apache.org/schema/spring;>
>
> java.lang.Exception
> true
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19004) XML IO DSL do not parse route configuration with XML namespace
[
https://issues.apache.org/jira/browse/CAMEL-19004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683834#comment-17683834
]
Tomas Turek commented on CAMEL-19004:
-
I tried it agains main branch too.
> XML IO DSL do not parse route configuration with XML namespace
> --
>
> Key: CAMEL-19004
> URL: https://issues.apache.org/jira/browse/CAMEL-19004
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.18.3
>Reporter: Tomas Turek
>Priority: Major
>
> XML IO DSL do not load {{routeConfiguration}} if it uses XML namespace like
> this:
> {code}
> http://camel.apache.org/schema/spring;>
>
> java.lang.Exception
> true
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19004) XML IO DSL do not parse route configuration with XML namespace
[
https://issues.apache.org/jira/browse/CAMEL-19004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683831#comment-17683831
]
Tomas Turek commented on CAMEL-19004:
-
Hi I am using 3.18.3 version.
> XML IO DSL do not parse route configuration with XML namespace
> --
>
> Key: CAMEL-19004
> URL: https://issues.apache.org/jira/browse/CAMEL-19004
> Project: Camel
> Issue Type: Bug
>Reporter: Tomas Turek
>Priority: Major
>
> XML IO DSL do not load {{routeConfiguration}} if it uses XML namespace like
> this:
> {code}
> http://camel.apache.org/schema/spring;>
>
> java.lang.Exception
> true
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19004) XML IO DSL do not parse route configuration with XML namespace
Tomas Turek created CAMEL-19004:
---
Summary: XML IO DSL do not parse route configuration with XML
namespace
Key: CAMEL-19004
URL: https://issues.apache.org/jira/browse/CAMEL-19004
Project: Camel
Issue Type: Bug
Reporter: Tomas Turek
XML IO DSL do not load {{routeConfiguration}} if it uses XML namespace like
this:
{code}
http://camel.apache.org/schema/spring;>
java.lang.Exception
true
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-12436) camel-undertow - should extract body message from PATCH request
[ https://issues.apache.org/jira/browse/CAMEL-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Turek updated CAMEL-12436: Summary: camel-undertow - should extract body message from PATCH request (was: camel-undertow - should extract body massage from PATCH request) > camel-undertow - should extract body message from PATCH request > --- > > Key: CAMEL-12436 > URL: https://issues.apache.org/jira/browse/CAMEL-12436 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Affects Versions: 2.21.0 >Reporter: Tomas Turek >Priority: Major > > Undertow component should process body message of HTTP PATCH request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12436) camel-undertow - should extract body massage from PATCH request
Tomas Turek created CAMEL-12436: --- Summary: camel-undertow - should extract body massage from PATCH request Key: CAMEL-12436 URL: https://issues.apache.org/jira/browse/CAMEL-12436 Project: Camel Issue Type: Bug Components: camel-undertow Affects Versions: 2.21.0 Reporter: Tomas Turek Undertow component should process body message of HTTP PATCH request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-10453) camel-elsql does not set CamelSqlUpdateCount header on update operation
[
https://issues.apache.org/jira/browse/CAMEL-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650570#comment-15650570
]
Tomas Turek commented on CAMEL-10453:
-
This problem exists only in the camel-elsql component because this component
does not reuse {{SqlProducer}} to implement {{ElSqlProducer}}. Which should be
a source of the problem because I discover another bug in {{ElSqlProducer}}
[CAMEL-10459|https://issues.apache.org/jira/browse/CAMEL-10459].
> camel-elsql does not set CamelSqlUpdateCount header on update operation
> ---
>
> Key: CAMEL-10453
> URL: https://issues.apache.org/jira/browse/CAMEL-10453
> Project: Camel
> Issue Type: Bug
> Components: camel-elsql
>Affects Versions: 2.18.0
>Reporter: Tomas Turek
>Priority: Minor
> Fix For: 2.18.1, 2.19.0
>
>
> Camel ElSql should store number of rows updated for update operation into
> CamelSqlUpdateCount header.
> Route:
> {code}
>
>
>
>
>
> {code}
> ElSQL
> {code}
> @NAME(updateLicense)
> UPDATE projects
> SET license = :lic
> WHERE id = :id
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-10459) camel-elsql - option batch is not implemented in producer
Tomas Turek created CAMEL-10459:
---
Summary: camel-elsql - option batch is not implemented in producer
Key: CAMEL-10459
URL: https://issues.apache.org/jira/browse/CAMEL-10459
Project: Camel
Issue Type: Bug
Components: camel-elsql
Affects Versions: 2.18.0
Reporter: Tomas Turek
Option {{batch}} which should enable support for SQL batch update statements is
not working.
Route:
{code}
{code}
ElSql:
{code}
@NAME(insert)
INSERT INTO projects (id, project, license)
VALUES (:id, :project, :license)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-10453) camel-elsql does not set CamelSqlUpdateCount header on update operation
[
https://issues.apache.org/jira/browse/CAMEL-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Turek updated CAMEL-10453:
Description:
Camel ElSql should store number of rows updated for update operation into
CamelSqlUpdateCount header.
Route:
{code}
{code}
ElSQL
{code}
@NAME(updateLicense)
UPDATE projects
SET license = :lic
WHERE id = :id
{code}
> camel-elsql does not set CamelSqlUpdateCount header on update operation
> ---
>
> Key: CAMEL-10453
> URL: https://issues.apache.org/jira/browse/CAMEL-10453
> Project: Camel
> Issue Type: Bug
> Components: camel-elsql
>Affects Versions: 2.18.0
>Reporter: Tomas Turek
>
> Camel ElSql should store number of rows updated for update operation into
> CamelSqlUpdateCount header.
> Route:
> {code}
>
>
>
>
>
> {code}
> ElSQL
> {code}
> @NAME(updateLicense)
> UPDATE projects
> SET license = :lic
> WHERE id = :id
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-10453) camel-elsql does not set CamelSqlUpdateCount header on update operation
Tomas Turek created CAMEL-10453: --- Summary: camel-elsql does not set CamelSqlUpdateCount header on update operation Key: CAMEL-10453 URL: https://issues.apache.org/jira/browse/CAMEL-10453 Project: Camel Issue Type: Bug Components: camel-elsql Affects Versions: 2.18.0 Reporter: Tomas Turek -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10431) camel-elsql - Does not read named parameter from header properties
Tomas Turek created CAMEL-10431:
---
Summary: camel-elsql - Does not read named parameter from header
properties
Key: CAMEL-10431
URL: https://issues.apache.org/jira/browse/CAMEL-10431
Project: Camel
Issue Type: Bug
Components: camel-elsql
Affects Versions: 2.18.0
Reporter: Tomas Turek
Camel-elsql could not lookup for parameters from message headers. Problem is
here
https://github.com/apache/camel/blob/camel-2.18.0/components/camel-elsql/src/main/java/org/apache/camel/component/elsql/ElsqlSqlMapSource.java#L70
Sample route:
{code}
from("direct:projects")
.setHeader("lic", constant("ASF"))
.setHeader("min", constant(123))
.to("elsql:projects:com/foo/projects.elsql")
{code}
ElSql:
{code}
@NAME(projects)
SELECT *
FROM projects
WHERE license = :lic AND id > :min
ORDER BY id
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-9042) Incorrect default value in a documentation of camel-atom
Tomas Turek created CAMEL-9042:
--
Summary: Incorrect default value in a documentation of camel-atom
Key: CAMEL-9042
URL: https://issues.apache.org/jira/browse/CAMEL-9042
Project: Camel
Issue Type: Bug
Components: documentation
Affects Versions: 2.15.2
Reporter: Tomas Turek
Option {{consumer.delay}} in documentaion of
[camel-atom|https://camel.apache.org/atom.html] has incorrect default value
{{6}} but correct value is {{500}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-7659) camel-atom filter always returns the last consumed entry from feed more than once
[ https://issues.apache.org/jira/browse/CAMEL-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Turek updated CAMEL-7659: --- Description: I have problem with camel setup to consume feeds atom://atomUri?splitEntries=truefilter=truethrottleEntries=false, feed processor does not skip last consumed entry. The source of problem is in UpdateDateFilter class, it filters only entries older than last update and entries of same pubdate are once more consumed. was: I have problem with camel setup to consume feeds atom://atimUri?splitEntries=truefilter=true, feed processor does not skip last consumed entry. The source of problem is in UpdateDateFilter class, it filters only entries older than last update and entries of same pubdate are once more consumed. camel-atom filter always returns the last consumed entry from feed more than once - Key: CAMEL-7659 URL: https://issues.apache.org/jira/browse/CAMEL-7659 Project: Camel Issue Type: Bug Components: camel-atom Reporter: Tomas Turek I have problem with camel setup to consume feeds atom://atomUri?splitEntries=truefilter=truethrottleEntries=false, feed processor does not skip last consumed entry. The source of problem is in UpdateDateFilter class, it filters only entries older than last update and entries of same pubdate are once more consumed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7659) camel-atom filter always returns the last consumed entry from feed more than once
Tomas Turek created CAMEL-7659: -- Summary: camel-atom filter always returns the last consumed entry from feed more than once Key: CAMEL-7659 URL: https://issues.apache.org/jira/browse/CAMEL-7659 Project: Camel Issue Type: Bug Components: camel-atom Reporter: Tomas Turek I have problem with camel setup to consume feeds atom://atimUri?splitEntries=truefilter=true, feed processor does not skip last consumed entry. The source of problem is in UpdateDateFilter class, it filters only entries older than last update and entries of same pubdate are once more consumed. -- This message was sent by Atlassian JIRA (v6.2#6252)
