[jira] [Commented] (CAMEL-13954) Generated property configurator is using wrong method on endpoint (camel-file-watch component)
[
https://issues.apache.org/jira/browse/CAMEL-13954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924557#comment-16924557
]
Edem Tiassou commented on CAMEL-13954:
--
Right ! Good to know. Thanks for the quick update
> Generated property configurator is using wrong method on endpoint
> (camel-file-watch component)
> --
>
> Key: CAMEL-13954
> URL: https://issues.apache.org/jira/browse/CAMEL-13954
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.0.0.RC1
>Reporter: Edem Tiassou
>Priority: Major
> Fix For: 3.0.0, 3.0.0.RC2
>
>
> Hi, I'am very new at Camel and I've being trying to use the component
> camel-file-watch (version:3.0.0-RC1).
> When I set thing up with spring-boot, it does not seem to dectect file
> systems events.
> With a little investigation, I found that the property conversion of events
> from the uri scheme (file-watch://some-directory?events=DELETE,CREATE) to the
> endpoint is calling
> (FileWatchEndpoint.java)
> public void setEvents(Set events) {
> this.events = events;
> }
> Instead of
> (FileWatchEndpoint.java)
> @SuppressWarnings("unused") //called via reflection
> public void setEvents(String commaSeparatedEvents) {
> String[] stringArray = commaSeparatedEvents.split(",");
> Set eventsSet = new HashSet<>();
> for (String event : stringArray) {
> eventsSet.add(FileEventEnum.valueOf(event.trim()));
> }
> events = eventsSet.isEmpty() ? new
> HashSet<>(Arrays.asList(FileEventEnum.values())) : eventsSet;
> }
> (FileWatchEndpoint.java) events object declaration
> @UriParam(label = "consumer",
> enums = "CREATE,MODIFY,DELETE",
> description = "Comma separated list of events to watch.",
> defaultValue = "CREATE,MODIFY,DELETE")
> private Set events = new
> HashSet<>(Arrays.asList(FileEventEnum.values()));
> Basically the conversion from String to Set fails and the
> component is calling the first method listed above with Set instead
> of Set
> I got it to work by adding a converter from String to Set but
> I feel like this should have been taken care of by the component.
> Let me know what you think
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13954) Generated property configurator is using wrong method on endpoint (camel-file-watch component)
[
https://issues.apache.org/jira/browse/CAMEL-13954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924553#comment-16924553
]
Claus Ibsen commented on CAMEL-13954:
-
Use a string type to set the events that can support comma separation values.
This works the best also with tooling and configuration from sprig boot etc
> Generated property configurator is using wrong method on endpoint
> (camel-file-watch component)
> --
>
> Key: CAMEL-13954
> URL: https://issues.apache.org/jira/browse/CAMEL-13954
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.0.0.RC1
>Reporter: Edem Tiassou
>Priority: Major
> Fix For: 3.0.0, 3.0.0.RC2
>
>
> Hi, I'am very new at Camel and I've being trying to use the component
> camel-file-watch (version:3.0.0-RC1).
> When I set thing up with spring-boot, it does not seem to dectect file
> systems events.
> With a little investigation, I found that the property conversion of events
> from the uri scheme (file-watch://some-directory?events=DELETE,CREATE) to the
> endpoint is calling
> (FileWatchEndpoint.java)
> public void setEvents(Set events) {
> this.events = events;
> }
> Instead of
> (FileWatchEndpoint.java)
> @SuppressWarnings("unused") //called via reflection
> public void setEvents(String commaSeparatedEvents) {
> String[] stringArray = commaSeparatedEvents.split(",");
> Set eventsSet = new HashSet<>();
> for (String event : stringArray) {
> eventsSet.add(FileEventEnum.valueOf(event.trim()));
> }
> events = eventsSet.isEmpty() ? new
> HashSet<>(Arrays.asList(FileEventEnum.values())) : eventsSet;
> }
> (FileWatchEndpoint.java) events object declaration
> @UriParam(label = "consumer",
> enums = "CREATE,MODIFY,DELETE",
> description = "Comma separated list of events to watch.",
> defaultValue = "CREATE,MODIFY,DELETE")
> private Set events = new
> HashSet<>(Arrays.asList(FileEventEnum.values()));
> Basically the conversion from String to Set fails and the
> component is calling the first method listed above with Set instead
> of Set
> I got it to work by adding a converter from String to Set but
> I feel like this should have been taken care of by the component.
> Let me know what you think
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13954) Generated property configurator is using wrong method on endpoint (camel-file-watch component)
[
https://issues.apache.org/jira/browse/CAMEL-13954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13954:
Fix Version/s: 3.0.0.RC2
3.0.0
> Generated property configurator is using wrong method on endpoint
> (camel-file-watch component)
> --
>
> Key: CAMEL-13954
> URL: https://issues.apache.org/jira/browse/CAMEL-13954
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.0.0.RC1
>Reporter: Edem Tiassou
>Priority: Major
> Fix For: 3.0.0, 3.0.0.RC2
>
>
> Hi, I'am very new at Camel and I've being trying to use the component
> camel-file-watch (version:3.0.0-RC1).
> When I set thing up with spring-boot, it does not seem to dectect file
> systems events.
> With a little investigation, I found that the property conversion of events
> from the uri scheme (file-watch://some-directory?events=DELETE,CREATE) to the
> endpoint is calling
> (FileWatchEndpoint.java)
> public void setEvents(Set events) {
> this.events = events;
> }
> Instead of
> (FileWatchEndpoint.java)
> @SuppressWarnings("unused") //called via reflection
> public void setEvents(String commaSeparatedEvents) {
> String[] stringArray = commaSeparatedEvents.split(",");
> Set eventsSet = new HashSet<>();
> for (String event : stringArray) {
> eventsSet.add(FileEventEnum.valueOf(event.trim()));
> }
> events = eventsSet.isEmpty() ? new
> HashSet<>(Arrays.asList(FileEventEnum.values())) : eventsSet;
> }
> (FileWatchEndpoint.java) events object declaration
> @UriParam(label = "consumer",
> enums = "CREATE,MODIFY,DELETE",
> description = "Comma separated list of events to watch.",
> defaultValue = "CREATE,MODIFY,DELETE")
> private Set events = new
> HashSet<>(Arrays.asList(FileEventEnum.values()));
> Basically the conversion from String to Set fails and the
> component is calling the first method listed above with Set instead
> of Set
> I got it to work by adding a converter from String to Set but
> I feel like this should have been taken care of by the component.
> Let me know what you think
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13954) Generated property configurator is using wrong method on endpoint (camel-file-watch component)
[
https://issues.apache.org/jira/browse/CAMEL-13954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924552#comment-16924552
]
Claus Ibsen commented on CAMEL-13954:
-
Yeah it should be fixed in the component, we have done it for others which had
a similar issue.
> Generated property configurator is using wrong method on endpoint
> (camel-file-watch component)
> --
>
> Key: CAMEL-13954
> URL: https://issues.apache.org/jira/browse/CAMEL-13954
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.0.0.RC1
>Reporter: Edem Tiassou
>Priority: Major
>
> Hi, I'am very new at Camel and I've being trying to use the component
> camel-file-watch (version:3.0.0-RC1).
> When I set thing up with spring-boot, it does not seem to dectect file
> systems events.
> With a little investigation, I found that the property conversion of events
> from the uri scheme (file-watch://some-directory?events=DELETE,CREATE) to the
> endpoint is calling
> (FileWatchEndpoint.java)
> public void setEvents(Set events) {
> this.events = events;
> }
> Instead of
> (FileWatchEndpoint.java)
> @SuppressWarnings("unused") //called via reflection
> public void setEvents(String commaSeparatedEvents) {
> String[] stringArray = commaSeparatedEvents.split(",");
> Set eventsSet = new HashSet<>();
> for (String event : stringArray) {
> eventsSet.add(FileEventEnum.valueOf(event.trim()));
> }
> events = eventsSet.isEmpty() ? new
> HashSet<>(Arrays.asList(FileEventEnum.values())) : eventsSet;
> }
> (FileWatchEndpoint.java) events object declaration
> @UriParam(label = "consumer",
> enums = "CREATE,MODIFY,DELETE",
> description = "Comma separated list of events to watch.",
> defaultValue = "CREATE,MODIFY,DELETE")
> private Set events = new
> HashSet<>(Arrays.asList(FileEventEnum.values()));
> Basically the conversion from String to Set fails and the
> component is calling the first method listed above with Set instead
> of Set
> I got it to work by adding a converter from String to Set but
> I feel like this should have been taken care of by the component.
> Let me know what you think
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (CAMEL-13954) Generated property configurator is using wrong method on endpoint (camel-file-watch component)
Edem Tiassou created CAMEL-13954:
Summary: Generated property configurator is using wrong method on
endpoint (camel-file-watch component)
Key: CAMEL-13954
URL: https://issues.apache.org/jira/browse/CAMEL-13954
Project: Camel
Issue Type: Bug
Affects Versions: 3.0.0.RC1
Reporter: Edem Tiassou
Hi, I'am very new at Camel and I've being trying to use the component
camel-file-watch (version:3.0.0-RC1).
When I set thing up with spring-boot, it does not seem to dectect file systems
events.
With a little investigation, I found that the property conversion of events
from the uri scheme (file-watch://some-directory?events=DELETE,CREATE) to the
endpoint is calling
(FileWatchEndpoint.java)
public void setEvents(Set events) {
this.events = events;
}
Instead of
(FileWatchEndpoint.java)
@SuppressWarnings("unused") //called via reflection
public void setEvents(String commaSeparatedEvents) {
String[] stringArray = commaSeparatedEvents.split(",");
Set eventsSet = new HashSet<>();
for (String event : stringArray) {
eventsSet.add(FileEventEnum.valueOf(event.trim()));
}
events = eventsSet.isEmpty() ? new
HashSet<>(Arrays.asList(FileEventEnum.values())) : eventsSet;
}
(FileWatchEndpoint.java) events object declaration
@UriParam(label = "consumer",
enums = "CREATE,MODIFY,DELETE",
description = "Comma separated list of events to watch.",
defaultValue = "CREATE,MODIFY,DELETE")
private Set events = new
HashSet<>(Arrays.asList(FileEventEnum.values()));
Basically the conversion from String to Set fails and the
component is calling the first method listed above with Set instead of
Set
I got it to work by adding a converter from String to Set but I
feel like this should have been taken care of by the component.
Let me know what you think
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13931) camel-file - tempFileName directory is not auto-created if it is relative before the endpoint path
[
https://issues.apache.org/jira/browse/CAMEL-13931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924529#comment-16924529
]
Dimitri Kotlovsky commented on CAMEL-13931:
---
Appreciate it. Thanks for the quick response and straightforward collaboration
=)
> camel-file - tempFileName directory is not auto-created if it is relative
> before the endpoint path
> --
>
> Key: CAMEL-13931
> URL: https://issues.apache.org/jira/browse/CAMEL-13931
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.23.3, 2.22.5, 2.24.1, 3.0.0.M4
>Reporter: Dimitri Kotlovsky
>Assignee: Claus Ibsen
>Priority: Minor
> Labels: pull-request-available
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Hi,
> I face a requirement to place temp files in a folder at the same hierarchy as
> the output folder like this:
> * {{target/data/output/claus.txt}}
> * {{target/data/temp/claus.tmp}}
> Using a simple route definition like:
> {code:java}
> from("direct:a").to("file://target/data/output/?tempFileName=../temp/${file:name.noext}.tmp"){code}
>
> If the temp folder does not exist, the GenericFileProducer should auto-create
> it. However, it only does so correctly for the tempFileName path, if it is
> *relativ "after" the endpoint path*. If it is above/before the endpoint path
> the tempFileName path will be created as a child of the endpoint path instead:
> * {{target/data/output/target/data/temp}}
> This results in a NoSuchFileException when camel tries to write the temp file
> into the "correct" temp directory target/data/temp afterwards.
>
>
> A very easy way to reproduce this is to use the 'parentFileUrl' instead of
> the 'fileUrl' in the createRouteBuilder method of
> FileProduceTempFileNameTest.java
> ([https://github.com/apache/camel/blob/master/core/camel-core/src/test/java/org/apache/camel/component/file/FileProduceTempFileNameTest.java]).
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924521#comment-16924521
]
Grzegorz Grzybek commented on CAMEL-13951:
--
Thanks Claus - I wanted to tackle it on Monday - I'll check then and let you
know. Thanks for help!
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.RC2
>
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924496#comment-16924496
]
Claus Ibsen commented on CAMEL-13951:
-
I added setter to set custom propagation behaviour
https://github.com/apache/camel/commit/b1b8fbc9e0027c6c4158405f0e9b3cb5165c9cc0
That is a first step, you can try this and see if it this helps. Then we can
work on making a nicer option to turn on PostgreSQL behaviour
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.RC2
>
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924497#comment-16924497
]
Claus Ibsen commented on CAMEL-13951:
-
It has also been backported to 2.x branches
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.RC2
>
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924458#comment-16924458
]
Freeman Fang edited comment on CAMEL-13953 at 9/6/19 5:34 PM:
--
Hi [~4535992],
Thanks for the update.
In your blueprint do you really need to use so many xsds? Like undertow and
security related xsds you definitely need to install more features. And for
namespace like
http://camel.apache.org/schema/cxf/camel-cxf-blueprint
I don't think this is correct, does it work previously?
Anyway, could you please append a reproducer project? A reproducer absolutely
can help speed up the process to address this issue. If you are the Red Hat
Fuse customer, you can use that channel to put your reproducer.
Thanks!
Freeman
was (Author: ffang):
Hi [~4535992],
Thanks for the update.
In your blueprint do you really need to use so many xsds? Like undertow and
security related xsds you definitely need to install more features.
Could you please append a reproducer project? A reproducer absolutely can help
speed up the process to address this issue. If you are the Red Hat Fuse
customer, you can use that channel to put your reproducer.
Thanks!
Freeman
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924458#comment-16924458
]
Freeman Fang commented on CAMEL-13953:
--
Hi [~4535992],
Thanks for the update.
In your blueprint do you really need to use so many xsds? Like undertow and
security related xsds you definitely need to install more features.
Could you please append a reproducer project? A reproducer absolutely can help
speed up the process to address this issue. If you are the Red Hat Fuse
customer, you can use that channel to put your reproducer.
Thanks!
Freeman
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Assigned] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CAMEL-13953:
Assignee: Freeman Fang
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924414#comment-16924414
]
Marco Tenti edited comment on CAMEL-13953 at 9/6/19 5:06 PM:
-
ty all for the clarification.
For now i use the http protocol instead of https .
I'm not very smart on this configuration, but here my "blueprint.xml header"
updated :
{code:xml}
http://osgi.org/xmlns/blueprint/v1.0.0";
xmlns:blueprint-schema-cxf="http://camel.apache.org/schema/cxf";
xmlns:camel="http://camel.apache.org/schema/blueprint";
xmlns:cm="http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0";
xmlns:ctx="http://www.springframework.org/schema/context";
xmlns:cxf="http://camel.apache.org/schema/cxf/camel-cxf-blueprint";
xmlns:cxf-core="http://cxf.apache.org/schemas/blueprint/core";
xmlns:cxf-security="http://cxf.apache.org/configuration/security";
xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0";
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
xmlns:http="http://cxf.apache.org/schemas/configuration/http-conf";
xmlns:httpn="http://cxf.apache.org/schemas/configuration/http-netty-server";
xmlns:httpu="http://cxf.apache.org/schemas/configuration/http-undertow";
xmlns:jaxrs="http://cxf.apache.org/schemas/blueprint/jaxrs";
xmlns:jaxws="http://cxf.apache.org/schemas/blueprint/jaxws";
xmlns:osgi="http://www.springframework.org/schema/osgi";
xmlns:osgix="http://www.springframework.org/schema/osgi-compendium";
xmlns:sec="http://cxf.apache.org/schemas/configuration/security";
xmlns:spring-beans="http://www.springframework.org/schema/beans";
xmlns:spring-camel-cxf="http://camel.apache.org/schema/cxf";
xmlns:spring-security="http://www.springframework.org/schema/security";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://osgi.org/xmlns/blueprint/v1.0.0
https://osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd
http://camel.apache.org/schema/cxf/camel-cxf-blueprint.xsd
http://cxf.apache.org/schemas/blueprint/core
http://cxf.apache.org/schemas/blueprint/core.xsd
http://karaf.apache.org/xmlns/jasypt/v1.0.0
http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0
http://aries.apache.org/schemas/blueprint-ext/blueprint-ext.xsd
http://cxf.apache.org/schemas/configuration/http-conf
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/schemas/configuration/http-netty-server
http://cxf.apache.org/schemas/configuration/http-netty-server.xsd
http://cxf.apache.org/schemas/configuration/http-undertow
http://cxf.apache.org/schemas/configuration/http-undertow.xsd
http://cxf.apache.org/schemas/blueprint/jaxrs
http://cxf.apache.org/schemas/blueprint/jaxrs.xsd
http://cxf.apache.org/schemas/blueprint/jaxws
http://cxf.apache.org/schemas/blueprint/jaxws.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://www.springframework.org/schema/osgi-compendium
http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd
http://cxf.apache.org/schemas/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/cxf
https://camel.apache.org/schema/cxf/camel-cxf.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security.xsd";>
{code}
i still get the error
{code:java}
is waiting for namespace handlers [http://osgi.org/xmlns/blueprint/v1.0.0,
http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
http://cxf.apache.org/schemas/blueprint/core,
http://cxf.apache.org/schemas/configuration/security,
http://cxf.apache.org/schemas/configuration/http-conf,
http://camel.apache.org/schema/blueprint,
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0,
http://cxf.apache.org/schemas/configuration/http-undertow]
{code}
there is still some wrong url on this?
*To answer to Claus and Freeman:* i'm using RedHat Fuse and i've installed the
feature "camel-cxf" there is some configuration i must put on my OSGI manifest
for avoid the call to remote XSD using a the mebdded XSD on the "camel-cxf"
bundle?
Here the maven plugin i'
[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924414#comment-16924414
]
Marco Tenti edited comment on CAMEL-13953 at 9/6/19 5:06 PM:
-
ty all for the clarification.
For now i use the http protocol instead of https .
I'm not very smart on this configuration, but here my "blueprint.xml header"
updated :
{code:xml}
http://osgi.org/xmlns/blueprint/v1.0.0";
xmlns:blueprint-schema-cxf="http://camel.apache.org/schema/cxf";
xmlns:camel="http://camel.apache.org/schema/blueprint";
xmlns:cm="http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0";
xmlns:ctx="http://www.springframework.org/schema/context";
xmlns:cxf="http://camel.apache.org/schema/cxf/camel-cxf-blueprint";
xmlns:cxf-core="http://cxf.apache.org/schemas/blueprint/core";
xmlns:cxf-security="http://cxf.apache.org/configuration/security";
xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0";
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
xmlns:http="http://cxf.apache.org/schemas/configuration/http-conf";
xmlns:httpn="http://cxf.apache.org/schemas/configuration/http-netty-server";
xmlns:httpu="http://cxf.apache.org/schemas/configuration/http-undertow";
xmlns:jaxrs="http://cxf.apache.org/schemas/blueprint/jaxrs";
xmlns:jaxws="http://cxf.apache.org/schemas/blueprint/jaxws";
xmlns:osgi="http://www.springframework.org/schema/osgi";
xmlns:osgix="http://www.springframework.org/schema/osgi-compendium";
xmlns:sec="http://cxf.apache.org/schemas/configuration/security";
xmlns:spring-beans="http://www.springframework.org/schema/beans";
xmlns:spring-camel-cxf="http://camel.apache.org/schema/cxf";
xmlns:spring-security="http://www.springframework.org/schema/security";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://osgi.org/xmlns/blueprint/v1.0.0
https://osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd
http://camel.apache.org/schema/cxf/camel-cxf-blueprint.xsd
http://cxf.apache.org/schemas/blueprint/core
http://cxf.apache.org/schemas/blueprint/core.xsd
http://karaf.apache.org/xmlns/jasypt/v1.0.0
http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0
http://aries.apache.org/schemas/blueprint-ext/blueprint-ext.xsd
http://cxf.apache.org/schemas/configuration/http-conf
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/schemas/configuration/http-netty-server
http://cxf.apache.org/schemas/configuration/http-netty-server.xsd
http://cxf.apache.org/schemas/configuration/http-undertow
http://cxf.apache.org/schemas/configuration/http-undertow.xsd
http://cxf.apache.org/schemas/blueprint/jaxrs
http://cxf.apache.org/schemas/blueprint/jaxrs.xsd
http://cxf.apache.org/schemas/blueprint/jaxws
http://cxf.apache.org/schemas/blueprint/jaxws.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://www.springframework.org/schema/osgi-compendium
http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd
http://cxf.apache.org/schemas/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/cxf
https://camel.apache.org/schema/cxf/camel-cxf.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security.xsd";>
{code}
i still get the error
{code:java}
is waiting for namespace handlers [http://osgi.org/xmlns/blueprint/v1.0.0,
http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
http://cxf.apache.org/schemas/blueprint/core,
http://cxf.apache.org/schemas/configuration/security,
http://cxf.apache.org/schemas/configuration/http-conf,
http://camel.apache.org/schema/blueprint,
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0,
http://cxf.apache.org/schemas/configuration/http-undertow]
{code}
there is still some wrong url on this?
*To answer to Claus and Freeman:* i'm using RedHat Fuse and i've installed the
feature "camel-cxf" there is some configuration i must put on my OSGI manifest
for avoid the call to remote XSD using a the embbeded XSD on the "camel-cxf"
bundle?
Here the maven plugin i
[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924414#comment-16924414
]
Marco Tenti edited comment on CAMEL-13953 at 9/6/19 5:02 PM:
-
ty all for the clarification.
For now i use the http protocol instead of https .
I'm not very smart on this configuration, but here my "blueprint.xml header"
updated :
{code:xml}
http://osgi.org/xmlns/blueprint/v1.0.0";
xmlns:blueprint-schema-cxf="http://camel.apache.org/schema/cxf";
xmlns:camel="http://camel.apache.org/schema/blueprint";
xmlns:cm="http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0";
xmlns:ctx="http://www.springframework.org/schema/context";
xmlns:cxf="http://camel.apache.org/schema/cxf/camel-cxf-blueprint";
xmlns:cxf-core="http://cxf.apache.org/schemas/blueprint/core";
xmlns:cxf-security="http://cxf.apache.org/configuration/security";
xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0";
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
xmlns:http="http://cxf.apache.org/schemas/configuration/http-conf";
xmlns:httpn="http://cxf.apache.org/schemas/configuration/http-netty-server";
xmlns:httpu="http://cxf.apache.org/schemas/configuration/http-undertow";
xmlns:jaxrs="http://cxf.apache.org/schemas/blueprint/jaxrs";
xmlns:jaxws="http://cxf.apache.org/schemas/blueprint/jaxws";
xmlns:osgi="http://www.springframework.org/schema/osgi";
xmlns:osgix="http://www.springframework.org/schema/osgi-compendium";
xmlns:sec="http://cxf.apache.org/schemas/configuration/security";
xmlns:spring-beans="http://www.springframework.org/schema/beans";
xmlns:spring-camel-cxf="http://camel.apache.org/schema/cxf";
xmlns:spring-security="http://www.springframework.org/schema/security";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://osgi.org/xmlns/blueprint/v1.0.0
https://osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd
http://camel.apache.org/schema/cxf/camel-cxf-blueprint.xsd
http://cxf.apache.org/schemas/blueprint/core
http://cxf.apache.org/schemas/blueprint/core.xsd
http://karaf.apache.org/xmlns/jasypt/v1.0.0
http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0
http://aries.apache.org/schemas/blueprint-ext/blueprint-ext.xsd
http://cxf.apache.org/schemas/configuration/http-conf
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/schemas/configuration/http-netty-server
http://cxf.apache.org/schemas/configuration/http-netty-server.xsd
http://cxf.apache.org/schemas/configuration/http-undertow
http://cxf.apache.org/schemas/configuration/http-undertow.xsd
http://cxf.apache.org/schemas/blueprint/jaxrs
http://cxf.apache.org/schemas/blueprint/jaxrs.xsd
http://cxf.apache.org/schemas/blueprint/jaxws
http://cxf.apache.org/schemas/blueprint/jaxws.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://www.springframework.org/schema/osgi-compendium
http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd
http://cxf.apache.org/schemas/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/cxf
https://camel.apache.org/schema/cxf/camel-cxf.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security.xsd";>
{code}
i still get the error
{code:java}
is waiting for namespace handlers [http://osgi.org/xmlns/blueprint/v1.0.0,
http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
http://cxf.apache.org/schemas/blueprint/core,
http://cxf.apache.org/schemas/configuration/security,
http://cxf.apache.org/schemas/configuration/http-conf,
http://camel.apache.org/schema/blueprint,
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0,
http://cxf.apache.org/schemas/configuration/http-undertow]
{code}
there is still some wrong url on this?
*To answer to Claus* i'm using RedHat Fuse and i've installed the feature
"camel-cxf" there is some configuration i must put on my OSGI manifest for
avoid the call to remote XSD using a "blueprint.xml" ?
was (Author: 4535992):
ty all for the clarification.
For now
[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924414#comment-16924414
]
Marco Tenti edited comment on CAMEL-13953 at 9/6/19 5:00 PM:
-
ty all for the clarification.
For now i use the http protocol instead of https .
I'm not very smart on this configuration, but here my "blueprint.xml header"
updated :
{code:xml}
http://osgi.org/xmlns/blueprint/v1.0.0";
xmlns:blueprint-schema-cxf="http://camel.apache.org/schema/cxf";
xmlns:camel="http://camel.apache.org/schema/blueprint";
xmlns:cm="http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0";
xmlns:ctx="http://www.springframework.org/schema/context";
xmlns:cxf="http://camel.apache.org/schema/cxf/camel-cxf-blueprint";
xmlns:cxf-core="http://cxf.apache.org/schemas/blueprint/core";
xmlns:cxf-security="http://cxf.apache.org/configuration/security";
xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0";
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
xmlns:http="http://cxf.apache.org/schemas/configuration/http-conf";
xmlns:httpn="http://cxf.apache.org/schemas/configuration/http-netty-server";
xmlns:httpu="http://cxf.apache.org/schemas/configuration/http-undertow";
xmlns:jaxrs="http://cxf.apache.org/schemas/blueprint/jaxrs";
xmlns:jaxws="http://cxf.apache.org/schemas/blueprint/jaxws";
xmlns:osgi="http://www.springframework.org/schema/osgi";
xmlns:osgix="http://www.springframework.org/schema/osgi-compendium";
xmlns:sec="http://cxf.apache.org/schemas/configuration/security";
xmlns:spring-beans="http://www.springframework.org/schema/beans";
xmlns:spring-camel-cxf="http://camel.apache.org/schema/cxf";
xmlns:spring-security="http://www.springframework.org/schema/security";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://osgi.org/xmlns/blueprint/v1.0.0
https://osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd
http://camel.apache.org/schema/cxf/camel-cxf-blueprint.xsd
http://cxf.apache.org/schemas/blueprint/core
http://cxf.apache.org/schemas/blueprint/core.xsd
http://karaf.apache.org/xmlns/jasypt/v1.0.0
http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0
http://aries.apache.org/schemas/blueprint-ext/blueprint-ext.xsd
http://cxf.apache.org/schemas/configuration/http-conf
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/schemas/configuration/http-netty-server
http://cxf.apache.org/schemas/configuration/http-netty-server.xsd
http://cxf.apache.org/schemas/configuration/http-undertow
http://cxf.apache.org/schemas/configuration/http-undertow.xsd
http://cxf.apache.org/schemas/blueprint/jaxrs
http://cxf.apache.org/schemas/blueprint/jaxrs.xsd
http://cxf.apache.org/schemas/blueprint/jaxws
http://cxf.apache.org/schemas/blueprint/jaxws.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://www.springframework.org/schema/osgi-compendium
http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd
http://cxf.apache.org/schemas/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/cxf
https://camel.apache.org/schema/cxf/camel-cxf.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security.xsd";>
{code}
i still get the error
{code:java}
is waiting for namespace handlers [http://osgi.org/xmlns/blueprint/v1.0.0,
http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
http://cxf.apache.org/schemas/blueprint/core,
http://cxf.apache.org/schemas/configuration/security,
http://cxf.apache.org/schemas/configuration/http-conf,
http://camel.apache.org/schema/blueprint,
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0,
http://cxf.apache.org/schemas/configuration/http-undertow]
{code}
there is still some wrong url on this?
was (Author: 4535992):
ty all for the clarification.
For now i use the http protocol instead of https .
I'm not very smart on this configuration, but here my "blueprint.xml header"
update by the sugeestion :
{code:xml}
http://osgi.org/xmlns/blueprint/v1.0.0";
xml
[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924414#comment-16924414
]
Marco Tenti edited comment on CAMEL-13953 at 9/6/19 4:59 PM:
-
ty all for the clarification.
For now i use the http protocl instead of https .
I'm not very smart on this configuration, but here my "blueprint.xml header"
update by the sugeestion :
{code:xml}
http://osgi.org/xmlns/blueprint/v1.0.0";
xmlns:blueprint-schema-cxf="http://camel.apache.org/schema/cxf";
xmlns:camel="http://camel.apache.org/schema/blueprint";
xmlns:cm="http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0";
xmlns:ctx="http://www.springframework.org/schema/context";
xmlns:cxf="http://camel.apache.org/schema/cxf/camel-cxf-blueprint";
xmlns:cxf-core="http://cxf.apache.org/schemas/blueprint/core";
xmlns:cxf-security="http://cxf.apache.org/configuration/security";
xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0";
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
xmlns:http="http://cxf.apache.org/schemas/configuration/http-conf";
xmlns:httpn="http://cxf.apache.org/schemas/configuration/http-netty-server";
xmlns:httpu="http://cxf.apache.org/schemas/configuration/http-undertow";
xmlns:jaxrs="http://cxf.apache.org/schemas/blueprint/jaxrs";
xmlns:jaxws="http://cxf.apache.org/schemas/blueprint/jaxws";
xmlns:osgi="http://www.springframework.org/schema/osgi";
xmlns:osgix="http://www.springframework.org/schema/osgi-compendium";
xmlns:sec="http://cxf.apache.org/schemas/configuration/security";
xmlns:spring-beans="http://www.springframework.org/schema/beans";
xmlns:spring-camel-cxf="http://camel.apache.org/schema/cxf";
xmlns:spring-security="http://www.springframework.org/schema/security";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://osgi.org/xmlns/blueprint/v1.0.0
https://osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd
http://camel.apache.org/schema/cxf/camel-cxf-blueprint.xsd
http://cxf.apache.org/schemas/blueprint/core
http://cxf.apache.org/schemas/blueprint/core.xsd
http://karaf.apache.org/xmlns/jasypt/v1.0.0
http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0
http://aries.apache.org/schemas/blueprint-ext/blueprint-ext.xsd
http://cxf.apache.org/schemas/configuration/http-conf
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/schemas/configuration/http-netty-server
http://cxf.apache.org/schemas/configuration/http-netty-server.xsd
http://cxf.apache.org/schemas/configuration/http-undertow
http://cxf.apache.org/schemas/configuration/http-undertow.xsd
http://cxf.apache.org/schemas/blueprint/jaxrs
http://cxf.apache.org/schemas/blueprint/jaxrs.xsd
http://cxf.apache.org/schemas/blueprint/jaxws
http://cxf.apache.org/schemas/blueprint/jaxws.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://www.springframework.org/schema/osgi-compendium
http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd
http://cxf.apache.org/schemas/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/cxf
https://camel.apache.org/schema/cxf/camel-cxf.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security.xsd";>
{code}
i still get the error
{code:java}
is waiting for namespace handlers [http://osgi.org/xmlns/blueprint/v1.0.0,
http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
http://cxf.apache.org/schemas/blueprint/core,
http://cxf.apache.org/schemas/configuration/security,
http://cxf.apache.org/schemas/configuration/http-conf,
http://camel.apache.org/schema/blueprint,
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0,
http://cxf.apache.org/schemas/configuration/http-undertow]
{code}
there is still some wrong url on this?
was (Author: 4535992):
ty all for the clarification.
For now i use the http protocl instead of https .
I'm not very smart on this configuration, but here my blueprint.xml header :
{code:xml}
http://osgi.org/xmlns/blueprint/v1.0.0";
xmlns:blueprint-
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924414#comment-16924414
]
Marco Tenti commented on CAMEL-13953:
-
ty all for the clarification.
For now i use the http protocl instead of https .
I'm not very smart on this configuration, but here my blueprint.xml header :
{code:xml}
http://osgi.org/xmlns/blueprint/v1.0.0";
xmlns:blueprint-schema-cxf="http://camel.apache.org/schema/cxf";
xmlns:camel="http://camel.apache.org/schema/blueprint";
xmlns:cm="http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0";
xmlns:ctx="http://www.springframework.org/schema/context";
xmlns:cxf="http://camel.apache.org/schema/cxf/camel-cxf-blueprint";
xmlns:cxf-core="http://cxf.apache.org/schemas/blueprint/core";
xmlns:cxf-security="http://cxf.apache.org/configuration/security";
xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0";
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
xmlns:http="http://cxf.apache.org/schemas/configuration/http-conf";
xmlns:httpn="http://cxf.apache.org/schemas/configuration/http-netty-server";
xmlns:httpu="http://cxf.apache.org/schemas/configuration/http-undertow";
xmlns:jaxrs="http://cxf.apache.org/schemas/blueprint/jaxrs";
xmlns:jaxws="http://cxf.apache.org/schemas/blueprint/jaxws";
xmlns:osgi="http://www.springframework.org/schema/osgi";
xmlns:osgix="http://www.springframework.org/schema/osgi-compendium";
xmlns:sec="http://cxf.apache.org/schemas/configuration/security";
xmlns:spring-beans="http://www.springframework.org/schema/beans";
xmlns:spring-camel-cxf="http://camel.apache.org/schema/cxf";
xmlns:spring-security="http://www.springframework.org/schema/security";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://osgi.org/xmlns/blueprint/v1.0.0
https://osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd
http://camel.apache.org/schema/cxf/camel-cxf-blueprint.xsd
http://cxf.apache.org/schemas/blueprint/core
http://cxf.apache.org/schemas/blueprint/core.xsd
http://karaf.apache.org/xmlns/jasypt/v1.0.0
http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0
http://aries.apache.org/schemas/blueprint-ext/blueprint-ext.xsd
http://cxf.apache.org/schemas/configuration/http-conf
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/schemas/configuration/http-netty-server
http://cxf.apache.org/schemas/configuration/http-netty-server.xsd
http://cxf.apache.org/schemas/configuration/http-undertow
http://cxf.apache.org/schemas/configuration/http-undertow.xsd
http://cxf.apache.org/schemas/blueprint/jaxrs
http://cxf.apache.org/schemas/blueprint/jaxrs.xsd
http://cxf.apache.org/schemas/blueprint/jaxws
http://cxf.apache.org/schemas/blueprint/jaxws.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://www.springframework.org/schema/osgi-compendium
http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd
http://cxf.apache.org/schemas/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/cxf
https://camel.apache.org/schema/cxf/camel-cxf.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security.xsd";>
{code}
i still get the error
{code}
is waiting for namespace handlers [http://osgi.org/xmlns/blueprint/v1.0.0,
http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
http://cxf.apache.org/schemas/blueprint/core,
http://cxf.apache.org/schemas/configuration/security,
http://cxf.apache.org/schemas/configuration/http-conf,
http://camel.apache.org/schema/blueprint,
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0,
http://cxf.apache.org/schemas/configuration/http-undertow]
{code}
there is still some wrong url on this?
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>
[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924414#comment-16924414
]
Marco Tenti edited comment on CAMEL-13953 at 9/6/19 4:59 PM:
-
ty all for the clarification.
For now i use the http protocol instead of https .
I'm not very smart on this configuration, but here my "blueprint.xml header"
update by the sugeestion :
{code:xml}
http://osgi.org/xmlns/blueprint/v1.0.0";
xmlns:blueprint-schema-cxf="http://camel.apache.org/schema/cxf";
xmlns:camel="http://camel.apache.org/schema/blueprint";
xmlns:cm="http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0";
xmlns:ctx="http://www.springframework.org/schema/context";
xmlns:cxf="http://camel.apache.org/schema/cxf/camel-cxf-blueprint";
xmlns:cxf-core="http://cxf.apache.org/schemas/blueprint/core";
xmlns:cxf-security="http://cxf.apache.org/configuration/security";
xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0";
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
xmlns:http="http://cxf.apache.org/schemas/configuration/http-conf";
xmlns:httpn="http://cxf.apache.org/schemas/configuration/http-netty-server";
xmlns:httpu="http://cxf.apache.org/schemas/configuration/http-undertow";
xmlns:jaxrs="http://cxf.apache.org/schemas/blueprint/jaxrs";
xmlns:jaxws="http://cxf.apache.org/schemas/blueprint/jaxws";
xmlns:osgi="http://www.springframework.org/schema/osgi";
xmlns:osgix="http://www.springframework.org/schema/osgi-compendium";
xmlns:sec="http://cxf.apache.org/schemas/configuration/security";
xmlns:spring-beans="http://www.springframework.org/schema/beans";
xmlns:spring-camel-cxf="http://camel.apache.org/schema/cxf";
xmlns:spring-security="http://www.springframework.org/schema/security";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://osgi.org/xmlns/blueprint/v1.0.0
https://osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd
http://camel.apache.org/schema/cxf/camel-cxf-blueprint.xsd
http://cxf.apache.org/schemas/blueprint/core
http://cxf.apache.org/schemas/blueprint/core.xsd
http://karaf.apache.org/xmlns/jasypt/v1.0.0
http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0
http://aries.apache.org/schemas/blueprint-ext/blueprint-ext.xsd
http://cxf.apache.org/schemas/configuration/http-conf
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/schemas/configuration/http-netty-server
http://cxf.apache.org/schemas/configuration/http-netty-server.xsd
http://cxf.apache.org/schemas/configuration/http-undertow
http://cxf.apache.org/schemas/configuration/http-undertow.xsd
http://cxf.apache.org/schemas/blueprint/jaxrs
http://cxf.apache.org/schemas/blueprint/jaxrs.xsd
http://cxf.apache.org/schemas/blueprint/jaxws
http://cxf.apache.org/schemas/blueprint/jaxws.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://www.springframework.org/schema/osgi-compendium
http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd
http://cxf.apache.org/schemas/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/cxf
https://camel.apache.org/schema/cxf/camel-cxf.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security.xsd";>
{code}
i still get the error
{code:java}
is waiting for namespace handlers [http://osgi.org/xmlns/blueprint/v1.0.0,
http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
http://cxf.apache.org/schemas/blueprint/core,
http://cxf.apache.org/schemas/configuration/security,
http://cxf.apache.org/schemas/configuration/http-conf,
http://camel.apache.org/schema/blueprint,
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.3.0,
http://cxf.apache.org/schemas/configuration/http-undertow]
{code}
there is still some wrong url on this?
was (Author: 4535992):
ty all for the clarification.
For now i use the http protocl instead of https .
I'm not very smart on this configuration, but here my "blueprint.xml header"
update by the sugeestion :
{code:xml}
http://osgi.org/xmlns/blueprint/
[jira] [Commented] (CAMEL-13948) Unpredictable registry lookup
[
https://issues.apache.org/jira/browse/CAMEL-13948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924407#comment-16924407
]
Claus Ibsen commented on CAMEL-13948:
-
gnodet what would that mean in lucas example?
Wont that mean that when b is bound then a is unbound, because they are both
DefaultComponent / Compoent?
> Unpredictable registry lookup
> -
>
> Key: CAMEL-13948
> URL: https://issues.apache.org/jira/browse/CAMEL-13948
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.0.0, 3.0.0.RC2
>
>
> The camel registry support binding multiple classes to the same entry via the
> bind method:
> {code:java}
> void bind(String id, Class type, Object bean)
> {code}
> The underlying implementation is roughly:
> {code:java}
> void bind(String id, Class type, Object bean) {
> computeIfAbsent(id, k -> new LinkedHashMap<>()).put(type, bean);
> }
> {code}
> So assuming I have a class MyLogComponent which extends LogComponent and I do
> the following binding:
> {code:java}
> Component a = new LogComponent()
> Component b = new MyLogComponent()
> registry.bind("log", LogComponent.class, a )
> registry.bind("log", MyLogComponent.class, b)
> {code}
> then lookupByNameAndType may return different values depending on the type
> used for looking up the beans:
> {code:java}
> registry.lookupByNameAndType("log", LogComponent.class) ==> a
> registry.lookupByNameAndType("log", MyLogComponent.class) ==> b
> registry.lookupByNameAndType("log", DefaultComponent.class) ==> a or b
> (depends on the order)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13946) Upgrade to Maven 3.6.2
[ https://issues.apache.org/jira/browse/CAMEL-13946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924401#comment-16924401 ] Claus Ibsen commented on CAMEL-13946: - https://github.com/takari/maven-wrapper/issues/147 > Upgrade to Maven 3.6.2 > -- > > Key: CAMEL-13946 > URL: https://issues.apache.org/jira/browse/CAMEL-13946 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13946) Upgrade to Maven 3.6.2
[ https://issues.apache.org/jira/browse/CAMEL-13946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924397#comment-16924397 ] Claus Ibsen commented on CAMEL-13946: - Maven wrapped does not yet support maven 3.6.2 The command to update mvn -N io.takari:maven:wrapper > Upgrade to Maven 3.6.2 > -- > > Key: CAMEL-13946 > URL: https://issues.apache.org/jira/browse/CAMEL-13946 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (CAMEL-13935) camel-properties: Properties with types different from string are not taken into account
[
https://issues.apache.org/jira/browse/CAMEL-13935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13935.
-
Resolution: Fixed
> camel-properties: Properties with types different from string are not taken
> into account
>
>
> Key: CAMEL-13935
> URL: https://issues.apache.org/jira/browse/CAMEL-13935
> Project: Camel
> Issue Type: Bug
> Components: camel-properties
>Affects Versions: 3.0.0.RC1
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.RC2
>
>
> The properties component spi has a setOverrideProperties that allow to use an
> arbitrary Properties object so it is possible that the properties it holds
> are not of type string.
> In case the properties component is asked to resolve a non string property,
> then it will fail as DefaultPropertiesLookup uses Properties::getProperty [¹]
> which returns null in case of the requested property is not of type string.
> The error is a little bit misleading as it states:
> {code}
> because of PropertiesComponent with name properties must be defined in
> CamelContext to support property placeholders. Property with key [the.body]
> not found in properties from text: in.body == {{the.body}}
> {code}
> [1]
> https://github.com/apache/camel/blob/master/components/camel-properties/src/main/java/org/apache/camel/component/properties/DefaultPropertiesLookup.java#L40
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13905) camel-any23 - ascii doc warning
[ https://issues.apache.org/jira/browse/CAMEL-13905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924381#comment-16924381 ] Claus Ibsen commented on CAMEL-13905: - Has this not been fixed? > camel-any23 - ascii doc warning > --- > > Key: CAMEL-13905 > URL: https://issues.apache.org/jira/browse/CAMEL-13905 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.0.0, 3.0.0.RC2 > > > [INFO] Found 389 ascii document files > asciidoctor: WARNING: any23-dataformat.adoc: line 13: section title out of > sequence: expected level 1, got level 2 > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir > asciidoctor: WARNING: dropping line containing reference to missing > attribute: examplesdir -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13935) camel-properties: Properties with types different from string are not taken into account
[
https://issues.apache.org/jira/browse/CAMEL-13935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924380#comment-16924380
]
Claus Ibsen commented on CAMEL-13935:
-
Okay I have a fix
> camel-properties: Properties with types different from string are not taken
> into account
>
>
> Key: CAMEL-13935
> URL: https://issues.apache.org/jira/browse/CAMEL-13935
> Project: Camel
> Issue Type: Bug
> Components: camel-properties
>Affects Versions: 3.0.0.RC1
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.RC2
>
>
> The properties component spi has a setOverrideProperties that allow to use an
> arbitrary Properties object so it is possible that the properties it holds
> are not of type string.
> In case the properties component is asked to resolve a non string property,
> then it will fail as DefaultPropertiesLookup uses Properties::getProperty [¹]
> which returns null in case of the requested property is not of type string.
> The error is a little bit misleading as it states:
> {code}
> because of PropertiesComponent with name properties must be defined in
> CamelContext to support property placeholders. Property with key [the.body]
> not found in properties from text: in.body == {{the.body}}
> {code}
> [1]
> https://github.com/apache/camel/blob/master/components/camel-properties/src/main/java/org/apache/camel/component/properties/DefaultPropertiesLookup.java#L40
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Assigned] (CAMEL-13935) camel-properties: Properties with types different from string are not taken into account
[
https://issues.apache.org/jira/browse/CAMEL-13935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-13935:
---
Assignee: Claus Ibsen
> camel-properties: Properties with types different from string are not taken
> into account
>
>
> Key: CAMEL-13935
> URL: https://issues.apache.org/jira/browse/CAMEL-13935
> Project: Camel
> Issue Type: Bug
> Components: camel-properties
>Affects Versions: 3.0.0.RC1
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.RC2
>
>
> The properties component spi has a setOverrideProperties that allow to use an
> arbitrary Properties object so it is possible that the properties it holds
> are not of type string.
> In case the properties component is asked to resolve a non string property,
> then it will fail as DefaultPropertiesLookup uses Properties::getProperty [¹]
> which returns null in case of the requested property is not of type string.
> The error is a little bit misleading as it states:
> {code}
> because of PropertiesComponent with name properties must be defined in
> CamelContext to support property placeholders. Property with key [the.body]
> not found in properties from text: in.body == {{the.body}}
> {code}
> [1]
> https://github.com/apache/camel/blob/master/components/camel-properties/src/main/java/org/apache/camel/component/properties/DefaultPropertiesLookup.java#L40
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13935) camel-properties: Properties with types different from string are not taken into account
[
https://issues.apache.org/jira/browse/CAMEL-13935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924374#comment-16924374
]
Claus Ibsen commented on CAMEL-13935:
-
So we should make those setInitial / setOverride properties convert their
values to string types
> camel-properties: Properties with types different from string are not taken
> into account
>
>
> Key: CAMEL-13935
> URL: https://issues.apache.org/jira/browse/CAMEL-13935
> Project: Camel
> Issue Type: Bug
> Components: camel-properties
>Affects Versions: 3.0.0.RC1
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.RC2
>
>
> The properties component spi has a setOverrideProperties that allow to use an
> arbitrary Properties object so it is possible that the properties it holds
> are not of type string.
> In case the properties component is asked to resolve a non string property,
> then it will fail as DefaultPropertiesLookup uses Properties::getProperty [¹]
> which returns null in case of the requested property is not of type string.
> The error is a little bit misleading as it states:
> {code}
> because of PropertiesComponent with name properties must be defined in
> CamelContext to support property placeholders. Property with key [the.body]
> not found in properties from text: in.body == {{the.body}}
> {code}
> [1]
> https://github.com/apache/camel/blob/master/components/camel-properties/src/main/java/org/apache/camel/component/properties/DefaultPropertiesLookup.java#L40
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924368#comment-16924368
]
Claus Ibsen commented on CAMEL-13951:
-
We could also have a PostgresAggregationRepository that extends the default
class and then setup for postgres with that nested transaction behavior, as it
makes it clear its for postgres database.
Otherwise then the setter setPostgreSQLSpecialBehavio is maybe the best as
then more end users will spot it, as if the name is to generic they wont know
that it benefit them if they use postgres
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13951:
Fix Version/s: 3.0.0.RC2
2.25.0
2.24.2
3.0.0
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.RC2
>
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13912) Make sure error handlers are created during the reification process and avoid having them created at runtime
[ https://issues.apache.org/jira/browse/CAMEL-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924363#comment-16924363 ] Claus Ibsen commented on CAMEL-13912: - Is this complete and can be resolved? > Make sure error handlers are created during the reification process and avoid > having them created at runtime > > > Key: CAMEL-13912 > URL: https://issues.apache.org/jira/browse/CAMEL-13912 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.0.0.RC1 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.0.0.RC2 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924344#comment-16924344
]
Freeman Fang commented on CAMEL-13953:
--
Yes, camel-cxf always load schema/blueprint/camel-cxf.xsd from camel-cxf bundle.
[~4535992]
Any chance you can append a reproducer project?
Thanks!
Freeman
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13936) SNMP Component support ‘snmp walk’
[
https://issues.apache.org/jira/browse/CAMEL-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13936.
-
Fix Version/s: (was: Future)
3.0.0.RC2
3.0.0
Assignee: Claus Ibsen
Resolution: Fixed
> SNMP Component support ‘snmp walk’
> --
>
> Key: CAMEL-13936
> URL: https://issues.apache.org/jira/browse/CAMEL-13936
> Project: Camel
> Issue Type: New Feature
> Components: camel-snmp
>Affects Versions: 3.0.0.M4
> Environment: SnmpEndpoint.java>>
> public Producer createProducer() throws Exception {
> if (this.type == SnmpActionType.TRAP) {
> return new SnmpTrapProducer(this);
> } else {
> // return new SnmpProducer(this);
> return new SnmpProducer(this, this.type); // add the snmp walk
> }
> }
>
> SnmpProducer.java>>
> public class SnmpProducer extends DefaultProducer {
>
> private SnmpEndpoint endpoint;
>
> private Address targetAddress;
> private USM usm;
> private CommunityTarget target;
> private PDU pdu;
> private SnmpActionType actionType;
>
> public SnmpProducer(SnmpEndpoint endpoint) {
> super(endpoint);
> this.endpoint = endpoint;
> }
> public SnmpProducer(SnmpEndpoint endpoint, SnmpActionType actionType) {
> super(endpoint);
> this.endpoint = endpoint;
> this.actionType = actionType;
> }
>
> @Override
> protected void doStart() throws Exception {
> super.doStart();
> this.targetAddress = GenericAddress.parse(this.endpoint.getAddress());
> log.debug("targetAddress: {}", targetAddress);
> this.usm = new USM(SecurityProtocols.getInstance(), new
> OctetString(MPv3.createLocalEngineID()), 0);
> SecurityModels.getInstance().addSecurityModel(this.usm);
>
> // setting up target
> this.target = new CommunityTarget();
> this.target.setCommunity(new OctetString(endpoint.getSnmpCommunity()));
> this.target.setAddress(this.targetAddress);
> this.target.setRetries(this.endpoint.getRetries());
> this.target.setTimeout(this.endpoint.getTimeout());
> this.target.setVersion(this.endpoint.getSnmpVersion());
> this.pdu = new PDU();
> // only POLL do
> if (this.actionType == SnmpActionType.POLL) {
> for (OID oid : this.endpoint.getOids()) {
> this.pdu.add(new VariableBinding(oid));
> }
> }
> this.pdu.setErrorIndex(0);
> this.pdu.setErrorStatus(0);
> this.pdu.setMaxRepetitions(0);
> // this.pdu.setType(PDU.GET);
> // add the snmp walk
> if (this.actionType == SnmpActionType.POLL)
> this.pdu.setType(PDU.GET);
> else if (this.actionType == SnmpActionType.GET_NEXT)
> this.pdu.setType(PDU.GETNEXT);
> else
> this.pdu.setType(PDU.GET);
> }
>
> @Override
> protected void doStop() throws Exception {
> super.doStop();
> try {
> SecurityModels.getInstance().removeSecurityModel(new
> Integer32(this.usm.getID()));
> } finally {
> this.targetAddress = null;
> this.usm = null;
> this.target = null;
> this.pdu = null;
> }
> }
>
> @Override
> public void process(final Exchange exchange) throws Exception {
> // load connection data only if the endpoint is enabled
> Snmp snmp = null;
> TransportMapping transport = null;
> try {
> log.debug("Starting SNMP producer on {}", this.endpoint.getAddress());
>
> // either tcp or udp
> if ("tcp".equals(this.endpoint.getProtocol())) {
> transport = new DefaultTcpTransportMapping();
> } else if ("udp".equals(this.endpoint.getProtocol())) {
> transport = new DefaultUdpTransportMapping();
> } else {
> throw new IllegalArgumentException("Unknown protocol: " +
> this.endpoint.getProtocol());
> }
>
> snmp = new Snmp(transport);
>
> log.debug("Snmp: i am sending");
>
> snmp.listen();
> if (this.actionType == SnmpActionType.GET_NEXT) {
> // snmp walk
> List smLst = new ArrayList<>();
> for (OID oid : this.endpoint.getOids()) {
> this.pdu.clear();
> this.pdu.add(new VariableBinding(oid));
> boolean matched = true;
> while (matched) {
> ResponseEvent responseEvent = snmp.send(this.pdu, this.target);
> if (responseEvent == null || responseEvent.getResponse() == null) {
> break;
> }
> PDU response = responseEvent.getResponse();
> String nextOid = null;
> Vector variableBindings =
> response.getVariableBindings();
> for (int i = 0; i < variableBindings.size(); i++) {
> VariableBinding variableBinding = variableBindings.elementAt(i);
> Variable variable = variableBinding.getVariable();
> nextOid = variableBinding.getOid().toDottedString();
> if (!nextOid.startsWith(oid.toDottedString())) {
> matched = false;
> break;
> }
> }
> if (!matched) {
> break;
> }
> this.pdu.clear();
> pdu.add(new VariableBinding(new OID(nextOid)));
> smLst.add(new SnmpMessage(getEndpoint().getCamelContext(), response));
> }
> }
> exchange.getIn().setBody(smLst);
> } else {
> // snmp get
> ResponseEvent responseEvent = snmp.send(this.pdu, thi
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924323#comment-16924323
]
Claus Ibsen commented on CAMEL-13953:
-
However the namespace url http://camel.apache.org/schema/blueprint/cxf is
hardcoded in camel-cxf so the camel-cxf ought to pickup this url and load it
from the bundle JAR and not attempt any http remote url
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924268#comment-16924268
]
Claus Ibsen commented on CAMEL-13953:
-
The urls are wrong, they are as listed here
https://camel.apache.org/schema/cxf/
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924266#comment-16924266
]
Zoran Regvart commented on CAMEL-13953:
---
[~4535992] can you provide more details on this?
We launched a new version of Camel website a while back so this could be the
cause of your issue. The previous website also did not contain
http://camel.apache.org/schema/blueprint/cxf URL
(https://svn.apache.org/repos/infra/websites/production/camel/content/schema/blueprint/
still has the content of the old website), so you should have been getting a
404 on the old website as well. The only difference could be that we serve the
404 page over https.
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924257#comment-16924257
]
Freeman Fang commented on CAMEL-13953:
--
Hi [~4535992],
This should be taken care of by Apache Camel community so I move this to Camel
jira.
Freeman
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Moved] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down
[
https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang moved DOSGI-281 to CAMEL-13953:
Key: CAMEL-13953 (was: DOSGI-281)
Project: Camel (was: CXF Distributed OSGi)
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13943) Camel-kafka Test cases getting failed
[
https://issues.apache.org/jira/browse/CAMEL-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-13943:
-
Priority: Minor (was: Major)
> Camel-kafka Test cases getting failed
> ---
>
> Key: CAMEL-13943
> URL: https://issues.apache.org/jira/browse/CAMEL-13943
> Project: Camel
> Issue Type: Test
> Components: camel-kafka
>Affects Versions: 3.0.0.RC1
>Reporter: Ramu
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:java}
> ERROR] Failures:
> [ERROR]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 3:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [INFO]
> [WARNING] Flakes:
> [WARNING]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:78->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-1 expected:<4> but was:
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:77->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-0 expected:<4> but was:
> [INFO] Run 3: PASS
> [INFO]
> [INFO]
> [ERROR] Tests run: 61, Failures: 1, Errors: 0, Skipped: 3, Flakes: 1
> [INFO]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (CAMEL-13943) Camel-kafka Test cases getting failed
[
https://issues.apache.org/jira/browse/CAMEL-13943?focusedWorklogId=307848&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-307848
]
ASF GitHub Bot logged work on CAMEL-13943:
--
Author: ASF GitHub Bot
Created on: 06/Sep/19 13:27
Start Date: 06/Sep/19 13:27
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #3154: CAMEL-13943:
Fix failing unit tests in camel-kafka
URL: https://github.com/apache/camel/pull/3154
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: 307848)
Time Spent: 20m (was: 10m)
> Camel-kafka Test cases getting failed
> ---
>
> Key: CAMEL-13943
> URL: https://issues.apache.org/jira/browse/CAMEL-13943
> Project: Camel
> Issue Type: Test
> Components: camel-kafka
>Affects Versions: 3.0.0.RC1
>Reporter: Ramu
>Priority: Major
> Fix For: 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:java}
> ERROR] Failures:
> [ERROR]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 3:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [INFO]
> [WARNING] Flakes:
> [WARNING]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:78->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-1 expected:<4> but was:
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:77->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-0 expected:<4> but was:
> [INFO] Run 3: PASS
> [INFO]
> [INFO]
> [ERROR] Tests run: 61, Failures: 1, Errors: 0, Skipped: 3, Flakes: 1
> [INFO]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Assigned] (CAMEL-13943) Camel-kafka Test cases getting failed
[
https://issues.apache.org/jira/browse/CAMEL-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-13943:
Assignee: Andrea Cosentino
> Camel-kafka Test cases getting failed
> ---
>
> Key: CAMEL-13943
> URL: https://issues.apache.org/jira/browse/CAMEL-13943
> Project: Camel
> Issue Type: Test
> Components: camel-kafka
>Affects Versions: 3.0.0.RC1
>Reporter: Ramu
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:java}
> ERROR] Failures:
> [ERROR]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 3:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [INFO]
> [WARNING] Flakes:
> [WARNING]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:78->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-1 expected:<4> but was:
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:77->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-0 expected:<4> but was:
> [INFO] Run 3: PASS
> [INFO]
> [INFO]
> [ERROR] Tests run: 61, Failures: 1, Errors: 0, Skipped: 3, Flakes: 1
> [INFO]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13943) Camel-kafka Test cases getting failed
[
https://issues.apache.org/jira/browse/CAMEL-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13943.
--
Resolution: Fixed
> Camel-kafka Test cases getting failed
> ---
>
> Key: CAMEL-13943
> URL: https://issues.apache.org/jira/browse/CAMEL-13943
> Project: Camel
> Issue Type: Test
> Components: camel-kafka
>Affects Versions: 3.0.0.RC1
>Reporter: Ramu
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:java}
> ERROR] Failures:
> [ERROR]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 3:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [INFO]
> [WARNING] Flakes:
> [WARNING]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:78->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-1 expected:<4> but was:
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:77->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-0 expected:<4> but was:
> [INFO] Run 3: PASS
> [INFO]
> [INFO]
> [ERROR] Tests run: 61, Failures: 1, Errors: 0, Skipped: 3, Flakes: 1
> [INFO]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13943) Camel-kafka Test cases getting failed
[
https://issues.apache.org/jira/browse/CAMEL-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-13943:
-
Fix Version/s: 3.0.0.RC2
> Camel-kafka Test cases getting failed
> ---
>
> Key: CAMEL-13943
> URL: https://issues.apache.org/jira/browse/CAMEL-13943
> Project: Camel
> Issue Type: Test
> Components: camel-kafka
>Affects Versions: 3.0.0.RC1
>Reporter: Ramu
>Priority: Major
> Fix For: 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:java}
> ERROR] Failures:
> [ERROR]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 3:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [INFO]
> [WARNING] Flakes:
> [WARNING]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:78->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-1 expected:<4> but was:
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:77->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-0 expected:<4> but was:
> [INFO] Run 3: PASS
> [INFO]
> [INFO]
> [ERROR] Tests run: 61, Failures: 1, Errors: 0, Skipped: 3, Flakes: 1
> [INFO]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (CAMEL-13943) Camel-kafka Test cases getting failed
[
https://issues.apache.org/jira/browse/CAMEL-13943?focusedWorklogId=307797&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-307797
]
ASF GitHub Bot logged work on CAMEL-13943:
--
Author: ASF GitHub Bot
Created on: 06/Sep/19 12:27
Start Date: 06/Sep/19 12:27
Worklog Time Spent: 10m
Work Description: omarsmak commented on pull request #3154: CAMEL-13943:
Fix failing unit tests in camel-kafka
URL: https://github.com/apache/camel/pull/3154
This intends to go around with the race condition issue that _sometimes_
occurs with `MemoryStateRepository` in
`KafkaConsumerOffsetRepositoryResumeTest` and
`KafkaConsumerOffsetRepositoryEmptyTest` which as result cause the tests to
fail (not always)
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: 307797)
Remaining Estimate: 0h
Time Spent: 10m
> Camel-kafka Test cases getting failed
> ---
>
> Key: CAMEL-13943
> URL: https://issues.apache.org/jira/browse/CAMEL-13943
> Project: Camel
> Issue Type: Test
> Components: camel-kafka
>Affects Versions: 3.0.0.RC1
>Reporter: Ramu
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> ERROR] Failures:
> [ERROR]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 3:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [INFO]
> [WARNING] Flakes:
> [WARNING]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:78->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-1 expected:<4> but was:
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:77->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-0 expected:<4> but was:
> [INFO] Run 3: PASS
> [INFO]
> [INFO]
> [ERROR] Tests run: 61, Failures: 1, Errors: 0, Skipped: 3, Flakes: 1
> [INFO]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924190#comment-16924190
]
Claus Ibsen commented on CAMEL-13951:
-
So are you saying to add a setter/getter for propgation behavior and then you
can use NESTED for your use case? Maybe provide a PR with your ideas then we
can review / discuss that
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924157#comment-16924157
]
Grzegorz Grzybek commented on CAMEL-13951:
--
Or more generic name {{setUseNestedPropagation()}}?
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13869) camel-undertow - Upgrade to 2.x
[ https://issues.apache.org/jira/browse/CAMEL-13869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13869. -- Resolution: Fixed > camel-undertow - Upgrade to 2.x > --- > > Key: CAMEL-13869 > URL: https://issues.apache.org/jira/browse/CAMEL-13869 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC2 > > > It would be good to upgrade camel-undertow to 2.x before we go GA -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13869) camel-undertow - Upgrade to 2.x
[ https://issues.apache.org/jira/browse/CAMEL-13869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13869: - Fix Version/s: (was: 3.x) 3.0.0.RC2 > camel-undertow - Upgrade to 2.x > --- > > Key: CAMEL-13869 > URL: https://issues.apache.org/jira/browse/CAMEL-13869 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC2 > > > It would be good to upgrade camel-undertow to 2.x before we go GA -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (CAMEL-13821) Upgrade Corda Version in camel parent pom to 4.0
[ https://issues.apache.org/jira/browse/CAMEL-13821?focusedWorklogId=307719&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-307719 ] ASF GitHub Bot logged work on CAMEL-13821: -- Author: ASF GitHub Bot Created on: 06/Sep/19 09:34 Start Date: 06/Sep/19 09:34 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #3153: CAMEL-13821: Upgraded Corda RPC version to 4.0 URL: https://github.com/apache/camel/pull/3153 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: 307719) Time Spent: 40m (was: 0.5h) > Upgrade Corda Version in camel parent pom to 4.0 > > > Key: CAMEL-13821 > URL: https://issues.apache.org/jira/browse/CAMEL-13821 > Project: Camel > Issue Type: Improvement >Reporter: krishnath poologanathan >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC2 > > Time Spent: 40m > Remaining Estimate: 0h > > Corda client which uses camel Corda component is unable to connect with > Corda 4 node -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (CAMEL-13821) Upgrade Corda Version in camel parent pom to 4.0
[ https://issues.apache.org/jira/browse/CAMEL-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13821: Assignee: Andrea Cosentino > Upgrade Corda Version in camel parent pom to 4.0 > > > Key: CAMEL-13821 > URL: https://issues.apache.org/jira/browse/CAMEL-13821 > Project: Camel > Issue Type: Improvement >Reporter: krishnath poologanathan >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.x > > Time Spent: 0.5h > Remaining Estimate: 0h > > Corda client which uses camel Corda component is unable to connect with > Corda 4 node -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (CAMEL-13821) Upgrade Corda Version in camel parent pom to 4.0
[ https://issues.apache.org/jira/browse/CAMEL-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13821. -- Resolution: Fixed > Upgrade Corda Version in camel parent pom to 4.0 > > > Key: CAMEL-13821 > URL: https://issues.apache.org/jira/browse/CAMEL-13821 > Project: Camel > Issue Type: Improvement >Reporter: krishnath poologanathan >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Corda client which uses camel Corda component is unable to connect with > Corda 4 node -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13821) Upgrade Corda Version in camel parent pom to 4.0
[ https://issues.apache.org/jira/browse/CAMEL-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13821: - Fix Version/s: (was: 3.x) 3.0.0.RC2 > Upgrade Corda Version in camel parent pom to 4.0 > > > Key: CAMEL-13821 > URL: https://issues.apache.org/jira/browse/CAMEL-13821 > Project: Camel > Issue Type: Improvement >Reporter: krishnath poologanathan >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Corda client which uses camel Corda component is unable to connect with > Corda 4 node -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13952) Project URL in pom is incorrect
[ https://issues.apache.org/jira/browse/CAMEL-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924085#comment-16924085 ] Zoran Regvart commented on CAMEL-13952: --- [~ST-DDT] seems that you need this fixed for your use case, we can wait... ;) > Project URL in pom is incorrect > --- > > Key: CAMEL-13952 > URL: https://issues.apache.org/jira/browse/CAMEL-13952 > Project: Camel > Issue Type: Wish >Reporter: D T >Priority: Minor > > Maven seems to append the submodules name/path to the url, thus the URL for > the submodules is wrong. > > Examples: > [http://camel.apache.org/camel-parent/camel-core] > [http://camel.apache.org/camel-parent/components/camel-spring] > [http://camel.apache.org/camel-parent/components/camel-spring-boot] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-core-starter] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-spring-boot-starter] > > Please configure the submodules url correctly or add server side redirects. > > Ref: https://github.com/apache/camel/blob/master/pom.xml#L37 > > PS: While you are at it, please use `https` links. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13952) Project URL in pom is incorrect
[ https://issues.apache.org/jira/browse/CAMEL-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924084#comment-16924084 ] D T commented on CAMEL-13952: - Spring-Boot avoided the issue by suffixing the url with a `#` in their parent pom. > Project URL in pom is incorrect > --- > > Key: CAMEL-13952 > URL: https://issues.apache.org/jira/browse/CAMEL-13952 > Project: Camel > Issue Type: Wish >Reporter: D T >Priority: Minor > > Maven seems to append the submodules name/path to the url, thus the URL for > the submodules is wrong. > > Examples: > [http://camel.apache.org/camel-parent/camel-core] > [http://camel.apache.org/camel-parent/components/camel-spring] > [http://camel.apache.org/camel-parent/components/camel-spring-boot] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-core-starter] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-spring-boot-starter] > > Please configure the submodules url correctly or add server side redirects. > > Ref: https://github.com/apache/camel/blob/master/pom.xml#L37 > > PS: While you are at it, please use `https` links. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13821) Upgrade Corda Version in camel parent pom to 4.0
[ https://issues.apache.org/jira/browse/CAMEL-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924080#comment-16924080 ] Amol Pednekar commented on CAMEL-13821: --- [https://github.com/apache/camel/pull/3153] > Upgrade Corda Version in camel parent pom to 4.0 > > > Key: CAMEL-13821 > URL: https://issues.apache.org/jira/browse/CAMEL-13821 > Project: Camel > Issue Type: Improvement >Reporter: krishnath poologanathan >Priority: Major > Fix For: 3.x > > Time Spent: 0.5h > Remaining Estimate: 0h > > Corda client which uses camel Corda component is unable to connect with > Corda 4 node -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (CAMEL-13821) Upgrade Corda Version in camel parent pom to 4.0
[ https://issues.apache.org/jira/browse/CAMEL-13821?focusedWorklogId=307716&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-307716 ] ASF GitHub Bot logged work on CAMEL-13821: -- Author: ASF GitHub Bot Created on: 06/Sep/19 09:22 Start Date: 06/Sep/19 09:22 Worklog Time Spent: 10m Work Description: amolpednekar commented on pull request #3153: CAMEL-13821: Upgraded Corda RPC version to 4.0 URL: https://github.com/apache/camel/pull/3153 Updated RPC version to 4.0 Issue and discussion: https://issues.apache.org/jira/browse/CAMEL-13821 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: 307716) Time Spent: 0.5h (was: 20m) > Upgrade Corda Version in camel parent pom to 4.0 > > > Key: CAMEL-13821 > URL: https://issues.apache.org/jira/browse/CAMEL-13821 > Project: Camel > Issue Type: Improvement >Reporter: krishnath poologanathan >Priority: Major > Fix For: 3.x > > Time Spent: 0.5h > Remaining Estimate: 0h > > Corda client which uses camel Corda component is unable to connect with > Corda 4 node -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13952) Project URL in pom is incorrect
[ https://issues.apache.org/jira/browse/CAMEL-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924075#comment-16924075 ] D T commented on CAMEL-13952: - [~zregvart]: Sure, but it might take a while. > Project URL in pom is incorrect > --- > > Key: CAMEL-13952 > URL: https://issues.apache.org/jira/browse/CAMEL-13952 > Project: Camel > Issue Type: Wish >Reporter: D T >Priority: Minor > > Maven seems to append the submodules name/path to the url, thus the URL for > the submodules is wrong. > > Examples: > [http://camel.apache.org/camel-parent/camel-core] > [http://camel.apache.org/camel-parent/components/camel-spring] > [http://camel.apache.org/camel-parent/components/camel-spring-boot] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-core-starter] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-spring-boot-starter] > > Please configure the submodules url correctly or add server side redirects. > > Ref: https://github.com/apache/camel/blob/master/pom.xml#L37 > > PS: While you are at it, please use `https` links. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13952) Project URL in pom is incorrect
[ https://issues.apache.org/jira/browse/CAMEL-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924073#comment-16924073 ] D T commented on CAMEL-13952: - In your root pom: [https://github.com/apache/camel/blob/master/pom.xml#L37] You define the url as `http://camel.apache.org` for each submodule maven (implicitly) appends the module name to the url. So for the `core` module this results in `http://camel.apache.org/core`. For the `core/camel-util` this results in `http://camel.apache.org/core/camel-util`. These urls will be then used by maven plugins and thus shown in dependency-reports. Usecase: We need to send a list of all our used libraries including a link to the projects page to our customers. For this we currently use maven's dependency site report. This contains ||GroupId||ArtifactId||Version||Type||Licenses|| for all used dependencies. But all links for camel's dependencies result in a HTTP 404, which makes it useless. Manually fixing it quite a lot of effort (checking/fixing ~100 libs/urls per software module), so i reported it here to be fixed "upstream" . You can test it yourself by executing `mvn site` on any project that uses camel. > Project URL in pom is incorrect > --- > > Key: CAMEL-13952 > URL: https://issues.apache.org/jira/browse/CAMEL-13952 > Project: Camel > Issue Type: Wish >Reporter: D T >Priority: Minor > > Maven seems to append the submodules name/path to the url, thus the URL for > the submodules is wrong. > > Examples: > [http://camel.apache.org/camel-parent/camel-core] > [http://camel.apache.org/camel-parent/components/camel-spring] > [http://camel.apache.org/camel-parent/components/camel-spring-boot] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-core-starter] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-spring-boot-starter] > > Please configure the submodules url correctly or add server side redirects. > > Ref: https://github.com/apache/camel/blob/master/pom.xml#L37 > > PS: While you are at it, please use `https` links. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13943) Camel-kafka Test cases getting failed
[
https://issues.apache.org/jira/browse/CAMEL-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924072#comment-16924072
]
Omar Al-Safi commented on CAMEL-13943:
--
I am looking at it
> Camel-kafka Test cases getting failed
> ---
>
> Key: CAMEL-13943
> URL: https://issues.apache.org/jira/browse/CAMEL-13943
> Project: Camel
> Issue Type: Test
> Components: camel-kafka
>Affects Versions: 3.0.0.RC1
>Reporter: Ramu
>Priority: Major
>
> {code:java}
> ERROR] Failures:
> [ERROR]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryResumeTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [ERROR] Run 3:
> KafkaConsumerOffsetRepositoryResumeTest.shouldResumeFromAnyParticularOffset:77->Assert.assertEquals:115
> partition-0 expected:<[4]> but was:<[2]>
> [INFO]
> [WARNING] Flakes:
> [WARNING]
> org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository(org.apache.camel.component.kafka.KafkaConsumerOffsetRepositoryEmptyTest)
> [ERROR] Run 1:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:78->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-1 expected:<4> but was:
> [ERROR] Run 2:
> KafkaConsumerOffsetRepositoryEmptyTest.shouldStartFromBeginningWithEmptyOffsetRepository:77->Assert.assertEquals:118->Assert.failNotEquals:834->Assert.fail:88
> partition-0 expected:<4> but was:
> [INFO] Run 3: PASS
> [INFO]
> [INFO]
> [ERROR] Tests run: 61, Failures: 1, Errors: 0, Skipped: 3, Flakes: 1
> [INFO]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13952) Project URL in pom is incorrect
[ https://issues.apache.org/jira/browse/CAMEL-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924065#comment-16924065 ] Zoran Regvart commented on CAMEL-13952: --- [~ST-DDT] could you provide a pull request for this? > Project URL in pom is incorrect > --- > > Key: CAMEL-13952 > URL: https://issues.apache.org/jira/browse/CAMEL-13952 > Project: Camel > Issue Type: Wish >Reporter: D T >Priority: Minor > > Maven seems to append the submodules name/path to the url, thus the URL for > the submodules is wrong. > > Examples: > [http://camel.apache.org/camel-parent/camel-core] > [http://camel.apache.org/camel-parent/components/camel-spring] > [http://camel.apache.org/camel-parent/components/camel-spring-boot] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-core-starter] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-spring-boot-starter] > > Please configure the submodules url correctly or add server side redirects. > > Ref: https://github.com/apache/camel/blob/master/pom.xml#L37 > > PS: While you are at it, please use `https` links. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924054#comment-16924054
]
Grzegorz Grzybek commented on CAMEL-13951:
--
Quickest option - make {{JdbcAggregationRepository#transactionTemplate}}
protected and tell PostgreSQL users to override {{doStart()}} to set nested
propagation on the template.
Setting NESTED for the template used in add()/remove()/confirm() by default
would work too but could change existing behavior for databases/drivers that
didn't have this _problem_ as PostgreSQL.
And what about {{setPostgreSQLSpecialBehavior(true)}} setter? (or with better
name)?
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (CAMEL-13851) camel-xj component contribution
[ https://issues.apache.org/jira/browse/CAMEL-13851?focusedWorklogId=307706&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-307706 ] ASF GitHub Bot logged work on CAMEL-13851: -- Author: ASF GitHub Bot Created on: 06/Sep/19 08:41 Start Date: 06/Sep/19 08:41 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #3093: CAMEL-13851: camel-xj component contribution URL: https://github.com/apache/camel/pull/3093 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: 307706) Time Spent: 20m (was: 10m) > camel-xj component contribution > --- > > Key: CAMEL-13851 > URL: https://issues.apache.org/jira/browse/CAMEL-13851 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.24.1, 3.0.0.M4 >Reporter: Marc Giger >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC2 > > Time Spent: 20m > Remaining Estimate: 0h > > Hi, > For a customer of mine i've setup an ESB infrastructure (JBoss Fuse) and > implement camel routes for some time now. Until now i've used camel-xmljson > that was nicely expressed "not so nice". It was always a pain to get the > desired output and needed most of the time some hacks. Lately we had some > performance issues with "larger" messages and the culprit was again the > xmljson lib because of its excessive regex use. Apart from that camel-xmljson > was removed from camel (correctly). So, time for a new component for direct > xml <-> json conversion. > Thanks goes to "Berner Fachhochschule" to allow me to work and contribute the > component. > On a high level the component works as follows: > xml -> xslt -> json and json -> xslt -> xml > This allows to transform the input document directly in the desired target > structure without the need of an intermediary format. > More in detail: > xml -> xslt -> XmlJsonStreamWriter -> json > The XmlJsonStreamWriter is a custom impl. of javax.xml.stream.XMLStreamWriter > that acts as a StAX -> JsonEvent bridge and uses internally > com.fasterxml.jackson.core.JsonGenerator as json writer. > In the other direction: > json -> JsonXmlStreamReader -> xslt -> xml > Here the JsonXmlStreamReader is a custom impl. of > avax.xml.stream.XMLStreamReader that acts as a JsonEvent -> StAX bridge and > uses internally com.fasterxml.jackson.core.JsonParser as json reader. > The json -> xml conversion is fully event driven. That means that just the > current token is held in memory. In the other direction, xml -> json, a > internal tree needs to be built and therefore the complete json document is > held in memory. Actually I can even see a possibility to stream it under some > circumstandes. > The current implementation can be found in: > https://github.com/kayuma/camel/tree/camel-xj-component > The question is now if the camel community is interested in this contribution? > Open Issues: > - Some of the classes are copies from the xslt component because of minor but > important differences that are required to get XJ to work. Maybe we should > refactor the xslt component so that it may be extended? Advice needed. > - Documentation > And in the end it would be very nice, if the contribution is accepted, if it > could be backported and integrated into camel 2.x > Thanks, > Marc -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924051#comment-16924051
]
Luca Burgazzoli commented on CAMEL-13950:
-
In my mind it is just about consistency and btw, I'm just ok to use rest(), but
as today we can basically do routing directly from the rest dsl:
{code:java}
rest()
.get("").to(...)
.post("").route().to("")
{code}
but with the introduction of the endpointdsl we have discrepancies as I cannot
do something like
{code:java}
timer("test")
.route().to("")
{code}
And I cannot use the result of the rest() method as endpoint so I'm striving to
find out if there is a way to improve what we have in order to provide a
consistent user experience.
But it is not as simple as I initially tough :)
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13952) Project URL in pom is incorrect
[ https://issues.apache.org/jira/browse/CAMEL-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924050#comment-16924050 ] Claus Ibsen commented on CAMEL-13952: - What do you mean, can you explain better? > Project URL in pom is incorrect > --- > > Key: CAMEL-13952 > URL: https://issues.apache.org/jira/browse/CAMEL-13952 > Project: Camel > Issue Type: Wish >Reporter: D T >Priority: Minor > > Maven seems to append the submodules name/path to the url, thus the URL for > the submodules is wrong. > > Examples: > [http://camel.apache.org/camel-parent/camel-core] > [http://camel.apache.org/camel-parent/components/camel-spring] > [http://camel.apache.org/camel-parent/components/camel-spring-boot] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-core-starter] > [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-spring-boot-starter] > > Please configure the submodules url correctly or add server side redirects. > > Ref: https://github.com/apache/camel/blob/master/pom.xml#L37 > > PS: While you are at it, please use `https` links. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924047#comment-16924047
]
Grzegorz Grzybek commented on CAMEL-13951:
--
Some kind of change in {{JdbcAggregationRepository}} is needed anyway. I can't
simply extend this class because
{{org.apache.camel.processor.aggregate.jdbc.JdbcAggregationRepository#transactionTemplate}}
is private - I can't replace it and I can't
{{org.springframework.transaction.support.DefaultTransactionDefinition#setPropagationBehavior}}
on it either.
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (CAMEL-13952) Project URL in pom is incorrect
D T created CAMEL-13952: --- Summary: Project URL in pom is incorrect Key: CAMEL-13952 URL: https://issues.apache.org/jira/browse/CAMEL-13952 Project: Camel Issue Type: Wish Reporter: D T Maven seems to append the submodules name/path to the url, thus the URL for the submodules is wrong. Examples: [http://camel.apache.org/camel-parent/camel-core] [http://camel.apache.org/camel-parent/components/camel-spring] [http://camel.apache.org/camel-parent/components/camel-spring-boot] [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-core-starter] [http://camel.apache.org/spring-boot/camel-spring-boot-dm/camel-starter-parent/components-starter/camel-spring-boot-starter] Please configure the submodules url correctly or add server side redirects. Ref: https://github.com/apache/camel/blob/master/pom.xml#L37 PS: While you are at it, please use `https` links. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924042#comment-16924042
]
Grzegorz Grzybek commented on CAMEL-13951:
--
bq. And be careful to tie to this to Spring XML only as those InitializingBean
etc are spring only
sure sure ;)
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924040#comment-16924040
]
Claus Ibsen commented on CAMEL-13951:
-
You can always write your own custom repository that fits your use-case /
database etc.
And yeah maybe JdbcAggRepo can be refactored to be more extensible, we have
done this in the past for some of the others. But we can't hit 100% of every
database setup that are out there in the world with the OOTB code, and
therefore you can write your own.
And be careful to tie to this to Spring XML only as those InitializingBean etc
are spring only. This should work for non spring users too etc. And therefore
Camel has its Service API where you have callbacks for start/stop etc.
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924037#comment-16924037
]
Claus Ibsen commented on CAMEL-13950:
-
Hmm then there is yet another variation, there is a special endpoint route
builder for endpoint DSL. And you can't have a rest route builder as well, and
we dont want a endpointDslwithRest route builder. Or am I mistaking.
And all for not writing rest() which clearly indicate its a rest service.
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924034#comment-16924034
]
Grzegorz Grzybek commented on CAMEL-13951:
--
The inflexibility of {{JdbcAggregationRepository}} is that it configures
{{org.apache.camel.processor.aggregate.jdbc.JdbcAggregationRepository#transactionTemplate}}
inside
{{org.apache.camel.processor.aggregate.jdbc.JdbcAggregationRepository#setTransactionManager()}}
without a way to specify the propagation behavior.
Please suggest the best way to _open_ {{JdbcAggregationRepository}}:
* add setter for the propagation behavior of template used for {{add()}}, to
allow pass {{PROPAGATION_NESTED}}
* add setter for entire {{TransactionTemplate}} used by
{{JdbcAggregationRepository#add()}}
* maybe use 3rd {{TransactionTemplate}} used only by {{add()}} to be used in
PostgreSQL case
Probably all of the above would require adding {{implements InitializingBean}}
and overriding {{afterPropertiesSet()}}.
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924031#comment-16924031
]
Claus Ibsen commented on CAMEL-13951:
-
Do you really want to use optimistic locking in the first place? It has its
caveats.
We could consider adding getter/setters so you can specify the SQL queries to
be used, then for postgres you can setup custom that uses this on conflict do
nothing stuff
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924030#comment-16924030
]
Luca Burgazzoli commented on CAMEL-13950:
-
that would work too
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924026#comment-16924026
]
Grzegorz Grzybek commented on CAMEL-13951:
--
The considered scenario is (which may be contested):
{code:xml}
http://camel.apache.org/...";>
...
{code}
where both {{}} and {{JdbcAggregationRepository}} use the same
Spring's PlatformTransactionmanager (which I don't think is ok, but that's the
case I worked on).
There are *two* possible solutions I've found.
h4. update count
{{org.springframework.jdbc.core.support.AbstractLobCreatingPreparedStatementCallback}}
is a creator templated by {{Integer}} returning number of affected (for INSERT
- inserted) rows using {{java.sql.PreparedStatement#executeUpdate()}}.
PosrgreSQL (I'm not sure if it's standard) [has this neat clause for INSERT
INTO
statement|https://www.depesz.com/2015/05/10/waiting-for-9-5-add-support-for-insert-on-conflict-do-nothingupdate/]
that allows us to do:
{code:sql}
insert into aggregation (id, exchange) values (?, ?) on conflict do nothing
{code}
Using this statement, instead of getting SQLState 23505, which makes connection
(and transaction) effectively unusable under PostgreSQL, we could return {{0}}
from
{{org.apache.camel.processor.aggregate.jdbc.JdbcAggregationRepository#insert()}}
and handle optimistic locking scenario.
This would require only to add {{ON CONFLICT DO NOTHING}} to the generated SQL.
Of course on DERBY (using in camel-sql tests), we're getting:
{noformat}
Caused by: ERROR 42X01: Syntax error: Encountered "ON" at line 1, column 58.
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at
org.apache.derby.impl.sql.compile.ParserImpl.parseStatementOrSearchCondition(Unknown
Source)
at org.apache.derby.impl.sql.compile.ParserImpl.parseStatement(Unknown
Source)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source)
at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source)
at
org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown
Source)
... 67 more
{noformat}
h4. nested transaction
{{org.apache.camel.processor.aggregate.jdbc.JdbcAggregationRepository}} uses
*two* instances of
{{org.springframework.transaction.support.TransactionTemplate}}:
* read only called in
{{org.apache.camel.processor.aggregate.jdbc.JdbcAggregationRepository#get()}}
* read-write called in {{add()}}, {{remove()}} and {{confirm()}}
*if* the transaction template used in {{add()}} used
{{org.springframework.transaction.TransactionDefinition#PROPAGATION_NESTED}}
instead of
{{org.springframework.transaction.TransactionDefinition#PROPAGATION_REQUIRED}},
nested transaction used by {{add()}} would be rolled back upon SQLState=23505
and {{org.springframework.dao.DuplicateKeyException}} would cause:
{code:java}
org.springframework.transaction.support.AbstractTransactionStatus#rollbackToHeldSavepoint()
...
java.sql.Connection#rollback(java.sql.Savepoint)
{code}
instead of
{code:java}
org.springframework.transaction.support.AbstractPlatformTransactionManager#doRollback()
...
java.sql.Connection#rollback()
{code}
then,
{{org.apache.camel.processor.aggregate.jdbc.DefaultJdbcOptimisticLockingExceptionMapper#isOptimisticLocking()}}
would still return {{true}} because error propagation wouldn't be affected.
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Sprin
[jira] [Commented] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924020#comment-16924020
]
Guillaume Nodet commented on CAMEL-13950:
-
What about adding a {{RestRouteBuilder}} which would extend the existing
{{RouteBuilder}}, adding those methods as shortcuts ?
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924017#comment-16924017
]
Luca Burgazzoli commented on CAMEL-13950:
-
oh yes, maybe was not so clear (as usual). I do not want to remove what we
have, just add some syntactic sugar in the context of the endpoint dsl, maybe
targeting the rest component itself
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924016#comment-16924016
]
Claus Ibsen commented on CAMEL-13950:
-
Yeah but its a special DSL for Java only.
The route model is 99% identical between java and xml and others. And so should
the Rest DSL.
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Assigned] (CAMEL-13851) camel-xj component contribution
[ https://issues.apache.org/jira/browse/CAMEL-13851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13851: Assignee: Andrea Cosentino > camel-xj component contribution > --- > > Key: CAMEL-13851 > URL: https://issues.apache.org/jira/browse/CAMEL-13851 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.24.1, 3.0.0.M4 >Reporter: Marc Giger >Assignee: Andrea Cosentino >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Hi, > For a customer of mine i've setup an ESB infrastructure (JBoss Fuse) and > implement camel routes for some time now. Until now i've used camel-xmljson > that was nicely expressed "not so nice". It was always a pain to get the > desired output and needed most of the time some hacks. Lately we had some > performance issues with "larger" messages and the culprit was again the > xmljson lib because of its excessive regex use. Apart from that camel-xmljson > was removed from camel (correctly). So, time for a new component for direct > xml <-> json conversion. > Thanks goes to "Berner Fachhochschule" to allow me to work and contribute the > component. > On a high level the component works as follows: > xml -> xslt -> json and json -> xslt -> xml > This allows to transform the input document directly in the desired target > structure without the need of an intermediary format. > More in detail: > xml -> xslt -> XmlJsonStreamWriter -> json > The XmlJsonStreamWriter is a custom impl. of javax.xml.stream.XMLStreamWriter > that acts as a StAX -> JsonEvent bridge and uses internally > com.fasterxml.jackson.core.JsonGenerator as json writer. > In the other direction: > json -> JsonXmlStreamReader -> xslt -> xml > Here the JsonXmlStreamReader is a custom impl. of > avax.xml.stream.XMLStreamReader that acts as a JsonEvent -> StAX bridge and > uses internally com.fasterxml.jackson.core.JsonParser as json reader. > The json -> xml conversion is fully event driven. That means that just the > current token is held in memory. In the other direction, xml -> json, a > internal tree needs to be built and therefore the complete json document is > held in memory. Actually I can even see a possibility to stream it under some > circumstandes. > The current implementation can be found in: > https://github.com/kayuma/camel/tree/camel-xj-component > The question is now if the camel community is interested in this contribution? > Open Issues: > - Some of the classes are copies from the xslt component because of minor but > important differences that are required to get XJ to work. Maybe we should > refactor the xslt component so that it may be extended? Advice needed. > - Documentation > And in the end it would be very nice, if the contribution is accepted, if it > could be backported and integrated into camel 2.x > Thanks, > Marc -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13851) camel-xj component contribution
[ https://issues.apache.org/jira/browse/CAMEL-13851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13851: - Fix Version/s: 3.0.0.RC2 > camel-xj component contribution > --- > > Key: CAMEL-13851 > URL: https://issues.apache.org/jira/browse/CAMEL-13851 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.24.1, 3.0.0.M4 >Reporter: Marc Giger >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC2 > > Time Spent: 10m > Remaining Estimate: 0h > > Hi, > For a customer of mine i've setup an ESB infrastructure (JBoss Fuse) and > implement camel routes for some time now. Until now i've used camel-xmljson > that was nicely expressed "not so nice". It was always a pain to get the > desired output and needed most of the time some hacks. Lately we had some > performance issues with "larger" messages and the culprit was again the > xmljson lib because of its excessive regex use. Apart from that camel-xmljson > was removed from camel (correctly). So, time for a new component for direct > xml <-> json conversion. > Thanks goes to "Berner Fachhochschule" to allow me to work and contribute the > component. > On a high level the component works as follows: > xml -> xslt -> json and json -> xslt -> xml > This allows to transform the input document directly in the desired target > structure without the need of an intermediary format. > More in detail: > xml -> xslt -> XmlJsonStreamWriter -> json > The XmlJsonStreamWriter is a custom impl. of javax.xml.stream.XMLStreamWriter > that acts as a StAX -> JsonEvent bridge and uses internally > com.fasterxml.jackson.core.JsonGenerator as json writer. > In the other direction: > json -> JsonXmlStreamReader -> xslt -> xml > Here the JsonXmlStreamReader is a custom impl. of > avax.xml.stream.XMLStreamReader that acts as a JsonEvent -> StAX bridge and > uses internally com.fasterxml.jackson.core.JsonParser as json reader. > The json -> xml conversion is fully event driven. That means that just the > current token is held in memory. In the other direction, xml -> json, a > internal tree needs to be built and therefore the complete json document is > held in memory. Actually I can even see a possibility to stream it under some > circumstandes. > The current implementation can be found in: > https://github.com/kayuma/camel/tree/camel-xj-component > The question is now if the camel community is interested in this contribution? > Open Issues: > - Some of the classes are copies from the xslt component because of minor but > important differences that are required to get XJ to work. Maybe we should > refactor the xslt component so that it may be extended? Advice needed. > - Documentation > And in the end it would be very nice, if the contribution is accepted, if it > could be backported and integrated into camel 2.x > Thanks, > Marc -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (CAMEL-13851) camel-xj component contribution
[ https://issues.apache.org/jira/browse/CAMEL-13851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13851. -- Resolution: Fixed > camel-xj component contribution > --- > > Key: CAMEL-13851 > URL: https://issues.apache.org/jira/browse/CAMEL-13851 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.24.1, 3.0.0.M4 >Reporter: Marc Giger >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC2 > > Time Spent: 10m > Remaining Estimate: 0h > > Hi, > For a customer of mine i've setup an ESB infrastructure (JBoss Fuse) and > implement camel routes for some time now. Until now i've used camel-xmljson > that was nicely expressed "not so nice". It was always a pain to get the > desired output and needed most of the time some hacks. Lately we had some > performance issues with "larger" messages and the culprit was again the > xmljson lib because of its excessive regex use. Apart from that camel-xmljson > was removed from camel (correctly). So, time for a new component for direct > xml <-> json conversion. > Thanks goes to "Berner Fachhochschule" to allow me to work and contribute the > component. > On a high level the component works as follows: > xml -> xslt -> json and json -> xslt -> xml > This allows to transform the input document directly in the desired target > structure without the need of an intermediary format. > More in detail: > xml -> xslt -> XmlJsonStreamWriter -> json > The XmlJsonStreamWriter is a custom impl. of javax.xml.stream.XMLStreamWriter > that acts as a StAX -> JsonEvent bridge and uses internally > com.fasterxml.jackson.core.JsonGenerator as json writer. > In the other direction: > json -> JsonXmlStreamReader -> xslt -> xml > Here the JsonXmlStreamReader is a custom impl. of > avax.xml.stream.XMLStreamReader that acts as a JsonEvent -> StAX bridge and > uses internally com.fasterxml.jackson.core.JsonParser as json reader. > The json -> xml conversion is fully event driven. That means that just the > current token is held in memory. In the other direction, xml -> json, a > internal tree needs to be built and therefore the complete json document is > held in memory. Actually I can even see a possibility to stream it under some > circumstandes. > The current implementation can be found in: > https://github.com/kayuma/camel/tree/camel-xj-component > The question is now if the camel community is interested in this contribution? > Open Issues: > - Some of the classes are copies from the xslt component because of minor but > important differences that are required to get XJ to work. Maybe we should > refactor the xslt component so that it may be extended? Advice needed. > - Documentation > And in the end it would be very nice, if the contribution is accepted, if it > could be backported and integrated into camel 2.x > Thanks, > Marc -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924012#comment-16924012
]
Luca Burgazzoli commented on CAMEL-13950:
-
isn't that similar to what the endpoint dsl does ?
{code:java}
var timer = timer("");
from(timer).to()
{code}
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13951:
Issue Type: Improvement (was: Bug)
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924002#comment-16924002
]
Claus Ibsen commented on CAMEL-13951:
-
I dont see this as a bug as its some postgres problem. So changing the type
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Bug
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924000#comment-16924000
]
Claus Ibsen commented on CAMEL-13950:
-
Hmm we dont really use variables and splitup. Also mind that we should ideally
have the Java and XML DSL similar (and also other DSLs like YAML etc) as the
Java DSL can get too far away from these others. eg we already got some of that
in Camel 2.x and have some "tricks" to fixup this.
So what I am saying is that a get method does not tell me that its rest or
something, its not HTTP GET or REST GET or something, but just get. And that
can mean anything, eg like a getter.
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923995#comment-16923995
]
Grzegorz Grzybek edited comment on CAMEL-13951 at 9/6/19 7:38 AM:
--
Here's the unit test that shows the problem:
{code:java}
@Test
public void optimisticLocking() throws Exception {
BasicDataSource pool = new org.apache.commons.dbcp2.BasicDataSource();
pool.setUrl("jdbc:postgresql://localhost:5432/reportdb");
pool.setUsername("admin");
pool.setPassword("admin);
pool.setMinIdle(2);
pool.setMaxTotal(10);
DataSource ds = pool;
PlatformTransactionManager ptm = new DataSourceTransactionManager(ds);
DefaultTransactionDefinition routeDef = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_REQUIRED);
routeDef.setReadOnly(false);
TransactionTemplate route = new TransactionTemplate(ptm, routeDef);
DefaultTransactionDefinition aggregationDefAdd = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_REQUIRED);
aggregationDefAdd.setReadOnly(false);
TransactionTemplate aggregationAdd = new TransactionTemplate(ptm,
aggregationDefAdd);
DefaultTransactionDefinition aggregationDefGet = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_REQUIRED);
aggregationDefGet.setReadOnly(true);
TransactionTemplate aggregationGet = new TransactionTemplate(ptm,
aggregationDefGet);
JdbcTemplate jdbc = new JdbcTemplate(ds);
route.execute(status1 -> {
jdbc.query("select messagetext from message", rs -> {
LOG.info("message fetched in external tt: " + rs.getString(1));
});
try {
aggregationAdd.execute(status2 -> {
int count = jdbc.update("insert into aggregation (id, exchange)
values (?, ?)", "1", "2".getBytes(StandardCharsets.UTF_8));
LOG.info("Count: {}", count);
return null;
});
} catch (DuplicateKeyException e) {
LOG.warn("Expected DuplicateKeyException: {}", e.getMessage(), e);
SQLException sqle = (SQLException) e.getCause();
LOG.warn("State: {}, code: {}", sqle.getSQLState(),
sqle.getErrorCode());
}
aggregationGet.execute(status2 -> {
jdbc.query("select messagetext from message", rs -> {
LOG.info("message fetched in internal tt: " + rs.getString(1));
});
return null;
});
return null;
});
}
{code}
was (Author: gzres):
Here's the unit test that shows the problem:
{code:java}
@Test
public void optimisticLocking() throws Exception {
BasicDataSource pool = new org.apache.commons.dbcp2.BasicDataSource();
pool.setUrl("jdbc:postgresql://localhost:5432/reportdb");
pool.setUsername("admin");
pool.setPassword("admin);
pool.setMinIdle(2);
pool.setMaxTotal(10);
DataSource ds = pool;
PlatformTransactionManager ptm = new DataSourceTransactionManager(ds);
DefaultTransactionDefinition routeDef = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_REQUIRED);
routeDef.setReadOnly(false);
TransactionTemplate route = new TransactionTemplate(ptm, routeDef);
//DefaultTransactionDefinition aggregationDefAdd = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_NESTED);
DefaultTransactionDefinition aggregationDefAdd = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_REQUIRED);
aggregationDefAdd.setReadOnly(false);
TransactionTemplate aggregationAdd = new TransactionTemplate(ptm,
aggregationDefAdd);
DefaultTransactionDefinition aggregationDefGet = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_REQUIRED);
aggregationDefGet.setReadOnly(true);
TransactionTemplate aggregationGet = new TransactionTemplate(ptm,
aggregationDefGet);
JdbcTemplate jdbc = new JdbcTemplate(ds);
//
route.execute(status1 -> {
jdbc.query("select messagetext from message", rs -> {
LOG.info("message fetched in external tt: " + rs.getString(1));
});
try {
aggregationAdd.execute(status2 -> {
int count = jdbc.update("insert into aggregation (id, exchange)
values (?, ?)", "1", "2".getBytes(StandardCharsets.UTF_8));
//int count = jdbc.update("insert into aggregation (id,
exchange) values (?, ?) on conflict do nothing", "1",
"2".getBytes(StandardCharsets.UTF_8));
LOG.info("Count: {}", count);
return null;
});
} catch (DuplicateKeyException e) {
LOG.warn("Expected DuplicateKeyException: {}", e.getMessage(), e);
SQLException sqle = (SQLException) e.getCause();
LOG.warn("State: {}, code: {}", sqle.getSQLState(),
sqle.getErrorCode());
}
ag
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923995#comment-16923995
]
Grzegorz Grzybek commented on CAMEL-13951:
--
Here's the unit test that shows the problem:
{code:java}
@Test
public void optimisticLocking() throws Exception {
BasicDataSource pool = new org.apache.commons.dbcp2.BasicDataSource();
pool.setUrl("jdbc:postgresql://localhost:5432/reportdb");
pool.setUsername("admin");
pool.setPassword("admin);
pool.setMinIdle(2);
pool.setMaxTotal(10);
DataSource ds = pool;
PlatformTransactionManager ptm = new DataSourceTransactionManager(ds);
DefaultTransactionDefinition routeDef = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_REQUIRED);
routeDef.setReadOnly(false);
TransactionTemplate route = new TransactionTemplate(ptm, routeDef);
//DefaultTransactionDefinition aggregationDefAdd = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_NESTED);
DefaultTransactionDefinition aggregationDefAdd = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_REQUIRED);
aggregationDefAdd.setReadOnly(false);
TransactionTemplate aggregationAdd = new TransactionTemplate(ptm,
aggregationDefAdd);
DefaultTransactionDefinition aggregationDefGet = new
DefaultTransactionDefinition(TransactionDefinition.PROPAGATION_REQUIRED);
aggregationDefGet.setReadOnly(true);
TransactionTemplate aggregationGet = new TransactionTemplate(ptm,
aggregationDefGet);
JdbcTemplate jdbc = new JdbcTemplate(ds);
//
route.execute(status1 -> {
jdbc.query("select messagetext from message", rs -> {
LOG.info("message fetched in external tt: " + rs.getString(1));
});
try {
aggregationAdd.execute(status2 -> {
int count = jdbc.update("insert into aggregation (id, exchange)
values (?, ?)", "1", "2".getBytes(StandardCharsets.UTF_8));
//int count = jdbc.update("insert into aggregation (id,
exchange) values (?, ?) on conflict do nothing", "1",
"2".getBytes(StandardCharsets.UTF_8));
LOG.info("Count: {}", count);
return null;
});
} catch (DuplicateKeyException e) {
LOG.warn("Expected DuplicateKeyException: {}", e.getMessage(), e);
SQLException sqle = (SQLException) e.getCause();
LOG.warn("State: {}, code: {}", sqle.getSQLState(),
sqle.getErrorCode());
}
aggregationGet.execute(status2 -> {
jdbc.query("select messagetext from message", rs -> {
LOG.info("message fetched in internal tt: " + rs.getString(1));
});
return null;
});
return null;
});
}
{code}
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Bug
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) beha
[jira] [Commented] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923997#comment-16923997
]
Luca Burgazzoli commented on CAMEL-13950:
-
Yep but now you can already do
{code}
rest().get(...).to("")
{code}
So maybe something like:
{code}
var api = .get(...).accept();
from(api).to()
{code}
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
[
https://issues.apache.org/jira/browse/CAMEL-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923993#comment-16923993
]
Grzegorz Grzybek commented on CAMEL-13951:
--
https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
says about an option to control the behavior, but it's not for
default/official PostgreSQL JDBC driver.
> JdbcAggregationRepository doesn't work with PostgreSQL
> --
>
> Key: CAMEL-13951
> URL: https://issues.apache.org/jira/browse/CAMEL-13951
> Project: Camel
> Issue Type: Bug
> Components: camel-sql
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> See:
> *
> https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
> *
> https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
> *
> https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
> The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
> throwing org.springframework.dao.DataIntegrityViolationException according to
> its sql exception mapping.
> By default, DataIntegrityViolationException is thrown if SQLState starts with
> {{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and
> see that:
> bq. 23505: unique_violation
> The _problem_ specific to PostgreSQL is that hitting such exception makes the
> connection (and surrounding Spring transaction) unusable. There's no way to
> _repeat_ an attempt to insert (or even check current) state of aggregation,
> because PostgreSQL will immediately throw:
> {noformat}
> Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
> ...
> {noformat}
> With SQLState - {{25P02}} == "in_failed_sql_transaction".
> The expected (by PostgreSQL) behavior is to rollback current transaction and
> start over.
> We're however in (potentially nested) TransactionTemplate and _rollback only_
> status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (CAMEL-13951) JdbcAggregationRepository doesn't work with PostgreSQL
Grzegorz Grzybek created CAMEL-13951:
Summary: JdbcAggregationRepository doesn't work with PostgreSQL
Key: CAMEL-13951
URL: https://issues.apache.org/jira/browse/CAMEL-13951
Project: Camel
Issue Type: Bug
Components: camel-sql
Affects Versions: 3.0.0.RC1, 2.24.1
Reporter: Grzegorz Grzybek
Assignee: Grzegorz Grzybek
See:
*
https://www.postgresql.org/message-id/200609241203.59292.ralf.wiebicke%40exedio.com
*
https://groups.google.com/forum/#!msg/comp.databases.postgresql/NuXGXdFbA4g/LQ97ahowmxkJ
*
https://www.progress.com/blogs/solution-to-current-transaction-is-aborted-error-for-postgresql-compatibility-with-odbc-jdbc
The problem is that JdbcAggregationRepository relies heavily on spring-jdbc's
throwing org.springframework.dao.DataIntegrityViolationException according to
its sql exception mapping.
By default, DataIntegrityViolationException is thrown if SQLState starts with
{{23}}. Check https://www.postgresql.org/docs/10/errcodes-appendix.html and see
that:
bq. 23505: unique_violation
The _problem_ specific to PostgreSQL is that hitting such exception makes the
connection (and surrounding Spring transaction) unusable. There's no way to
_repeat_ an attempt to insert (or even check current) state of aggregation,
because PostgreSQL will immediately throw:
{noformat}
Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is
aborted, commands ignored until end of transaction block
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
...
{noformat}
With SQLState - {{25P02}} == "in_failed_sql_transaction".
The expected (by PostgreSQL) behavior is to rollback current transaction and
start over.
We're however in (potentially nested) TransactionTemplate and _rollback only_
status is beyond (easy) control.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13919) "camel-package:update-readme" throws ArrayIndexOutOfBoundsException when there is an empty "adoc" file
[
https://issues.apache.org/jira/browse/CAMEL-13919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13919.
-
Assignee: Claus Ibsen
Resolution: Fixed
Thanks for the PR
> "camel-package:update-readme" throws ArrayIndexOutOfBoundsException when
> there is an empty "adoc" file
> --
>
> Key: CAMEL-13919
> URL: https://issues.apache.org/jira/browse/CAMEL-13919
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 3.0.0.M4
>Reporter: Omar Al-Safi
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Steps to produce:
> * Create an empty {{adoc}} file in any component.
> * Run {{camel-package:update-readme}}.
> * It will fail with the following error:
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds
> for length 1
> at org.apache.camel.maven.packaging.UpdateReadmeMojo.updateAvailableFrom
> (UpdateReadmeMojo.java:510)
> at org.apache.camel.maven.packaging.UpdateReadmeMojo.executeComponent
> (UpdateReadmeMojo.java:151)
> at org.apache.camel.maven.packaging.UpdateReadmeMojo.execute
> (UpdateReadmeMojo.java:105)
> {code}
> * As I can see
> [here|https://github.com/apache/camel/blob/master/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/UpdateReadmeMojo.java#L510],
> it looks it will try to retrieve index although there are empty lines
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (CAMEL-13919) "camel-package:update-readme" throws ArrayIndexOutOfBoundsException when there is an empty "adoc" file
[
https://issues.apache.org/jira/browse/CAMEL-13919?focusedWorklogId=307675&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-307675
]
ASF GitHub Bot logged work on CAMEL-13919:
--
Author: ASF GitHub Bot
Created on: 06/Sep/19 07:35
Start Date: 06/Sep/19 07:35
Worklog Time Spent: 10m
Work Description: davsclaus commented on pull request #3148: MINOR:
CAMEL-13919: Fix ArrayIndexOutOfBoundsException when generate readme …
URL: https://github.com/apache/camel/pull/3148
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: 307675)
Time Spent: 20m (was: 10m)
> "camel-package:update-readme" throws ArrayIndexOutOfBoundsException when
> there is an empty "adoc" file
> --
>
> Key: CAMEL-13919
> URL: https://issues.apache.org/jira/browse/CAMEL-13919
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 3.0.0.M4
>Reporter: Omar Al-Safi
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Steps to produce:
> * Create an empty {{adoc}} file in any component.
> * Run {{camel-package:update-readme}}.
> * It will fail with the following error:
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds
> for length 1
> at org.apache.camel.maven.packaging.UpdateReadmeMojo.updateAvailableFrom
> (UpdateReadmeMojo.java:510)
> at org.apache.camel.maven.packaging.UpdateReadmeMojo.executeComponent
> (UpdateReadmeMojo.java:151)
> at org.apache.camel.maven.packaging.UpdateReadmeMojo.execute
> (UpdateReadmeMojo.java:105)
> {code}
> * As I can see
> [here|https://github.com/apache/camel/blob/master/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/UpdateReadmeMojo.java#L510],
> it looks it will try to retrieve index although there are empty lines
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923989#comment-16923989
]
Claus Ibsen commented on CAMEL-13950:
-
Hmm I do think actually routes should always have started with route, instead
of just from
And therefore also rest should start from rest.
As a
get("foo").to("jms:bar")
Is not obvious what it really is
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13949) camel-core vs camel-core-engine
[ https://issues.apache.org/jira/browse/CAMEL-13949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13949: Priority: Major (was: Minor) > camel-core vs camel-core-engine > --- > > Key: CAMEL-13949 > URL: https://issues.apache.org/jira/browse/CAMEL-13949 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-core-engine >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > The camel-core-engine trims camel-core using maven exclusions which may lead > to unexpected result as if both are present in the dependencies tree, then > one may win over the other depending of the maven resolution. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13949) camel-core vs camel-core-engine
[ https://issues.apache.org/jira/browse/CAMEL-13949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923988#comment-16923988 ] Claus Ibsen commented on CAMEL-13949: - GNodet, yeah that would be a good idea. However camel-core we may need to have some dummy class or something as it should still be a JAR as that is what it is in Camel 2.x. And we also have camel-core test JAR that camel-spring and a few others uses for testing. > camel-core vs camel-core-engine > --- > > Key: CAMEL-13949 > URL: https://issues.apache.org/jira/browse/CAMEL-13949 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-core-engine >Reporter: Luca Burgazzoli >Priority: Minor > > The camel-core-engine trims camel-core using maven exclusions which may lead > to unexpected result as if both are present in the dependencies tree, then > one may win over the other depending of the maven resolution. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13950) better endpointdsl for rest
[
https://issues.apache.org/jira/browse/CAMEL-13950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13950:
Component/s: rest
> better endpointdsl for rest
> ---
>
> Key: CAMEL-13950
> URL: https://issues.apache.org/jira/browse/CAMEL-13950
> Project: Camel
> Issue Type: Improvement
> Components: rest
>Reporter: Luca Burgazzoli
>Priority: Minor
>
> We should have a better "fluent dsl" for rest services, as today we have
> something like
> {code:java}
> rest("/v1").get("/api").to(""...)
> {code}
> It would be nice to simplify this by having an option to start from the
> method like:
> {code:java}
> get("/api")
> .accept("...")
> .to("...")
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13949) camel-core vs camel-core-engine
[ https://issues.apache.org/jira/browse/CAMEL-13949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13949: Fix Version/s: 3.0.0.RC2 3.0.0 > camel-core vs camel-core-engine > --- > > Key: CAMEL-13949 > URL: https://issues.apache.org/jira/browse/CAMEL-13949 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-core-engine >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0, 3.0.0.RC2 > > > The camel-core-engine trims camel-core using maven exclusions which may lead > to unexpected result as if both are present in the dependencies tree, then > one may win over the other depending of the maven resolution. -- This message was sent by Atlassian Jira (v8.3.2#803003)
