[jira] [Work logged] (CAMEL-13877) RouteHealthCheck has NPE when JMX disabled
[ https://issues.apache.org/jira/browse/CAMEL-13877?focusedWorklogId=298475&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-298475 ] ASF GitHub Bot logged work on CAMEL-13877: -- Author: ASF GitHub Bot Created on: 21/Aug/19 06:53 Start Date: 21/Aug/19 06:53 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #3112: CAMEL-13877 fix NPE in RouteHealthCheck URL: https://github.com/apache/camel/pull/3112 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: 298475) Time Spent: 20m (was: 10m) > RouteHealthCheck has NPE when JMX disabled > -- > > Key: CAMEL-13877 > URL: https://issues.apache.org/jira/browse/CAMEL-13877 > Project: Camel > Issue Type: Bug >Affects Versions: 3.0.0-M1 >Reporter: Paul Heaberlin >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.0.0.RC1 > > Attachments: RouteHealthCheckTest.java > > Time Spent: 20m > Remaining Estimate: 0h > > RouteHealthCheck throws NPE when JMX is disabled > See attached Junit -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13877) RouteHealthCheck has NPE when JMX disabled
[ https://issues.apache.org/jira/browse/CAMEL-13877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13877: - Fix Version/s: 3.0.0.RC1 > RouteHealthCheck has NPE when JMX disabled > -- > > Key: CAMEL-13877 > URL: https://issues.apache.org/jira/browse/CAMEL-13877 > Project: Camel > Issue Type: Bug >Affects Versions: 3.0.0-M1 >Reporter: Paul Heaberlin >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.0.0.RC1 > > Attachments: RouteHealthCheckTest.java > > Time Spent: 10m > Remaining Estimate: 0h > > RouteHealthCheck throws NPE when JMX is disabled > See attached Junit -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (CAMEL-13877) RouteHealthCheck has NPE when JMX disabled
[ https://issues.apache.org/jira/browse/CAMEL-13877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13877. -- Resolution: Fixed > RouteHealthCheck has NPE when JMX disabled > -- > > Key: CAMEL-13877 > URL: https://issues.apache.org/jira/browse/CAMEL-13877 > Project: Camel > Issue Type: Bug >Affects Versions: 3.0.0-M1 >Reporter: Paul Heaberlin >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.0.0.RC1 > > Attachments: RouteHealthCheckTest.java > > Time Spent: 10m > Remaining Estimate: 0h > > RouteHealthCheck throws NPE when JMX is disabled > See attached Junit -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (CAMEL-13877) RouteHealthCheck has NPE when JMX disabled
[ https://issues.apache.org/jira/browse/CAMEL-13877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13877: Assignee: Andrea Cosentino > RouteHealthCheck has NPE when JMX disabled > -- > > Key: CAMEL-13877 > URL: https://issues.apache.org/jira/browse/CAMEL-13877 > Project: Camel > Issue Type: Bug >Affects Versions: 3.0.0-M1 >Reporter: Paul Heaberlin >Assignee: Andrea Cosentino >Priority: Minor > Attachments: RouteHealthCheckTest.java > > Time Spent: 10m > Remaining Estimate: 0h > > RouteHealthCheck throws NPE when JMX is disabled > See attached Junit -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13886) camel-servlet + camel-http4 with null body causes "Stream closed" IOException
[
https://issues.apache.org/jira/browse/CAMEL-13886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tadayoshi Sato updated CAMEL-13886:
---
Fix Version/s: 3.0.0.RC1
2.25.0
> camel-servlet + camel-http4 with null body causes "Stream closed" IOException
> -
>
> Key: CAMEL-13886
> URL: https://issues.apache.org/jira/browse/CAMEL-13886
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common, camel-http4, camel-servlet
>Affects Versions: 2.25.0, 3.0.0.M4
>Reporter: Tadayoshi Sato
>Assignee: Tadayoshi Sato
>Priority: Major
> Fix For: 2.25.0, 3.0.0.RC1
>
>
> A Rest DSL route like the following causes {{java.io.IOException: Stream
> closed}} when invoked at http://localhost:8000/test/proxy:
> {code:java}
> rest("/test")
> .get("/proxy")
> .to("direct:callInternalRestService");
> from("direct:callInternalRestService")
> .setHeader(Exchange.HTTP_METHOD, constant("DELETE"))
> //.setBody(constant("")) // workaround for null body and
> http4 component
> .to("http4://localhost:9000/test?bridgeEndpoint=true")
> .log("${body}");
> {code}
> The error stacktrace:
> {code}
> Caused by: java.io.IOException: Stream closed
> at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:372)
> at
> org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:156)
> at org.apache.camel.util.IOHelper.copy(IOHelper.java:202)
> at org.apache.camel.util.IOHelper.copy(IOHelper.java:174)
> at org.apache.camel.util.IOHelper.copyAndCloseInput(IOHelper.java:234)
> at org.apache.camel.util.IOHelper.copyAndCloseInput(IOHelper.java:230)
> at
> org.apache.camel.http.common.HttpHelper.readResponseBodyFromInputStream(HttpHelper.java:245)
> at
> org.apache.camel.http.common.HttpHelper.readRequestBodyFromServletRequest(HttpHelper.java:196)
> at
> org.apache.camel.http.common.DefaultHttpBinding.parseBody(DefaultHttpBinding.java:577)
> at
> org.apache.camel.http.common.HttpMessage.createBody(HttpMessage.java:78)
> ... 54 common frames omitted
> {code}
> This seems to happen only when Tomcat is used as the container with Spring
> Boot. Undertow doesn't cause such an issue.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (CAMEL-13887) camel-mongodb-gridfs - Mongo to MongoClient
Claus Ibsen created CAMEL-13887: --- Summary: camel-mongodb-gridfs - Mongo to MongoClient Key: CAMEL-13887 URL: https://issues.apache.org/jira/browse/CAMEL-13887 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen The former is deprecate and we should switch to MongoDBClient instead -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (CAMEL-13886) camel-servlet + camel-http4 with null body causes "Stream closed" IOException
[
https://issues.apache.org/jira/browse/CAMEL-13886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tadayoshi Sato resolved CAMEL-13886.
Resolution: Fixed
> camel-servlet + camel-http4 with null body causes "Stream closed" IOException
> -
>
> Key: CAMEL-13886
> URL: https://issues.apache.org/jira/browse/CAMEL-13886
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common, camel-http4, camel-servlet
>Affects Versions: 2.25.0, 3.0.0.M4
>Reporter: Tadayoshi Sato
>Assignee: Tadayoshi Sato
>Priority: Major
> Fix For: 2.25.0, 3.0.0.RC1
>
>
> A Rest DSL route like the following causes {{java.io.IOException: Stream
> closed}} when invoked at http://localhost:8000/test/proxy:
> {code:java}
> rest("/test")
> .get("/proxy")
> .to("direct:callInternalRestService");
> from("direct:callInternalRestService")
> .setHeader(Exchange.HTTP_METHOD, constant("DELETE"))
> //.setBody(constant("")) // workaround for null body and
> http4 component
> .to("http4://localhost:9000/test?bridgeEndpoint=true")
> .log("${body}");
> {code}
> The error stacktrace:
> {code}
> Caused by: java.io.IOException: Stream closed
> at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:372)
> at
> org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:156)
> at org.apache.camel.util.IOHelper.copy(IOHelper.java:202)
> at org.apache.camel.util.IOHelper.copy(IOHelper.java:174)
> at org.apache.camel.util.IOHelper.copyAndCloseInput(IOHelper.java:234)
> at org.apache.camel.util.IOHelper.copyAndCloseInput(IOHelper.java:230)
> at
> org.apache.camel.http.common.HttpHelper.readResponseBodyFromInputStream(HttpHelper.java:245)
> at
> org.apache.camel.http.common.HttpHelper.readRequestBodyFromServletRequest(HttpHelper.java:196)
> at
> org.apache.camel.http.common.DefaultHttpBinding.parseBody(DefaultHttpBinding.java:577)
> at
> org.apache.camel.http.common.HttpMessage.createBody(HttpMessage.java:78)
> ... 54 common frames omitted
> {code}
> This seems to happen only when Tomcat is used as the container with Spring
> Boot. Undertow doesn't cause such an issue.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13887) camel-mongodb-gridfs - Mongo to MongoClient
[ https://issues.apache.org/jira/browse/CAMEL-13887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13887: Fix Version/s: 3.x > camel-mongodb-gridfs - Mongo to MongoClient > --- > > Key: CAMEL-13887 > URL: https://issues.apache.org/jira/browse/CAMEL-13887 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > The former is deprecate and we should switch to MongoDBClient instead -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13887) camel-mongodb-gridfs - Mongo to MongoClient
[ https://issues.apache.org/jira/browse/CAMEL-13887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13887: Estimated Complexity: Novice (was: Unknown) > camel-mongodb-gridfs - Mongo to MongoClient > --- > > Key: CAMEL-13887 > URL: https://issues.apache.org/jira/browse/CAMEL-13887 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > > The former is deprecate and we should switch to MongoDBClient instead -- 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=16911981#comment-16911981 ] Dmitry Volodin commented on CAMEL-13888: [~zregvart], what do you think about this changes? > 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] [Created] (CAMEL-13886) camel-servlet + camel-http4 with null body causes "Stream closed" IOException
Tadayoshi Sato created CAMEL-13886:
--
Summary: camel-servlet + camel-http4 with null body causes "Stream
closed" IOException
Key: CAMEL-13886
URL: https://issues.apache.org/jira/browse/CAMEL-13886
Project: Camel
Issue Type: Bug
Components: camel-http-common, camel-http4, camel-servlet
Affects Versions: 3.0.0.M4, 2.25.0
Reporter: Tadayoshi Sato
Assignee: Tadayoshi Sato
A Rest DSL route like the following causes {{java.io.IOException: Stream
closed}} when invoked at http://localhost:8000/test/proxy:
{code:java}
rest("/test")
.get("/proxy")
.to("direct:callInternalRestService");
from("direct:callInternalRestService")
.setHeader(Exchange.HTTP_METHOD, constant("DELETE"))
//.setBody(constant("")) // workaround for null body and http4
component
.to("http4://localhost:9000/test?bridgeEndpoint=true")
.log("${body}");
{code}
The error stacktrace:
{code}
Caused by: java.io.IOException: Stream closed
at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:372)
at
org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:156)
at org.apache.camel.util.IOHelper.copy(IOHelper.java:202)
at org.apache.camel.util.IOHelper.copy(IOHelper.java:174)
at org.apache.camel.util.IOHelper.copyAndCloseInput(IOHelper.java:234)
at org.apache.camel.util.IOHelper.copyAndCloseInput(IOHelper.java:230)
at
org.apache.camel.http.common.HttpHelper.readResponseBodyFromInputStream(HttpHelper.java:245)
at
org.apache.camel.http.common.HttpHelper.readRequestBodyFromServletRequest(HttpHelper.java:196)
at
org.apache.camel.http.common.DefaultHttpBinding.parseBody(DefaultHttpBinding.java:577)
at
org.apache.camel.http.common.HttpMessage.createBody(HttpMessage.java:78)
... 54 common frames omitted
{code}
This seems to happen only when Tomcat is used as the container with Spring
Boot. Undertow doesn't cause such an issue.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (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=16911981#comment-16911981 ] Dmitry Volodin edited comment on CAMEL-13888 at 8/21/19 6:34 AM: - [~zregvart], what do you think about this change? was (Author: dmvolod): [~zregvart], what do you think about this changes? > 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] [Created] (CAMEL-13888) New web site: open foreign links in new window (tab)
Dmitry Volodin created CAMEL-13888: -- Summary: 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 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-13830) Move examples to a new camel-examples git repo
[ https://issues.apache.org/jira/browse/CAMEL-13830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911948#comment-16911948 ] Francois Papon commented on CAMEL-13830: Ok, let me know :) > Move examples to a new camel-examples git repo > -- > > Key: CAMEL-13830 > URL: https://issues.apache.org/jira/browse/CAMEL-13830 > Project: Camel > Issue Type: Improvement > Components: examples >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > I think it may be quicker and easier for new users to try our examples if we > put them in a separate repo, so there is less source code. The git repo for > Camel is very big, and it takes a longer time to checkout, and users may get > lost in the source code. > If we have a camel-examples git repo with just examples we can refer people > to this. -- This message was sent by Atlassian Jira (v8.3.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/21/19 4:46 AM: -- TODOs - Endpoints with missing getter/setter paris - 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" - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" - Fix camel-irc60870 as it has some "oddities" was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris - 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" - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" > 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.x > > > 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] [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/21/19 4:25 AM: -- TODOs - Endpoints with missing getter/setter paris - 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" - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris - 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" - Fix camel-cmis as it has some "oddities" - Fix camel-crypto-cms as it has some "oddities" > 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.x > > > 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] [Created] (CAMEL-13885) Add categories to examples that dont have this
Claus Ibsen created CAMEL-13885: --- Summary: Add categories to examples that dont have this Key: CAMEL-13885 URL: https://issues.apache.org/jira/browse/CAMEL-13885 Project: Camel Issue Type: Improvement Components: examples Reporter: Claus Ibsen Fix For: 3.0.0, 3.0.0.RC1 See the category column is empty for some of the examples https://github.com/apache/camel/tree/master/examples#examples You add this in the pom.xml file -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13586) New website: The spacing related to links in antora generated docs is wrong
[ https://issues.apache.org/jira/browse/CAMEL-13586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911763#comment-16911763 ] Jan Bednar commented on CAMEL-13586: I think this was fixed with CAMEL-13839 > New website: The spacing related to links in antora generated docs is wrong > --- > > Key: CAMEL-13586 > URL: https://issues.apache.org/jira/browse/CAMEL-13586 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Andrea Cosentino >Priority: Major > > This can be noticed for example in > [http://camel.apache.org/staging/components/latest/ahc-ws-component.html#ahc-component] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13091) Ensure that all spring boot starters have all their options documented
[
https://issues.apache.org/jira/browse/CAMEL-13091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911745#comment-16911745
]
Jan Bednar commented on CAMEL-13091:
[~swidersk7] What tool do you mean? The adoc files are already generated and
there is no need to update them manually.
*This task is about:*
# Find all component docs warning `
{{[WARNING] Option aaa.bbb.ccc.d has no description}}
during build - eg here:
[https://builds.apache.org/job/Camel/job/master/1483/consoleFull]
# For every warning find relevant code with {{Metadata}} annotation and add
{{description}} attribute into this annotation.
# Do full build - documentation will be updated automatically
> Ensure that all spring boot starters have all their options documented
> --
>
> Key: CAMEL-13091
> URL: https://issues.apache.org/jira/browse/CAMEL-13091
> Project: Camel
> Issue Type: Task
> Components: camel-spring-boot-starters
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 3.x
>
>
> Some of the camel components do not have component level docs for all their
> options, which are generated into the spring boot metadata.
> You can see this with the build WARNs when building all the starter JARs.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13091) Ensure that all spring boot starters have all their options documented
[ https://issues.apache.org/jira/browse/CAMEL-13091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911706#comment-16911706 ] Przemyslaw Swiderski commented on CAMEL-13091: -- Hi, is there any tool to generate adoc tables based on spring-configuration-metadata.json files? It would mke this task even easier. > Ensure that all spring boot starters have all their options documented > -- > > Key: CAMEL-13091 > URL: https://issues.apache.org/jira/browse/CAMEL-13091 > Project: Camel > Issue Type: Task > Components: camel-spring-boot-starters >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > Some of the camel components do not have component level docs for all their > options, which are generated into the spring boot metadata. > You can see this with the build WARNs when building all the starter JARs. -- 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/20/19 6:35 PM: -- TODOs - Endpoints with missing getter/setter paris - 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" - Fix camel-cmis as it has some "oddities" - Fix camel-crypto-cms as it has some "oddities" was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris - 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" - Fix camel-cmis as it has some "oddities" > 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.x > > > 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] [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/20/19 6:24 PM: -- TODOs - Endpoints with missing getter/setter paris - 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" - Fix camel-cmis as it has some "oddities" was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris - 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" > 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.x > > > 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] [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/20/19 6:03 PM: -- TODOs - Endpoints with missing getter/setter paris - 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" was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris - 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" > 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.x > > > 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] [Work logged] (CAMEL-13883) Fix broken links in summary page
[ https://issues.apache.org/jira/browse/CAMEL-13883?focusedWorklogId=298070&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-298070 ] ASF GitHub Bot logged work on CAMEL-13883: -- Author: ASF GitHub Bot Created on: 20/Aug/19 17:50 Start Date: 20/Aug/19 17:50 Worklog Time Spent: 10m Work Description: Nayananga commented on pull request #3115: CAMEL-13883 URL: https://github.com/apache/camel/pull/3115 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: 298070) Remaining Estimate: 0h Time Spent: 10m > Fix broken links in summary page > > > Key: CAMEL-13883 > URL: https://issues.apache.org/jira/browse/CAMEL-13883 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The user manual summary page > https://camel.apache.org/staging/manual/latest/index.html contains some > broken links, e.g.: > * Legal Notice > * Configuring route startup ordering and autostartup > * AsyncProcessorAwaitManager > * Camel Maven Plugin > * Camel JMX > * ... -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13586) New website: The spacing related to links in antora generated docs is wrong
[ https://issues.apache.org/jira/browse/CAMEL-13586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911578#comment-16911578 ] Nayananga Muhandiram commented on CAMEL-13586: -- Hi is this bug still available? I couldn`t spot it in the above link or in [https://camel.apache.org/components/latest/ahc-ws-component.html] > New website: The spacing related to links in antora generated docs is wrong > --- > > Key: CAMEL-13586 > URL: https://issues.apache.org/jira/browse/CAMEL-13586 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Andrea Cosentino >Priority: Major > > This can be noticed for example in > [http://camel.apache.org/staging/components/latest/ahc-ws-component.html#ahc-component] -- 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/20/19 5:19 PM: -- TODOs - Endpoints with missing getter/setter paris - 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" was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris - 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* > 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.x > > > 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] [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/20/19 5:15 PM: -- TODOs - Endpoints with missing getter/setter paris - 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* was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris - 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 - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* > 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.x > > > 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] [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/20/19 5:15 PM: -- TODOs - Endpoints with missing getter/setter paris - 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 - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) - 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 - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* > 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.x > > > 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] [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/20/19 3:27 PM: -- TODOs - Endpoints with missing getter/setter paris - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) - 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 - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) - 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 - Setting boolean should restrict to true|false string values - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" > 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.x > > > 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] [Resolved] (CAMEL-13882) Fix broken images
[ https://issues.apache.org/jira/browse/CAMEL-13882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-13882. --- Resolution: Fixed Should be fixed, I'll trigger the website build changes should be visible in 5 minutes or so. > Fix broken images > - > > Key: CAMEL-13882 > URL: https://issues.apache.org/jira/browse/CAMEL-13882 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Assignee: Zoran Regvart >Priority: Major > > The following pages contain broken images: > * https://camel.apache.org/staging/manual/latest/async.html > * https://camel.apache.org/staging/manual/latest/camel-core.html > * https://camel.apache.org/staging/manual/latest/debugger.html > * https://camel.apache.org/staging/manual/latest/lifecycle.html -- 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/20/19 2:32 PM: -- TODOs - Endpoints with missing getter/setter paris - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) - 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 - Setting boolean should restrict to true|false string values - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) - 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 - Setting boolean should restrict to true|false string values - Also generate for component's so we have for both endpoint and components > 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.x > > > 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] [Assigned] (CAMEL-13882) Fix broken images
[ https://issues.apache.org/jira/browse/CAMEL-13882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart reassigned CAMEL-13882: - Assignee: Zoran Regvart > Fix broken images > - > > Key: CAMEL-13882 > URL: https://issues.apache.org/jira/browse/CAMEL-13882 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Assignee: Zoran Regvart >Priority: Major > > The following pages contain broken images: > * https://camel.apache.org/staging/manual/latest/async.html > * https://camel.apache.org/staging/manual/latest/camel-core.html > * https://camel.apache.org/staging/manual/latest/debugger.html > * https://camel.apache.org/staging/manual/latest/lifecycle.html -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work started] (CAMEL-13882) Fix broken images
[ https://issues.apache.org/jira/browse/CAMEL-13882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-13882 started by Zoran Regvart. - > Fix broken images > - > > Key: CAMEL-13882 > URL: https://issues.apache.org/jira/browse/CAMEL-13882 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Assignee: Zoran Regvart >Priority: Major > > The following pages contain broken images: > * https://camel.apache.org/staging/manual/latest/async.html > * https://camel.apache.org/staging/manual/latest/camel-core.html > * https://camel.apache.org/staging/manual/latest/debugger.html > * https://camel.apache.org/staging/manual/latest/lifecycle.html -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13883) Fix broken links in summary page
[ https://issues.apache.org/jira/browse/CAMEL-13883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911373#comment-16911373 ] Zoran Regvart commented on CAMEL-13883: --- The source for that page is here: [https://github.com/apache/camel/blob/master/docs/user-manual/modules/ROOT/pages/index.adoc] We might consider of having links to other pages have a short introduction to the manual. > Fix broken links in summary page > > > Key: CAMEL-13883 > URL: https://issues.apache.org/jira/browse/CAMEL-13883 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Priority: Major > > The user manual summary page > https://camel.apache.org/staging/manual/latest/index.html contains some > broken links, e.g.: > * Legal Notice > * Configuring route startup ordering and autostartup > * AsyncProcessorAwaitManager > * Camel Maven Plugin > * Camel JMX > * ... -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13881) Article containers right margin is larger than left margin
[ https://issues.apache.org/jira/browse/CAMEL-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911371#comment-16911371 ] Zoran Regvart commented on CAMEL-13881: --- We have variables to change max-width here: [https://github.com/apache/camel-website/blob/1e4e14662052fddc64da5a7dcacd12e18ba552bc/antora-ui-camel/src/css/vars.css#L133-L136] Though what we might consider is to center the content to make the margins the same that can be done here for the documentation: [https://github.com/apache/camel-website/blob/master/antora-ui-camel/src/css/doc.css#L1-L16] And here for the static (Hugo built) bits: https://github.com/apache/camel-website/blob/1e4e14662052fddc64da5a7dcacd12e18ba552bc/antora-ui-camel/src/css/static.css#L1-L10 > Article containers right margin is larger than left margin > -- > > Key: CAMEL-13881 > URL: https://issues.apache.org/jira/browse/CAMEL-13881 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Priority: Minor > Attachments: Screenshot 2019-08-20 at 10.51.48.png > > > The right margin of the article containers is larger than the left margin. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (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 commented on CAMEL-13870: - TODOs - Endpoints with missing getter/setter paris - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) - 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 - Setting boolean should restrict to true|false string values - Also generate for component's so we have for both endpoint and components > 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.x > > > 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] [Commented] (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=16911199#comment-16911199 ] Claus Ibsen commented on CAMEL-13870: - Working on a prototype > 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.x > > > 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] [Assigned] (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 reassigned CAMEL-13870: --- Assignee: Claus Ibsen > 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.x > > > 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] [Commented] (CAMEL-13830) Move examples to a new camel-examples git repo
[ https://issues.apache.org/jira/browse/CAMEL-13830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911198#comment-16911198 ] Claus Ibsen commented on CAMEL-13830: - At this moment we are not moving the examples. But would likely start doing this in 3.x, eg when we move spring-boot, karaf and other parts out of "big camel" and then it makes sense to also move examples out. > Move examples to a new camel-examples git repo > -- > > Key: CAMEL-13830 > URL: https://issues.apache.org/jira/browse/CAMEL-13830 > Project: Camel > Issue Type: Improvement > Components: examples >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > I think it may be quicker and easier for new users to try our examples if we > put them in a separate repo, so there is less source code. The git repo for > Camel is very big, and it takes a longer time to checkout, and users may get > lost in the source code. > If we have a camel-examples git repo with just examples we can refer people > to this. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13884) JMS, transacted=true and multiple messages
[
https://issues.apache.org/jira/browse/CAMEL-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jgreffe updated CAMEL-13884:
Description:
Hello,
seems there's an issue with Camel JMS :
# one producer poll files from a directory and send to an ActiveMQ subject
# one consumer reads messages in a non transacted way
# one consumer reads messages in a transacted way
2. reads all messages correctly
3. doesn't read all messages
Attached is a Maven project, with a Transacted main.
The output will be :
{code:java}
INFO | Apache Camel 2.20.1 (CamelContext: camel-1) is starting
INFO | JMX is enabled
INFO | Type converters loaded (core: 192, classpath: 4)
INFO | StreamCaching is not in use. If using streams then its recommended to
enable stream caching. See more details at
http://camel.apache.org/stream-caching.html
INFO | Endpoint is configured with noop=true so forcing endpoint to be
idempotent as well
INFO | Using default memory based idempotent repository with cache max size:
1000
INFO | Route: globalTest_cFile_1 started and consuming from:
file://C:/tmp/in?autoCreate=true&bufferSize=128&flatten=false&noop=true
INFO | Route: globalTest_cJMS_2 started and consuming from:
cMQConnectionFactory1://topic:topic1?transacted=true
INFO | Route: globalTest_cJMS_3 started and consuming from:
cMQConnectionFactory1://topic:topic1
INFO | Total 3 routes, of which 3 are started
INFO | Apache Camel 2.20.1 (CamelContext: camel-1) started in 0.656 seconds
WARN | Producing: aFile1.txt
WARN | Received non transacted: aFile1.txt
WARN | Received transacted: aFile1.txt
WARN | Producing: aFile2.txt
WARN | Received non transacted: aFile2.txt {code}
We should have another log :
{code:java}
WARN | Received transacted: aFile2.txt{code}
To reproduce :
* run ActiveMQ
* import Transacted.zip in an IDE
* update the Transacted.filesDirectory to a directory
* fill 2 files in this directory
* execute the main method
Thanks!
was:
Hello,
seems there's an issue with Camel JMS :
# one producer poll files from a directory and send to an ActiveMQ subject
# one consumer reads messages in a non transacted way
# one consumer reads messages in a transacted way
2. reads all messages correctly
3. doesn't read all messages
Attached is a Maven project, with a Transacted main.
The output will be :
{code:java}
INFO | Apache Camel 2.20.1 (CamelContext: camel-1) is starting
INFO | JMX is enabled
INFO | Type converters loaded (core: 192, classpath: 4)
INFO | StreamCaching is not in use. If using streams then its recommended to
enable stream caching. See more details at
http://camel.apache.org/stream-caching.html
INFO | Endpoint is configured with noop=true so forcing endpoint to be
idempotent as well
INFO | Using default memory based idempotent repository with cache max size:
1000
INFO | Route: globalTest_cFile_1 started and consuming from:
file://C:/tmp/TESB-26765/in?autoCreate=true&bufferSize=128&flatten=false&noop=true
INFO | Route: globalTest_cJMS_2 started and consuming from:
cMQConnectionFactory1://topic:topic1?transacted=true
INFO | Route: globalTest_cJMS_3 started and consuming from:
cMQConnectionFactory1://topic:topic1
INFO | Total 3 routes, of which 3 are started
INFO | Apache Camel 2.20.1 (CamelContext: camel-1) started in 0.656 seconds
WARN | Producing: aFile1.txt
WARN | Received non transacted: aFile1.txt
WARN | Received transacted: aFile1.txt
WARN | Producing: aFile2.txt
WARN | Received non transacted: aFile2.txt {code}
We should have another log :
{code:java}
WARN | Received transacted: aFile2.txt{code}
To reproduce :
* import Transacted.zip in an IDE
* update the Transacted.filesDirectory to a directory
* fill 2 files in this directory
* execute the main method
Thanks!
> JMS, transacted=true and multiple messages
> --
>
> Key: CAMEL-13884
> URL: https://issues.apache.org/jira/browse/CAMEL-13884
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
>Affects Versions: 2.20.1, 2.21.2, 2.23.1
>Reporter: jgreffe
>Priority: Major
> Attachments: Transacted.zip
>
>
> Hello,
> seems there's an issue with Camel JMS :
> # one producer poll files from a directory and send to an ActiveMQ subject
> # one consumer reads messages in a non transacted way
> # one consumer reads messages in a transacted way
> 2. reads all messages correctly
> 3. doesn't read all messages
>
> Attached is a Maven project, with a Transacted main.
> The output will be :
> {code:java}
> INFO | Apache Camel 2.20.1 (CamelContext: camel-1) is starting
> INFO | JMX is enabled
> INFO | Type converters loaded (core: 192, classpath: 4)
> INFO | StreamCaching is not in use. If using streams then its recommended to
> enable stream caching. See more details at
> http://camel.apache.
[jira] [Created] (CAMEL-13884) JMS, transacted=true and multiple messages
jgreffe created CAMEL-13884:
---
Summary: JMS, transacted=true and multiple messages
Key: CAMEL-13884
URL: https://issues.apache.org/jira/browse/CAMEL-13884
Project: Camel
Issue Type: Bug
Components: camel-jms
Affects Versions: 2.23.1, 2.21.2, 2.20.1
Reporter: jgreffe
Attachments: Transacted.zip
Hello,
seems there's an issue with Camel JMS :
# one producer poll files from a directory and send to an ActiveMQ subject
# one consumer reads messages in a non transacted way
# one consumer reads messages in a transacted way
2. reads all messages correctly
3. doesn't read all messages
Attached is a Maven project, with a Transacted main.
The output will be :
{code:java}
INFO | Apache Camel 2.20.1 (CamelContext: camel-1) is starting
INFO | JMX is enabled
INFO | Type converters loaded (core: 192, classpath: 4)
INFO | StreamCaching is not in use. If using streams then its recommended to
enable stream caching. See more details at
http://camel.apache.org/stream-caching.html
INFO | Endpoint is configured with noop=true so forcing endpoint to be
idempotent as well
INFO | Using default memory based idempotent repository with cache max size:
1000
INFO | Route: globalTest_cFile_1 started and consuming from:
file://C:/tmp/TESB-26765/in?autoCreate=true&bufferSize=128&flatten=false&noop=true
INFO | Route: globalTest_cJMS_2 started and consuming from:
cMQConnectionFactory1://topic:topic1?transacted=true
INFO | Route: globalTest_cJMS_3 started and consuming from:
cMQConnectionFactory1://topic:topic1
INFO | Total 3 routes, of which 3 are started
INFO | Apache Camel 2.20.1 (CamelContext: camel-1) started in 0.656 seconds
WARN | Producing: aFile1.txt
WARN | Received non transacted: aFile1.txt
WARN | Received transacted: aFile1.txt
WARN | Producing: aFile2.txt
WARN | Received non transacted: aFile2.txt {code}
We should have another log :
{code:java}
WARN | Received transacted: aFile2.txt{code}
To reproduce :
* import Transacted.zip in an IDE
* update the Transacted.filesDirectory to a directory
* fill 2 files in this directory
* execute the main method
Thanks!
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-13881) Article containers right margin is larger than left margin
[
https://issues.apache.org/jira/browse/CAMEL-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911126#comment-16911126
]
Antonin Stefanutti edited comment on CAMEL-13881 at 8/20/19 9:37 AM:
-
It seems this is due to the {{max-width}} style being applied to the article.
Maybe one option would be to offer radio buttons for the users to choose from
unlimited width or max width.
Or simply increase the {{max-width}}, to give more space to layout elements
like component tables that look too _compressed_.
was (Author: antonin.stefanutti):
It seems this is due to the {{max-width}} style being applied to the article.
Maybe one option would be to offer radio buttons for the users to choose from
unlimited width or max width.
> Article containers right margin is larger than left margin
> --
>
> Key: CAMEL-13881
> URL: https://issues.apache.org/jira/browse/CAMEL-13881
> Project: Camel
> Issue Type: Sub-task
> Components: website
>Reporter: Antonin Stefanutti
>Priority: Minor
> Attachments: Screenshot 2019-08-20 at 10.51.48.png
>
>
> The right margin of the article containers is larger than the left margin.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAMEL-13830) Move examples to a new camel-examples git repo
[ https://issues.apache.org/jira/browse/CAMEL-13830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911161#comment-16911161 ] Francois Papon commented on CAMEL-13830: Hi [~davsclaus]! Can I help by working on this issue? > Move examples to a new camel-examples git repo > -- > > Key: CAMEL-13830 > URL: https://issues.apache.org/jira/browse/CAMEL-13830 > Project: Camel > Issue Type: Improvement > Components: examples >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > I think it may be quicker and easier for new users to try our examples if we > put them in a separate repo, so there is less source code. The git repo for > Camel is very big, and it takes a longer time to checkout, and users may get > lost in the source code. > If we have a camel-examples git repo with just examples we can refer people > to this. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (CAMEL-13883) Fix broken links in summary page
Antonin Stefanutti created CAMEL-13883: -- Summary: Fix broken links in summary page Key: CAMEL-13883 URL: https://issues.apache.org/jira/browse/CAMEL-13883 Project: Camel Issue Type: Sub-task Components: website Reporter: Antonin Stefanutti The user manual summary page https://camel.apache.org/staging/manual/latest/index.html contains some broken links, e.g.: * Legal Notice * Configuring route startup ordering and autostartup * AsyncProcessorAwaitManager * Camel Maven Plugin * Camel JMX * ... -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (CAMEL-13882) Fix broken images
Antonin Stefanutti created CAMEL-13882: -- Summary: Fix broken images Key: CAMEL-13882 URL: https://issues.apache.org/jira/browse/CAMEL-13882 Project: Camel Issue Type: Sub-task Components: website Reporter: Antonin Stefanutti The following pages contain broken images: * https://camel.apache.org/staging/manual/latest/async.html * https://camel.apache.org/staging/manual/latest/camel-core.html * https://camel.apache.org/staging/manual/latest/debugger.html * https://camel.apache.org/staging/manual/latest/lifecycle.html -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13881) Article containers right margin is larger than left margin
[
https://issues.apache.org/jira/browse/CAMEL-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911126#comment-16911126
]
Antonin Stefanutti commented on CAMEL-13881:
It seems this is due to the {{max-width}} style being applied to the article.
Maybe one option would be to offer radio buttons for the users to choose from
unlimited width or max width.
> Article containers right margin is larger than left margin
> --
>
> Key: CAMEL-13881
> URL: https://issues.apache.org/jira/browse/CAMEL-13881
> Project: Camel
> Issue Type: Sub-task
> Components: website
>Reporter: Antonin Stefanutti
>Priority: Minor
> Attachments: Screenshot 2019-08-20 at 10.51.48.png
>
>
> The right margin of the article containers is larger than the left margin.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAMEL-13881) Article containers right margin is larger than left margin
[ https://issues.apache.org/jira/browse/CAMEL-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated CAMEL-13881: --- Description: The right margin of the article containers is larger than the left margin. (was: The right margin of the component pages is larger than the left margin. ) > Article containers right margin is larger than left margin > -- > > Key: CAMEL-13881 > URL: https://issues.apache.org/jira/browse/CAMEL-13881 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Priority: Minor > Attachments: Screenshot 2019-08-20 at 10.51.48.png > > > The right margin of the article containers is larger than the left margin. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13881) Article containers right margin is larger than left margin
[ https://issues.apache.org/jira/browse/CAMEL-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated CAMEL-13881: --- Summary: Article containers right margin is larger than left margin (was: Component pages right margin is larger than left margin) > Article containers right margin is larger than left margin > -- > > Key: CAMEL-13881 > URL: https://issues.apache.org/jira/browse/CAMEL-13881 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Priority: Minor > Attachments: Screenshot 2019-08-20 at 10.51.48.png > > > The right margin of the component pages is larger than the left margin. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13881) Component pages right margin is larger than left margin
[ https://issues.apache.org/jira/browse/CAMEL-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated CAMEL-13881: --- Attachment: Screenshot 2019-08-20 at 10.51.48.png > Component pages right margin is larger than left margin > --- > > Key: CAMEL-13881 > URL: https://issues.apache.org/jira/browse/CAMEL-13881 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Priority: Minor > Attachments: Screenshot 2019-08-20 at 10.51.48.png > > > The right margin of the component pages is larger than the left margin. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13881) Component pages right margin is larger than left margin
[ https://issues.apache.org/jira/browse/CAMEL-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated CAMEL-13881: --- Summary: Component pages right margin is larger than left margin (was: Fix component pages right margin) > Component pages right margin is larger than left margin > --- > > Key: CAMEL-13881 > URL: https://issues.apache.org/jira/browse/CAMEL-13881 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Priority: Minor > > The right margin of the component pages is larger than the left margin. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (CAMEL-13881) Fix component pages right margin
Antonin Stefanutti created CAMEL-13881: -- Summary: Fix component pages right margin Key: CAMEL-13881 URL: https://issues.apache.org/jira/browse/CAMEL-13881 Project: Camel Issue Type: Sub-task Components: website Reporter: Antonin Stefanutti The right margin of the component pages is larger than the left margin. -- This message was sent by Atlassian Jira (v8.3.2#803003)
