[jira] [Updated] (CAMEL-13429) Rest DSL - Allow templating path parameters
[
https://issues.apache.org/jira/browse/CAMEL-13429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Istomin updated CAMEL-13429:
--
Fix Version/s: (was: 3.x)
3.0.0.RC1
3.0.0
Summary: Rest DSL - Allow templating path parameters (was: Rest DSL
- Allow dot as separator for path parameters)
> Rest DSL - Allow templating path parameters
> ---
>
> Key: CAMEL-13429
> URL: https://issues.apache.org/jira/browse/CAMEL-13429
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, rest
>Affects Versions: 3.0.0-M1
>Reporter: Arian Treffer
>Assignee: Denis Istomin
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.RC1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following route configuration should accept the "content-type" parameter
> as one would expect for URLs like "items/1/details.xml":
> {code:java}
> rest("items/")
> .get("{id}/details.{content-type}"){code}
> Currently, "content-type" is not recognized as a parameter.
>
> Maybe other separators, e.g. dash "-", should be supported as well.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13429) Rest DSL - Allow templating path parameters
[
https://issues.apache.org/jira/browse/CAMEL-13429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Istomin resolved CAMEL-13429.
---
Resolution: Fixed
> Rest DSL - Allow templating path parameters
> ---
>
> Key: CAMEL-13429
> URL: https://issues.apache.org/jira/browse/CAMEL-13429
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, rest
>Affects Versions: 3.0.0-M1
>Reporter: Arian Treffer
>Assignee: Denis Istomin
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.RC1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following route configuration should accept the "content-type" parameter
> as one would expect for URLs like "items/1/details.xml":
> {code:java}
> rest("items/")
> .get("{id}/details.{content-type}"){code}
> Currently, "content-type" is not recognized as a parameter.
>
> Maybe other separators, e.g. dash "-", should be supported as well.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (CAMEL-13429) Rest DSL - Allow dot as separator for path parameters
[
https://issues.apache.org/jira/browse/CAMEL-13429?focusedWorklogId=300499&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-300499
]
ASF GitHub Bot logged work on CAMEL-13429:
--
Author: ASF GitHub Bot
Created on: 23/Aug/19 20:45
Start Date: 23/Aug/19 20:45
Worklog Time Spent: 10m
Work Description: DenisIstomin commented on pull request #3120:
CAMEL-13429: Support expressions in path parameters at REST DSL
URL: https://github.com/apache/camel/pull/3120
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: 300499)
Time Spent: 20m (was: 10m)
> Rest DSL - Allow dot as separator for path parameters
> -
>
> Key: CAMEL-13429
> URL: https://issues.apache.org/jira/browse/CAMEL-13429
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, rest
>Affects Versions: 3.0.0-M1
>Reporter: Arian Treffer
>Assignee: Denis Istomin
>Priority: Minor
> Fix For: 3.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following route configuration should accept the "content-type" parameter
> as one would expect for URLs like "items/1/details.xml":
> {code:java}
> rest("items/")
> .get("{id}/details.{content-type}"){code}
> Currently, "content-type" is not recognized as a parameter.
>
> Maybe other separators, e.g. dash "-", should be supported as well.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13904) JMX - Early registered services may not be enlisted in XML DSL
[ https://issues.apache.org/jira/browse/CAMEL-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13904. - Resolution: Fixed > JMX - Early registered services may not be enlisted in XML DSL > -- > > Key: CAMEL-13904 > URL: https://issues.apache.org/jira/browse/CAMEL-13904 > Project: Camel > Issue Type: Bug > Components: camel-blueprint, camel-spring, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > In some use-cases depending on how you run Camel then some early services for > JMX may not get registered -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13870) camel3 - Fast configuring of endpoint options
[ https://issues.apache.org/jira/browse/CAMEL-13870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911236#comment-16911236 ] Claus Ibsen edited comment on CAMEL-13870 at 8/23/19 7:56 PM: -- TODOs - Endpoints with missing getter/setter paris *DONE* - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) *DONE* - Dynamic properties via multi valued and property prefix would still be reflection based (httpClient.xxx=aaa&httpClient.yyy=bbb) - Consider remove support for consumer.xxx as we dont really need this anymore - Allow to turn this on|off per endpoint so component developers can opt out *DONE* - Setting boolean should restrict to true|false string values *DONE* - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* - Fix camel-jetty as it has some "oddities" *DONE* - Fix camel-atomix as it has some "oddities" *DONE* - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" *DONE* - Fix camel-irc60870 as it has some "oddities" *DONE* - Fix camel-spring-ws as it has some "oddities" *DONE* - Fix camel-log as it has some "oddities" *DONE* - Rename apt json metadata to use configurationClassName instead of nested naming *DONE* - Omit getters as we dont need them for setting fast properties *DONE* - Fix camel-log so we use fast configurs for the log formatter options (its coded in a special way) *DONE* - Consider a way of gather usage statistics of introspection usage so we can find out how much reflection discovery we do with Camel *DONE* - fix camel-activemq / camel-amqp which should reuse camel-jms configurer *DONE* - make endpoint configurer map of options static and use 3-arg functional consumer for the writer. *DONE* - camel-hdfs test failure *DONE* - use mandatoryConvertTo *DONE* - camel-mllp has some issues so it wont generate fast configurers at this time - endpoint configurer classes can init their maps in class init instead of constructor was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris *DONE* - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) *DONE* - Dynamic properties via multi valued and property prefix would still be reflection based (httpClient.xxx=aaa&httpClient.yyy=bbb) - Consider remove support for consumer.xxx as we dont really need this anymore - Allow to turn this on|off per endpoint so component developers can opt out *DONE* - Setting boolean should restrict to true|false string values *DONE* - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* - Fix camel-jetty as it has some "oddities" *DONE* - Fix camel-atomix as it has some "oddities" *DONE* - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" *DONE* - Fix camel-irc60870 as it has some "oddities" *DONE* - Fix camel-spring-ws as it has some "oddities" *DONE* - Fix camel-log as it has some "oddities" *DONE* - Rename apt json metadata to use configurationClassName instead of nested naming *DONE* - Omit getters as we dont need them for setting fast properties *DONE* - Fix camel-log so we use fast configurs for the log formatter options (its coded in a special way) *DONE* - Consider a way of gather usage statistics of introspection usage so we can find out how much reflection discovery we do with Camel *DONE* - fix camel-activemq / camel-amqp which should reuse camel-jms configurer *DONE* - make endpoint configurer map of options static and use 3-arg functional consumer for the writer. *DONE* - camel-hdfs test failure *DONE* - use mandatoryConvertTo *DONE* - camel-mllp has some issues so it wont generate fast configurers at this time > camel3 - Fast configuring of endpoint options > - > > Key: CAMEL-13870 > URL: https://issues.apache.org/jira/browse/CAMEL-13870 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > Like we did for fast property placeholders on EIPs we can optimize endpoints > as well, by using the apt compiler plugin to generate a configurer classes > that uses direct java method invocations and then the property builder > support class can detect that we have such a configurer and use it, when it > looks for the setter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13904) JMX - Early registered services may not be enlisted in XML DSL
[ https://issues.apache.org/jira/browse/CAMEL-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13904: Summary: JMX - Early registered services may not be enlisted in XML DSL (was: JMX - Early registered services may not be enlisted) > JMX - Early registered services may not be enlisted in XML DSL > -- > > Key: CAMEL-13904 > URL: https://issues.apache.org/jira/browse/CAMEL-13904 > Project: Camel > Issue Type: Bug > Components: jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > In some use-cases depending on how you run Camel then some early services for > JMX may not get registered -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13904) JMX - Early registered services may not be enlisted in XML DSL
[ https://issues.apache.org/jira/browse/CAMEL-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13904: Component/s: camel-spring camel-blueprint > JMX - Early registered services may not be enlisted in XML DSL > -- > > Key: CAMEL-13904 > URL: https://issues.apache.org/jira/browse/CAMEL-13904 > Project: Camel > Issue Type: Bug > Components: camel-blueprint, camel-spring, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > In some use-cases depending on how you run Camel then some early services for > JMX may not get registered -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (CAMEL-13904) JMX - Early registered services may not be enlisted
Claus Ibsen created CAMEL-13904: --- Summary: JMX - Early registered services may not be enlisted Key: CAMEL-13904 URL: https://issues.apache.org/jira/browse/CAMEL-13904 Project: Camel Issue Type: Bug Components: jmx Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.0.0, 3.0.0.RC1 In some use-cases depending on how you run Camel then some early services for JMX may not get registered -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13870) camel3 - Fast configuring of endpoint options
[ https://issues.apache.org/jira/browse/CAMEL-13870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911236#comment-16911236 ] Claus Ibsen edited comment on CAMEL-13870 at 8/23/19 5:20 PM: -- TODOs - Endpoints with missing getter/setter paris *DONE* - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) *DONE* - Dynamic properties via multi valued and property prefix would still be reflection based (httpClient.xxx=aaa&httpClient.yyy=bbb) - Consider remove support for consumer.xxx as we dont really need this anymore - Allow to turn this on|off per endpoint so component developers can opt out *DONE* - Setting boolean should restrict to true|false string values *DONE* - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* - Fix camel-jetty as it has some "oddities" *DONE* - Fix camel-atomix as it has some "oddities" *DONE* - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" *DONE* - Fix camel-irc60870 as it has some "oddities" *DONE* - Fix camel-spring-ws as it has some "oddities" *DONE* - Fix camel-log as it has some "oddities" *DONE* - Rename apt json metadata to use configurationClassName instead of nested naming *DONE* - Omit getters as we dont need them for setting fast properties *DONE* - Fix camel-log so we use fast configurs for the log formatter options (its coded in a special way) *DONE* - Consider a way of gather usage statistics of introspection usage so we can find out how much reflection discovery we do with Camel *DONE* - fix camel-activemq / camel-amqp which should reuse camel-jms configurer *DONE* - make endpoint configurer map of options static and use 3-arg functional consumer for the writer. *DONE* - camel-hdfs test failure *DONE* - use mandatoryConvertTo *DONE* - camel-mllp has some issues so it wont generate fast configurers at this time was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris *DONE* - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) *DONE* - Dynamic properties via multi valued and property prefix would still be reflection based (httpClient.xxx=aaa&httpClient.yyy=bbb) - Consider remove support for consumer.xxx as we dont really need this anymore - Allow to turn this on|off per endpoint so component developers can opt out *DONE* - Setting boolean should restrict to true|false string values *DONE* - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* - Fix camel-jetty as it has some "oddities" *DONE* - Fix camel-atomix as it has some "oddities" *DONE* - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" *DONE* - Fix camel-irc60870 as it has some "oddities" *DONE* - Fix camel-spring-ws as it has some "oddities" *DONE* - Fix camel-log as it has some "oddities" *DONE* - Rename apt json metadata to use configurationClassName instead of nested naming *DONE* - Omit getters as we dont need them for setting fast properties *DONE* - Fix camel-log so we use fast configurs for the log formatter options (its coded in a special way) *DONE* - Consider a way of gather usage statistics of introspection usage so we can find out how much reflection discovery we do with Camel *DONE* - fix camel-activemq / camel-amqp which should reuse camel-jms configurer *DONE* - make endpoint configurer map of options static and use 3-arg functional consumer for the writer. - camel-hdfs test failure *DONE* - use mandatoryConvertTo *DONE* - camel-mllp has some issues so it wont generate fast configurers at this time > camel3 - Fast configuring of endpoint options > - > > Key: CAMEL-13870 > URL: https://issues.apache.org/jira/browse/CAMEL-13870 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > Like we did for fast property placeholders on EIPs we can optimize endpoints > as well, by using the apt compiler plugin to generate a configurer classes > that uses direct java method invocations and then the property builder > support class can detect that we have such a configurer and use it, when it > looks for the setter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13898) ensure camel-cxf consumer can propagate protocol headers from camel exchange headers when throwing a soap fault
[ https://issues.apache.org/jira/browse/CAMEL-13898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-13898: - Component/s: camel-cxf > ensure camel-cxf consumer can propagate protocol headers from camel exchange > headers when throwing a soap fault > --- > > Key: CAMEL-13898 > URL: https://issues.apache.org/jira/browse/CAMEL-13898 > Project: Camel > Issue Type: New Feature > Components: camel-cxf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC1 > > > to keep the same behavior as normal soap response -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (CAMEL-13891) camel-cxf - Add spring.schemas for -spring URL so it works for same online url
[ https://issues.apache.org/jira/browse/CAMEL-13891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13891. -- Resolution: Fixed > camel-cxf - Add spring.schemas for -spring URL so it works for same online url > -- > > Key: CAMEL-13891 > URL: https://issues.apache.org/jira/browse/CAMEL-13891 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Reporter: Claus Ibsen >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > https://github.com/apache/camel/blob/master/components/camel-cxf/src/main/resources/META-INF/spring.schemas > Should have 2x for each pair > http\://camel.apache.org/schema/cxf/camel-cxf-3.0.0-M3.xsd=schema/cxfEndpoint.xsd > http\://camel.apache.org/schema/cxf/camel-cxf-3.0.0-M3-spring.xsd=schema/cxfEndpoint.xsd > For all of them, as then we have for old and new locations (eg when we had > blueprint later) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (CAMEL-13876) enable camel-undertow component to set custom HttpHandler
[ https://issues.apache.org/jira/browse/CAMEL-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13876. -- Fix Version/s: 3.0.0.RC1 3.0.0 Resolution: Fixed > enable camel-undertow component to set custom HttpHandler > - > > Key: CAMEL-13876 > URL: https://issues.apache.org/jira/browse/CAMEL-13876 > Project: Camel > Issue Type: New Feature > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > such as security related undertow HttpHandlers -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (CAMEL-13898) ensure camel-cxf consumer can propagate protocol headers from camel exchange headers when throwing a soap fault
[ https://issues.apache.org/jira/browse/CAMEL-13898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13898. -- Fix Version/s: 3.0.0.RC1 2.25.0 2.24.2 2.23.4 3.0.0 Resolution: Fixed > ensure camel-cxf consumer can propagate protocol headers from camel exchange > headers when throwing a soap fault > --- > > Key: CAMEL-13898 > URL: https://issues.apache.org/jira/browse/CAMEL-13898 > Project: Camel > Issue Type: New Feature >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC1 > > > to keep the same behavior as normal soap response -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13903) Port telegram component to RestEasy
[ https://issues.apache.org/jira/browse/CAMEL-13903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914355#comment-16914355 ] Peter Palaga commented on CAMEL-13903: -- I agree this is not an issue from the Camel point of view. The issue exists solely on the side of Camel Quarkus, where the CXF REST client does not work out of the box in the native mode on Quarkus. The exact error messages can be seen in https://github.com/apache/camel-quarkus/issues/74 . Solving those issues in the CXF REST client is perhaps possible, but from our (camel-quarkus) point of view not preferred, because it is much more work than somehow switching the REST client implementation in the telegram component. So if simply replacing the CXF client with the RestEasy one does not find enough acceptance on the Camel side, let me try to find some other option and propose it here. > Port telegram component to RestEasy > --- > > Key: CAMEL-13903 > URL: https://issues.apache.org/jira/browse/CAMEL-13903 > Project: Camel > Issue Type: Wish > Components: camel-telegram >Reporter: Peter Palaga >Priority: Major > > This is motivated by our efforts to port the telegram component to Quarkus > where RestEasy is available out of the box. > https://github.com/apache/camel-quarkus/issues/74 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13903) Port telegram component to RestEasy
[ https://issues.apache.org/jira/browse/CAMEL-13903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914307#comment-16914307 ] Andrea Cosentino commented on CAMEL-13903: -- CXF is used a lot in Camel. So your question is not related to how much is controversial to eventually replace it with something else, the point is what are the technical reason to switch to resteasy and I don't see valid technical reason here. > Port telegram component to RestEasy > --- > > Key: CAMEL-13903 > URL: https://issues.apache.org/jira/browse/CAMEL-13903 > Project: Camel > Issue Type: Wish > Components: camel-telegram >Reporter: Peter Palaga >Priority: Major > > This is motivated by our efforts to port the telegram component to Quarkus > where RestEasy is available out of the box. > https://github.com/apache/camel-quarkus/issues/74 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13903) Port telegram component to RestEasy
[ https://issues.apache.org/jira/browse/CAMEL-13903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914300#comment-16914300 ] Andrea Cosentino commented on CAMEL-13903: -- This is not a bug. Camel-telegram works out of the box. The Quarkus effort is fine, but we can't do this kind of considerations for all the components. If it is something feasible to make it work on quarkus, ok, otherwise it won't be supported in Quarkus. Camel-quarkus is a subproject of Camel, not the Camel's reason for being. -1 for me. > Port telegram component to RestEasy > --- > > Key: CAMEL-13903 > URL: https://issues.apache.org/jira/browse/CAMEL-13903 > Project: Camel > Issue Type: Wish > Components: camel-telegram >Reporter: Peter Palaga >Priority: Major > > This is motivated by our efforts to port the telegram component to Quarkus > where RestEasy is available out of the box. > https://github.com/apache/camel-quarkus/issues/74 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13903) Port telegram component to RestEasy
[ https://issues.apache.org/jira/browse/CAMEL-13903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914298#comment-16914298 ] Peter Palaga commented on CAMEL-13903: -- I could eventually start working on this. But I am not sure how much is this feasible politically. Replacing CXF with a non ASF alternative might perhaps be seen as controversial? > Port telegram component to RestEasy > --- > > Key: CAMEL-13903 > URL: https://issues.apache.org/jira/browse/CAMEL-13903 > Project: Camel > Issue Type: Wish > Components: camel-telegram >Reporter: Peter Palaga >Priority: Major > > This is motivated by our efforts to port the telegram component to Quarkus > where RestEasy is available out of the box. > https://github.com/apache/camel-quarkus/issues/74 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13903) Port telegram component to RestEasy
[ https://issues.apache.org/jira/browse/CAMEL-13903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13903: - Issue Type: Wish (was: Bug) > Port telegram component to RestEasy > --- > > Key: CAMEL-13903 > URL: https://issues.apache.org/jira/browse/CAMEL-13903 > Project: Camel > Issue Type: Wish > Components: camel-telegram >Reporter: Peter Palaga >Priority: Major > > This is motivated by our efforts to port the telegram component to Quarkus > where RestEasy is available out of the box. > https://github.com/apache/camel-quarkus/issues/74 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (CAMEL-13891) camel-cxf - Add spring.schemas for -spring URL so it works for same online url
[ https://issues.apache.org/jira/browse/CAMEL-13891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13891: Assignee: Freeman Fang > camel-cxf - Add spring.schemas for -spring URL so it works for same online url > -- > > Key: CAMEL-13891 > URL: https://issues.apache.org/jira/browse/CAMEL-13891 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Reporter: Claus Ibsen >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > https://github.com/apache/camel/blob/master/components/camel-cxf/src/main/resources/META-INF/spring.schemas > Should have 2x for each pair > http\://camel.apache.org/schema/cxf/camel-cxf-3.0.0-M3.xsd=schema/cxfEndpoint.xsd > http\://camel.apache.org/schema/cxf/camel-cxf-3.0.0-M3-spring.xsd=schema/cxfEndpoint.xsd > For all of them, as then we have for old and new locations (eg when we had > blueprint later) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (CAMEL-13903) Port telegram component to RestEasy
Peter Palaga created CAMEL-13903: Summary: Port telegram component to RestEasy Key: CAMEL-13903 URL: https://issues.apache.org/jira/browse/CAMEL-13903 Project: Camel Issue Type: Bug Components: camel-telegram Reporter: Peter Palaga This is motivated by our efforts to port the telegram component to Quarkus where RestEasy is available out of the box. https://github.com/apache/camel-quarkus/issues/74 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13888) New web site: open foreign links in new window (tab)
[
https://issues.apache.org/jira/browse/CAMEL-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914251#comment-16914251
]
Zoran Regvart commented on CAMEL-13888:
---
For Hugo generated content we can add this to the
[config.toml|https://github.com/apache/camel-website/blob/master/config.toml]:
{code:yaml}
[blackfriday]
hrefTargetBlank = true
nofollowLinks = true
noreferrerLinks = true
{code}
Which also adds {{nofollow}}, {{noopener}} for {{target="_blank"}} is [on by
default|https://html.spec.whatwg.org/multipage/links.html#opener-processing-model].
For Asciidoc rendered content (user manual, component reference), we need to
change the markup of external links:
{code:none}
http://example.com[Example link^,opts=nofollow,noreferrer]
{code}
> New web site: open foreign links in new window (tab)
>
>
> Key: CAMEL-13888
> URL: https://issues.apache.org/jira/browse/CAMEL-13888
> Project: Camel
> Issue Type: Sub-task
> Components: website
>Reporter: Dmitry Volodin
>Priority: Minor
>
> It can be discussing, but would be nice to open all foreign links as new
> windows (tabs) for better usability while working with site, as some foreign
> resources not working correctly with return back to the original site page.
> Thank you.
--
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=16914218#comment-16914218 ] Andrea Cosentino commented on CAMEL-13821: -- There is also the camel-corda karaf feature to check. I don't have a corda node to test against.. But updating seems to be straightforward. > 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: 20m > 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] [Created] (CAMEL-13902) Publish links to JavaDoc on the website
Zoran Regvart created CAMEL-13902: - Summary: Publish links to JavaDoc on the website Key: CAMEL-13902 URL: https://issues.apache.org/jira/browse/CAMEL-13902 Project: Camel Issue Type: Task Components: website Reporter: Zoran Regvart We can utilize javadoc.io to publish the JavaDoc for: * camel-api * camel-support * camel-util -- 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=16914084#comment-16914084 ] Amol Pednekar commented on CAMEL-13821: --- In v4.0, the RPC API's themselves havent really changed, so dont think there'll be much to do other than changing the version of the library in the POM. ([~acosentino] - Unless there's anything else you've noticed?) Will have to run the tests to confirm. Unless there's a requirement to add new RPC APIs as well. > 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: 20m > 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] [Comment Edited] (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=16914084#comment-16914084 ] Amol Pednekar edited comment on CAMEL-13821 at 8/23/19 9:27 AM: In v4.0, the RPC API's themselves havent really changed, so dont think there'll be much to do other than changing the version of the library in the POM from 3.3 to 4.0/4.1 ([~acosentino] - Unless there's anything else you've noticed?) Will have to run the tests to confirm. Unless there's a requirement to add new RPC APIs as well. was (Author: amolpednekar): In v4.0, the RPC API's themselves havent really changed, so dont think there'll be much to do other than changing the version of the library in the POM. ([~acosentino] - Unless there's anything else you've noticed?) Will have to run the tests to confirm. Unless there's a requirement to add new RPC APIs as well. > 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: 20m > 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-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=16914075#comment-16914075
]
Jan Bednar commented on CAMEL-13821:
I dont know much about corda, but after reading docs it seems the
interoperability is just with 3.3 client.
{quote}There is a bug in Corda 3.3 that causes problems when receiving a
{{FungibleState}} created by Corda 4. There will shortly be a followup Corda
3.4 release that corrects this error. Interop between Corda 3 and Corda 4 will
require that Corda 3 users are on the latest patchlevel release.
{quote}
This should be fixed in 3.4 client with
[CORDA-2687|https://r3-cev.atlassian.net/browse/CORDA-2687]
Upgrade client between minor versions from 3.3 to 3.4 should be much easier.
Can somebody with access to corda nodes test this?
> 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: 20m
> 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-13598) camel-olingo4 - Support ETag / If-Match Headers when using CUD operations
[ https://issues.apache.org/jira/browse/CAMEL-13598?focusedWorklogId=300162&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-300162 ] ASF GitHub Bot logged work on CAMEL-13598: -- Author: ASF GitHub Bot Created on: 23/Aug/19 08:52 Start Date: 23/Aug/19 08:52 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #3118: CAMEL-13598: Implement ETag support in olingo components URL: https://github.com/apache/camel/pull/3118 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: 300162) Time Spent: 20m (was: 10m) > camel-olingo4 - Support ETag / If-Match Headers when using CUD operations > - > > Key: CAMEL-13598 > URL: https://issues.apache.org/jira/browse/CAMEL-13598 > Project: Camel > Issue Type: New Feature > Components: camel-olingo4 >Affects Versions: 2.21.5, 2.22.4 >Reporter: Paul Richardson >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC1 > > Time Spent: 20m > Remaining Estimate: 0h > > The [Tripin Reference > server|https://services.odata.org/TripPinRESTierService/(S(4gus0w41xmxedlzbywj2srqo))/$metadata] > supports ETags on its Airlines resource. Consequently, if an update or > delete operation is performed then the following must occur: > # Client calls a GET request & fetches the content of the ETag header; > # Client calls a PATCH/DELETE request complete with an *_If-None-Match_* > header that has a value of the previously queried ETag. > At the moment, attempts to use the camel-olingo4 implementation fail with an > http [428|https://httpstatuses.com/428] code. > Please see following for more information: > * [https://www.odata.org/getting-started/basic-tutorial/#etag] > * [https://www.odata.org/documentation/odata-version-2-0/operations/] > * > [https://olingo.apache.org/doc/odata4/overview.html#definition-of-the-web-infrastructure] > * [https://www.logicbig.com/quick-info/web/etag-header.html] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (CAMEL-13598) camel-olingo4 - Support ETag / If-Match Headers when using CUD operations
[ https://issues.apache.org/jira/browse/CAMEL-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13598: Assignee: Andrea Cosentino > camel-olingo4 - Support ETag / If-Match Headers when using CUD operations > - > > Key: CAMEL-13598 > URL: https://issues.apache.org/jira/browse/CAMEL-13598 > Project: Camel > Issue Type: New Feature > Components: camel-olingo4 >Affects Versions: 2.21.5, 2.22.4 >Reporter: Paul Richardson >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC1 > > Time Spent: 10m > Remaining Estimate: 0h > > The [Tripin Reference > server|https://services.odata.org/TripPinRESTierService/(S(4gus0w41xmxedlzbywj2srqo))/$metadata] > supports ETags on its Airlines resource. Consequently, if an update or > delete operation is performed then the following must occur: > # Client calls a GET request & fetches the content of the ETag header; > # Client calls a PATCH/DELETE request complete with an *_If-None-Match_* > header that has a value of the previously queried ETag. > At the moment, attempts to use the camel-olingo4 implementation fail with an > http [428|https://httpstatuses.com/428] code. > Please see following for more information: > * [https://www.odata.org/getting-started/basic-tutorial/#etag] > * [https://www.odata.org/documentation/odata-version-2-0/operations/] > * > [https://olingo.apache.org/doc/odata4/overview.html#definition-of-the-web-infrastructure] > * [https://www.logicbig.com/quick-info/web/etag-header.html] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (CAMEL-13598) camel-olingo4 - Support ETag / If-Match Headers when using CUD operations
[ https://issues.apache.org/jira/browse/CAMEL-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13598. -- Resolution: Fixed > camel-olingo4 - Support ETag / If-Match Headers when using CUD operations > - > > Key: CAMEL-13598 > URL: https://issues.apache.org/jira/browse/CAMEL-13598 > Project: Camel > Issue Type: New Feature > Components: camel-olingo4 >Affects Versions: 2.21.5, 2.22.4 >Reporter: Paul Richardson >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0.RC1 > > Time Spent: 10m > Remaining Estimate: 0h > > The [Tripin Reference > server|https://services.odata.org/TripPinRESTierService/(S(4gus0w41xmxedlzbywj2srqo))/$metadata] > supports ETags on its Airlines resource. Consequently, if an update or > delete operation is performed then the following must occur: > # Client calls a GET request & fetches the content of the ETag header; > # Client calls a PATCH/DELETE request complete with an *_If-None-Match_* > header that has a value of the previously queried ETag. > At the moment, attempts to use the camel-olingo4 implementation fail with an > http [428|https://httpstatuses.com/428] code. > Please see following for more information: > * [https://www.odata.org/getting-started/basic-tutorial/#etag] > * [https://www.odata.org/documentation/odata-version-2-0/operations/] > * > [https://olingo.apache.org/doc/odata4/overview.html#definition-of-the-web-infrastructure] > * [https://www.logicbig.com/quick-info/web/etag-header.html] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13598) camel-olingo4 - Support ETag / If-Match Headers when using CUD operations
[ https://issues.apache.org/jira/browse/CAMEL-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13598: - Fix Version/s: 3.0.0.RC1 > camel-olingo4 - Support ETag / If-Match Headers when using CUD operations > - > > Key: CAMEL-13598 > URL: https://issues.apache.org/jira/browse/CAMEL-13598 > Project: Camel > Issue Type: New Feature > Components: camel-olingo4 >Affects Versions: 2.21.5, 2.22.4 >Reporter: Paul Richardson >Priority: Major > Fix For: 3.0.0.RC1 > > Time Spent: 10m > Remaining Estimate: 0h > > The [Tripin Reference > server|https://services.odata.org/TripPinRESTierService/(S(4gus0w41xmxedlzbywj2srqo))/$metadata] > supports ETags on its Airlines resource. Consequently, if an update or > delete operation is performed then the following must occur: > # Client calls a GET request & fetches the content of the ETag header; > # Client calls a PATCH/DELETE request complete with an *_If-None-Match_* > header that has a value of the previously queried ETag. > At the moment, attempts to use the camel-olingo4 implementation fail with an > http [428|https://httpstatuses.com/428] code. > Please see following for more information: > * [https://www.odata.org/getting-started/basic-tutorial/#etag] > * [https://www.odata.org/documentation/odata-version-2-0/operations/] > * > [https://olingo.apache.org/doc/odata4/overview.html#definition-of-the-web-infrastructure] > * [https://www.logicbig.com/quick-info/web/etag-header.html] -- 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=16914057#comment-16914057 ] Andrea Cosentino commented on CAMEL-13821: -- There are not so much issue related to camel-corda, so a label for it is not really useful, you can use the filter function and [~amolpednekar] you're welcome to work on a PR for updating to 4 > 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: 20m > 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] [Comment Edited] (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=16914047#comment-16914047 ] Amol Pednekar edited comment on CAMEL-13821 at 8/23/19 8:29 AM: +1; any update? Because v3.3 of the Java RPC library doesn't work at all with Corda v4 because they've changed the serialization format (also can we tag the component as camel-corda so that its easy to filter?) was (Author: amolpednekar): +1; any update? Because v3.3 of the Java RPC library doesn't work at all with Corda v4 because they've changed the serialization format > 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: 20m > 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-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=16914047#comment-16914047 ] Amol Pednekar commented on CAMEL-13821: --- +1; any update? Because v3.3 of the Java RPC library doesn't work at all with Corda v4 because they've changed the serialization format > 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: 20m > 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-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914045#comment-16914045 ] Zoran Regvart commented on CAMEL-13780: --- We seem to be missing entries to some of the content, for example: https://camel.apache.org/manual/latest/dead-letter-channel.html https://camel.apache.org/manual/latest/exception-clause.html > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Fix For: 3.0.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (CAMEL-13901) camel-main-plugin - Dont run it automatic on compile
Claus Ibsen created CAMEL-13901: --- Summary: camel-main-plugin - Dont run it automatic on compile Key: CAMEL-13901 URL: https://issues.apache.org/jira/browse/CAMEL-13901 Project: Camel Issue Type: Improvement Components: examples, tooling Reporter: Claus Ibsen Fix For: 3.0.0, 3.0.0.RC1 Lets just add instructions in the readme and avoid running it on each build. Its used for setting up the project for tooling support, and if you want to have it to do auto-detection of certain JMS clients - eg ActiveMQ vs Artemis and adapt the project accordingly. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13870) camel3 - Fast configuring of endpoint options
[ https://issues.apache.org/jira/browse/CAMEL-13870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911236#comment-16911236 ] Claus Ibsen edited comment on CAMEL-13870 at 8/23/19 7:36 AM: -- TODOs - Endpoints with missing getter/setter paris *DONE* - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) *DONE* - Dynamic properties via multi valued and property prefix would still be reflection based (httpClient.xxx=aaa&httpClient.yyy=bbb) - Consider remove support for consumer.xxx as we dont really need this anymore - Allow to turn this on|off per endpoint so component developers can opt out *DONE* - Setting boolean should restrict to true|false string values *DONE* - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* - Fix camel-jetty as it has some "oddities" *DONE* - Fix camel-atomix as it has some "oddities" *DONE* - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" *DONE* - Fix camel-irc60870 as it has some "oddities" *DONE* - Fix camel-spring-ws as it has some "oddities" *DONE* - Fix camel-log as it has some "oddities" *DONE* - Rename apt json metadata to use configurationClassName instead of nested naming *DONE* - Omit getters as we dont need them for setting fast properties *DONE* - Fix camel-log so we use fast configurs for the log formatter options (its coded in a special way) *DONE* - Consider a way of gather usage statistics of introspection usage so we can find out how much reflection discovery we do with Camel *DONE* - fix camel-activemq / camel-amqp which should reuse camel-jms configurer *DONE* - make endpoint configurer map of options static and use 3-arg functional consumer for the writer. - camel-hdfs test failure *DONE* - use mandatoryConvertTo *DONE* - camel-mllp has some issues so it wont generate fast configurers at this time was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris *DONE* - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) *DONE* - Dynamic properties via multi valued and property prefix would still be reflection based (httpClient.xxx=aaa&httpClient.yyy=bbb) - Consider remove support for consumer.xxx as we dont really need this anymore - Allow to turn this on|off per endpoint so component developers can opt out *DONE* - Setting boolean should restrict to true|false string values *DONE* - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* - Fix camel-jetty as it has some "oddities" *DONE* - Fix camel-atomix as it has some "oddities" *DONE* - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" *DONE* - Fix camel-irc60870 as it has some "oddities" *DONE* - Fix camel-spring-ws as it has some "oddities" *DONE* - Fix camel-log as it has some "oddities" *DONE* - Rename apt json metadata to use configurationClassName instead of nested naming *DONE* - Omit getters as we dont need them for setting fast properties *DONE* - Fix camel-log so we use fast configurs for the log formatter options (its coded in a special way) *DONE* - Consider a way of gather usage statistics of introspection usage so we can find out how much reflection discovery we do with Camel *DONE* - fix camel-activemq / camel-amqp which should reuse camel-jms configurer *DONE* - make endpoint configurer map of options static and use a bi-arg functional consumer for the setter/getter - camel-hdfs test failure *DONE* - use mandatoryConvertTo *DONE* - camel-mllp has some issues so it wont generate fast configurers at this time > camel3 - Fast configuring of endpoint options > - > > Key: CAMEL-13870 > URL: https://issues.apache.org/jira/browse/CAMEL-13870 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > Like we did for fast property placeholders on EIPs we can optimize endpoints > as well, by using the apt compiler plugin to generate a configurer classes > that uses direct java method invocations and then the property builder > support class can detect that we have such a configurer and use it, when it > looks for the setter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13870) camel3 - Fast configuring of endpoint options
[ https://issues.apache.org/jira/browse/CAMEL-13870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13870: Fix Version/s: (was: 3.x) 3.0.0.RC1 3.0.0 > camel3 - Fast configuring of endpoint options > - > > Key: CAMEL-13870 > URL: https://issues.apache.org/jira/browse/CAMEL-13870 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > Like we did for fast property placeholders on EIPs we can optimize endpoints > as well, by using the apt compiler plugin to generate a configurer classes > that uses direct java method invocations and then the property builder > support class can detect that we have such a configurer and use it, when it > looks for the setter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
