[jira] [Commented] (CAMEL-14746) camel-rest-swagger java.lang.IllegalArgumentException when Swagger specification don't have "scheme" object and get this specification by "file;" resource
[
https://issues.apache.org/jira/browse/CAMEL-14746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063102#comment-17063102
]
Dmitry Volodin commented on CAMEL-14746:
[~lukymiv] thanks for reporting, we will fix it in the future.
As workaround, you just need to define
{code:json}
"schemes": [
"http"
],
{code}
inside your swagger json
> camel-rest-swagger java.lang.IllegalArgumentException when Swagger
> specification don't have "scheme" object and get this specification by
> "file;" resource
> --
>
> Key: CAMEL-14746
> URL: https://issues.apache.org/jira/browse/CAMEL-14746
> Project: Camel
> Issue Type: Bug
> Components: camel-rest-swagger
>Affects Versions: 2.25.0
>Reporter: Mikhail Lukyanov
>Assignee: Dmitry Volodin
>Priority: Minor
>
> *camelContext*
>
> __
> _http://www.springframework.org/schema/beans"_
> _xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"_
> _xsi:schemaLocation="http://camel.apache.org/schema/spring
> [http://camel.apache.org/schema/spring/camel-spring.xsd]
> [http://www.springframework.org/schema/beans]
> [http://www.springframework.org/schema/beans/spring-beans.xsd];>_
> _ xmlns="http://camel.apache.org/schema/spring; >_
> __
> __
> _ uri="swagger*:file*:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json#downloadUsingGET"/>_
> __
> __
> __
> _ class="org.apache.camel.component.rest.swagger.RestSwaggerComponent">_
> __
> __
> __
>
> *Swagger.json*
>
> _{_
> _"swagger": "2.0",_
> _"info": {_
> _"description": "Api Documentation",_
> _"version": "1.0",_
> _"title": "Api Documentation",_
> _"termsOfService": "urn:tos",_
> _"contact": {},_
> _"license": {_
> _"name": "Apache 2.0",_
> _"url": "http://www.apache.org/licenses/LICENSE-2.0"_
> _}_
> _},_
> _"host": "localhost:8182",_
> _"basePath": "/manager",_
> _"tags": [_
> _{_
> _"name": "Logs",_
> _"description": "API for logs"_
> _}_
> _],_
> _"paths": {_
> _"/api/log/download": {_
> _"get": {_
> _"tags": [_
> _"Работа с логами"_
> _],_
> _"summary": "Export",_
> _"operationId": "downloadUsingGET",_
> _"produces": [_
> _"*/*"_
> _],_
> _"responses": {_
> _"200": {_
> _"description": "OK"_
> _},_
> _"401": {_
> _"description": "Unauthorized"_
> _},_
> _"403": {_
> "description": "Forbidden"
> },
> "404":
> { "description": "Not Found" }
> },
> "deprecated": false
> }
> }
> }
> }
>
> *Error*
>
> {color:#de350b}Caused by: org.apache.camel.FailedToCreateProducerException:
> Failed to create Producer for endpoint:
> swagger://[file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET|file:///C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET].
> Reason: java.lang.IllegalArgumentException: The endpoint is not of type:
> class org.apache.camel.component.http.HttpEndpoint but is:
> org.apache.camel.component.file.FileEndpointCaused by:
> org.apache.camel.FailedToCreateProducerException: Failed to create Producer
> for endpoint:
> swagger://[file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET|file:///C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET].
> Reason: java.lang.IllegalArgumentException: The endpoint is not of type:
> class org.apache.camel.component.http.HttpEndpoint but is:
> org.apache.camel.component.file.FileEndpoint{color}
>
> {color:#172b4d}When I get the same swagger specification through the resource
> "http:" everything is ok{color}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14747) Put all the EIP documentation in one place, and possibly version it.
David Jencks created CAMEL-14747: Summary: Put all the EIP documentation in one place, and possibly version it. Key: CAMEL-14747 URL: https://issues.apache.org/jira/browse/CAMEL-14747 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.1.0 Reporter: David Jencks Assignee: David Jencks * move all the EIP documentation to core/camel-core-engine to be with the partially generated documentation. I plan to move pages referencing an EIP in [http://www.enterpriseintegrationpatterns.com|http://www.enterpriseintegrationpatterns.com/] and, if I can find them, other closely related pages. * Consider where this module would best live as part of a versioned component. It could be added to the components component or made a standalone component. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14746) camel-rest-swagger java.lang.IllegalArgumentException when Swagger specification don't have "scheme" object and get this specification by "file;" resource
[
https://issues.apache.org/jira/browse/CAMEL-14746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-14746:
--
Assignee: Dmitry Volodin
> camel-rest-swagger java.lang.IllegalArgumentException when Swagger
> specification don't have "scheme" object and get this specification by
> "file;" resource
> --
>
> Key: CAMEL-14746
> URL: https://issues.apache.org/jira/browse/CAMEL-14746
> Project: Camel
> Issue Type: Bug
> Components: camel-rest-swagger
>Affects Versions: 2.25.0
>Reporter: Mikhail Lukyanov
>Assignee: Dmitry Volodin
>Priority: Minor
>
> *camelContext*
>
> __
> _http://www.springframework.org/schema/beans"_
> _xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"_
> _xsi:schemaLocation="http://camel.apache.org/schema/spring
> [http://camel.apache.org/schema/spring/camel-spring.xsd]
> [http://www.springframework.org/schema/beans]
> [http://www.springframework.org/schema/beans/spring-beans.xsd];>_
> _ xmlns="http://camel.apache.org/schema/spring; >_
> __
> __
> _ uri="swagger*:file*:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json#downloadUsingGET"/>_
> __
> __
> __
> _ class="org.apache.camel.component.rest.swagger.RestSwaggerComponent">_
> __
> __
> __
>
> *Swagger.json*
>
> _{_
> _"swagger": "2.0",_
> _"info": {_
> _"description": "Api Documentation",_
> _"version": "1.0",_
> _"title": "Api Documentation",_
> _"termsOfService": "urn:tos",_
> _"contact": {},_
> _"license": {_
> _"name": "Apache 2.0",_
> _"url": "http://www.apache.org/licenses/LICENSE-2.0"_
> _}_
> _},_
> _"host": "localhost:8182",_
> _"basePath": "/manager",_
> _"tags": [_
> _{_
> _"name": "Logs",_
> _"description": "API for logs"_
> _}_
> _],_
> _"paths": {_
> _"/api/log/download": {_
> _"get": {_
> _"tags": [_
> _"Работа с логами"_
> _],_
> _"summary": "Export",_
> _"operationId": "downloadUsingGET",_
> _"produces": [_
> _"*/*"_
> _],_
> _"responses": {_
> _"200": {_
> _"description": "OK"_
> _},_
> _"401": {_
> _"description": "Unauthorized"_
> _},_
> _"403": {_
> "description": "Forbidden"
> },
> "404":
> { "description": "Not Found" }
> },
> "deprecated": false
> }
> }
> }
> }
>
> *Error*
>
> {color:#de350b}Caused by: org.apache.camel.FailedToCreateProducerException:
> Failed to create Producer for endpoint:
> swagger://[file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET|file:///C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET].
> Reason: java.lang.IllegalArgumentException: The endpoint is not of type:
> class org.apache.camel.component.http.HttpEndpoint but is:
> org.apache.camel.component.file.FileEndpointCaused by:
> org.apache.camel.FailedToCreateProducerException: Failed to create Producer
> for endpoint:
> swagger://[file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET|file:///C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET].
> Reason: java.lang.IllegalArgumentException: The endpoint is not of type:
> class org.apache.camel.component.http.HttpEndpoint but is:
> org.apache.camel.component.file.FileEndpoint{color}
>
> {color:#172b4d}When I get the same swagger specification through the resource
> "http:" everything is ok{color}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14666) Search results push the website's Navbar
[ https://issues.apache.org/jira/browse/CAMEL-14666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Agha Saad Fraz resolved CAMEL-14666. Resolution: Fixed > Search results push the website's Navbar > > > Key: CAMEL-14666 > URL: https://issues.apache.org/jira/browse/CAMEL-14666 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Agha Saad Fraz >Priority: Minor > Labels: help-wanted > Attachments: image-2020-03-06-15-35-11-524.png > > > To produce the bug follow these steps: > > Go to [https://camel.apache.org/] > > Try to search for anything. > > The search result will push the navbar to left. > Screenshot: > !image-2020-03-06-15-35-11-524.png|width=571,height=263! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13923) Fix incorrectly escaped simple expressions in migrated manual pages
[ https://issues.apache.org/jira/browse/CAMEL-13923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062744#comment-17062744 ] Rimsha Chaudhry commented on CAMEL-13923: - Hi [~Menekam] are you still working on this issue? > Fix incorrectly escaped simple expressions in migrated manual pages > --- > > Key: CAMEL-13923 > URL: https://issues.apache.org/jira/browse/CAMEL-13923 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Jan Bednar >Priority: Major > Labels: help-wanted > Time Spent: 20m > Remaining Estimate: 0h > > E.g. section "USING DYNAMIC URIS" in > [https://camel.apache.org/manual/latest/content-enricher.html], but it can be > seen in many pages. There is already one user, which attempted to implement > these backslashes into his code (CAMEL-13922). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14592) Correct the camel-gson documentation
[ https://issues.apache.org/jira/browse/CAMEL-14592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14592. - Resolution: Fixed > Correct the camel-gson documentation > > > Key: CAMEL-14592 > URL: https://issues.apache.org/jira/browse/CAMEL-14592 > Project: Camel > Issue Type: Task > Components: camel-gson >Affects Versions: 3.1.0 >Reporter: Alex Dettinger >Assignee: Claus Ibsen >Priority: Minor > Labels: help-wanted > Fix For: 3.2.0 > > > The doc says GsonDataFormat implements a useList option according to > [https://github.com/apache/camel/blob/master/components/camel-gson/src/main/docs/json-gson-dataformat.adoc]. > But, it turns out this is not true. Same applies for gson/allowUnmarshallType. > I suspect other json components may be impacted too. There may be an issue in > documentation generation from camel model. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14208) camel-undertow: add option to secure endpoints with Keycloak on spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-14208?focusedWorklogId=406363=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-406363 ] ASF GitHub Bot logged work on CAMEL-14208: -- Author: ASF GitHub Bot Created on: 19/Mar/20 16:16 Start Date: 19/Mar/20 16:16 Worklog Time Spent: 10m Work Description: omarsmak commented on pull request #3652: CAMEL-14208 camel-undertow: add option to secure endpoints with Keycl… URL: https://github.com/apache/camel/pull/3652 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: 406363) Time Spent: 20m (was: 10m) > camel-undertow: add option to secure endpoints with Keycloak on spring-boot > --- > > Key: CAMEL-14208 > URL: https://issues.apache.org/jira/browse/CAMEL-14208 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Affects Versions: 3.0.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.x > > Time Spent: 20m > Remaining Estimate: 0h > > It should be possible to configure Keycloak adapter with spring-boot to > secure endpoints. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14746) camel-rest-swagger java.lang.IllegalArgumentException when Swagger specification don't have "scheme" object and get this specification by "file;" resource
[
https://issues.apache.org/jira/browse/CAMEL-14746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Lukyanov updated CAMEL-14746:
-
Summary: camel-rest-swagger java.lang.IllegalArgumentException when Swagger
specification don't have "scheme" object and get this specification by "file;"
resource (was: camel-rest-swagger java.lang.IllegalArgumentException when
Swagger specification don't have "scheme" object and get this specification by
by "file;" resource)
> camel-rest-swagger java.lang.IllegalArgumentException when Swagger
> specification don't have "scheme" object and get this specification by
> "file;" resource
> --
>
> Key: CAMEL-14746
> URL: https://issues.apache.org/jira/browse/CAMEL-14746
> Project: Camel
> Issue Type: Bug
> Components: camel-rest-swagger
>Affects Versions: 2.25.0
>Reporter: Mikhail Lukyanov
>Priority: Minor
>
> *camelContext*
>
> __
> _http://www.springframework.org/schema/beans"_
> _xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"_
> _xsi:schemaLocation="http://camel.apache.org/schema/spring
> [http://camel.apache.org/schema/spring/camel-spring.xsd]
> [http://www.springframework.org/schema/beans]
> [http://www.springframework.org/schema/beans/spring-beans.xsd];>_
> _ xmlns="http://camel.apache.org/schema/spring; >_
> __
> __
> _ uri="swagger*:file*:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json#downloadUsingGET"/>_
> __
> __
> __
> _ class="org.apache.camel.component.rest.swagger.RestSwaggerComponent">_
> __
> __
> __
>
> *Swagger.json*
>
> _{_
> _"swagger": "2.0",_
> _"info": {_
> _"description": "Api Documentation",_
> _"version": "1.0",_
> _"title": "Api Documentation",_
> _"termsOfService": "urn:tos",_
> _"contact": {},_
> _"license": {_
> _"name": "Apache 2.0",_
> _"url": "http://www.apache.org/licenses/LICENSE-2.0"_
> _}_
> _},_
> _"host": "localhost:8182",_
> _"basePath": "/manager",_
> _"tags": [_
> _{_
> _"name": "Logs",_
> _"description": "API for logs"_
> _}_
> _],_
> _"paths": {_
> _"/api/log/download": {_
> _"get": {_
> _"tags": [_
> _"Работа с логами"_
> _],_
> _"summary": "Export",_
> _"operationId": "downloadUsingGET",_
> _"produces": [_
> _"*/*"_
> _],_
> _"responses": {_
> _"200": {_
> _"description": "OK"_
> _},_
> _"401": {_
> _"description": "Unauthorized"_
> _},_
> _"403": {_
> "description": "Forbidden"
> },
> "404":
> { "description": "Not Found" }
> },
> "deprecated": false
> }
> }
> }
> }
>
> *Error*
>
> {color:#de350b}Caused by: org.apache.camel.FailedToCreateProducerException:
> Failed to create Producer for endpoint:
> swagger://[file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET|file:///C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET].
> Reason: java.lang.IllegalArgumentException: The endpoint is not of type:
> class org.apache.camel.component.http.HttpEndpoint but is:
> org.apache.camel.component.file.FileEndpointCaused by:
> org.apache.camel.FailedToCreateProducerException: Failed to create Producer
> for endpoint:
> swagger://[file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET|file:///C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET].
> Reason: java.lang.IllegalArgumentException: The endpoint is not of type:
> class org.apache.camel.component.http.HttpEndpoint but is:
> org.apache.camel.component.file.FileEndpoint{color}
>
> {color:#172b4d}When I get the same swagger specification through the resource
> "http:" everything is ok{color}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14739) RouteContext missing for RedeliveryErrorHandler
[ https://issues.apache.org/jira/browse/CAMEL-14739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062718#comment-17062718 ] Nathan commented on CAMEL-14739: I've added an example with 3 rest operations to show the different cases, it took some extra time since the condition for which the bug happens is apparently not after a route call, but only after a route call that directs to another route call. > RouteContext missing for RedeliveryErrorHandler > --- > > Key: CAMEL-14739 > URL: https://issues.apache.org/jira/browse/CAMEL-14739 > Project: Camel > Issue Type: Bug > Components: came-core >Affects Versions: 3.1.0 >Reporter: Nathan >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.2.0 > > Attachments: camel-error-test.zip > > > The RedeliveryErrorHandler needs the RouteContext to determine which > onException rule to use. > The RouteContext is set at the start of a route, when leaving a route the > RouteContext should be set to the route that called it. However it is > apparently null, which means that if an error happens at that point it cannot > use the onException rules that have been set. > In 3.0 the RouteContext was a stack so it kept track of all the routes that > it passed, meaning automatically returned to the parent RouteContext value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14739) RouteContext missing for RedeliveryErrorHandler
[ https://issues.apache.org/jira/browse/CAMEL-14739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan updated CAMEL-14739: --- Attachment: camel-error-test.zip > RouteContext missing for RedeliveryErrorHandler > --- > > Key: CAMEL-14739 > URL: https://issues.apache.org/jira/browse/CAMEL-14739 > Project: Camel > Issue Type: Bug > Components: came-core >Affects Versions: 3.1.0 >Reporter: Nathan >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.2.0 > > Attachments: camel-error-test.zip > > > The RedeliveryErrorHandler needs the RouteContext to determine which > onException rule to use. > The RouteContext is set at the start of a route, when leaving a route the > RouteContext should be set to the route that called it. However it is > apparently null, which means that if an error happens at that point it cannot > use the onException rules that have been set. > In 3.0 the RouteContext was a stack so it kept track of all the routes that > it passed, meaning automatically returned to the parent RouteContext value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14745) Navbar hamburger doesn't fit within the visible screen.
[ https://issues.apache.org/jira/browse/CAMEL-14745?focusedWorklogId=406316=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-406316 ] ASF GitHub Bot logged work on CAMEL-14745: -- Author: ASF GitHub Bot Created on: 19/Mar/20 15:20 Start Date: 19/Mar/20 15:20 Worklog Time Spent: 10m Work Description: AemieJ commented on pull request #241: CAMEL-14745: Navbar doesn't fit the screen resolved for few pages URL: https://github.com/apache/camel-website/pull/241 * It was observed that certain webpages under smaller screen width, the entire webpage doesn't fit the screen and the user needs to scroll through the screen to access the navbar. It is observed in several webpages. * Currently, I have resolved this issue for **DOWNLOADS**, **FRONTPAGE**, **SUPPORT** pages, and the navbar and all its content fit within the screen for any width. ### ISSUE OBSERVED IN DOWNLOADS PAGE AS THE TABLE WAS CREATING THE ISSUE.  ### SOLUTION TO RESOLVE THE ISSUE BY WRAPPING THE TABLE UNDER THE TABLE-WRAPPER  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: 406316) Remaining Estimate: 0h Time Spent: 10m > Navbar hamburger doesn't fit within the visible screen. > > > Key: CAMEL-14745 > URL: https://issues.apache.org/jira/browse/CAMEL-14745 > Project: Camel > Issue Type: Bug >Reporter: Aemie >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > For particular webpages, within a smaller screen width, due to a few links or > tables or text, the entire webpage doesn't fit within the screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14592) Correct the camel-gson documentation
[ https://issues.apache.org/jira/browse/CAMEL-14592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-14592: --- Assignee: Claus Ibsen > Correct the camel-gson documentation > > > Key: CAMEL-14592 > URL: https://issues.apache.org/jira/browse/CAMEL-14592 > Project: Camel > Issue Type: Task > Components: camel-gson >Affects Versions: 3.1.0 >Reporter: Alex Dettinger >Assignee: Claus Ibsen >Priority: Minor > Labels: help-wanted > Fix For: 3.2.0 > > > The doc says GsonDataFormat implements a useList option according to > [https://github.com/apache/camel/blob/master/components/camel-gson/src/main/docs/json-gson-dataformat.adoc]. > But, it turns out this is not true. Same applies for gson/allowUnmarshallType. > I suspect other json components may be impacted too. There may be an issue in > documentation generation from camel model. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14746) camel-rest-swagger java.lang.IllegalArgumentException when Swagger specification don't have "scheme" object and get this specification by by "file;" resource
[
https://issues.apache.org/jira/browse/CAMEL-14746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Lukyanov updated CAMEL-14746:
-
Description:
*camelContext*
__
_http://www.springframework.org/schema/beans"_
_xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"_
_xsi:schemaLocation="http://camel.apache.org/schema/spring
[http://camel.apache.org/schema/spring/camel-spring.xsd]
[http://www.springframework.org/schema/beans]
[http://www.springframework.org/schema/beans/spring-beans.xsd];>_
_http://camel.apache.org/schema/spring;
>_
__
__
__
__
__
__
__
__
__
__
*Swagger.json*
_{_
_"swagger": "2.0",_
_"info": {_
_"description": "Api Documentation",_
_"version": "1.0",_
_"title": "Api Documentation",_
_"termsOfService": "urn:tos",_
_"contact": {},_
_"license": {_
_"name": "Apache 2.0",_
_"url": "http://www.apache.org/licenses/LICENSE-2.0"_
_}_
_},_
_"host": "localhost:8182",_
_"basePath": "/manager",_
_"tags": [_
_{_
_"name": "Logs",_
_"description": "API for logs"_
_}_
_],_
_"paths": {_
_"/api/log/download": {_
_"get": {_
_"tags": [_
_"Работа с логами"_
_],_
_"summary": "Export",_
_"operationId": "downloadUsingGET",_
_"produces": [_
_"*/*"_
_],_
_"responses": {_
_"200": {_
_"description": "OK"_
_},_
_"401": {_
_"description": "Unauthorized"_
_},_
_"403": {_
"description": "Forbidden"
},
"404":
{ "description": "Not Found" }
},
"deprecated": false
}
}
}
}
*Error*
{color:#de350b}Caused by: org.apache.camel.FailedToCreateProducerException:
Failed to create Producer for endpoint:
swagger://[file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET|file:///C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET].
Reason: java.lang.IllegalArgumentException: The endpoint is not of type: class
org.apache.camel.component.http.HttpEndpoint but is:
org.apache.camel.component.file.FileEndpointCaused by:
org.apache.camel.FailedToCreateProducerException: Failed to create Producer for
endpoint:
swagger://[file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET|file:///C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET].
Reason: java.lang.IllegalArgumentException: The endpoint is not of type: class
org.apache.camel.component.http.HttpEndpoint but is:
org.apache.camel.component.file.FileEndpoint{color}
{color:#172b4d}When I get the same swagger specification through the resource
"http:" everything is ok{color}
was:
*camelContext*
__
_http://www.springframework.org/schema/beans"_
_xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"_
_xsi:schemaLocation="http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;>_
_http://camel.apache.org/schema/spring;
>_
__
__
__
__
__
__
__
__
__
__
__
__
*Swagger.json*
_{_
_"swagger": "2.0",_
_"info": {_
_"description": "Api Documentation",_
_"version": "1.0",_
_"title": "Api Documentation",_
_"termsOfService": "urn:tos",_
_"contact": {},_
_"license": {_
_"name": "Apache 2.0",_
_"url": "http://www.apache.org/licenses/LICENSE-2.0"_
_}_
_},_
_"host": "localhost:8182",_
_"basePath": "/manager",_
_"tags": [_
_{_
_"name": "Logs",_
_"description": "API for logs"_
_}_
_],_
_"paths": {_
_"/api/log/download": {_
_"get": {_
_"tags": [_
_"Работа с логами"_
_],_
_"summary": "Export",_
_"operationId": "downloadUsingGET",_
_"produces": [_
_"*/*"_
_],_
_"responses": {_
_"200": {_
_"description": "OK"_
_},_
_"401": {_
_"description": "Unauthorized"_
_},_
_"403": {_
"description": "Forbidden"
},
"404": {
"description": "Not Found"
}
},
"deprecated": false
}
}
}
}
*Error*
{color:#de350b}Caused by: org.apache.camel.FailedToCreateProducerException:
Failed to create Producer for endpoint:
swagger://file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET.
Reason: java.lang.IllegalArgumentException: The endpoint is not of type: class
org.apache.camel.component.http.HttpEndpoint but is:
org.apache.camel.component.file.FileEndpointCaused by:
org.apache.camel.FailedToCreateProducerException: Failed to create Producer for
endpoint:
swagger://file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET.
Reason: java.lang.IllegalArgumentException: The endpoint is not of type: class
org.apache.camel.component.http.HttpEndpoint but is:
org.apache.camel.component.file.FileEndpoint{color}
{color:#172b4d}When I get the
[jira] [Created] (CAMEL-14746) camel-rest-swagger java.lang.IllegalArgumentException when Swagger specification don't have "scheme" object and get this specification by by "file;" resource
Mikhail Lukyanov created CAMEL-14746:
Summary: camel-rest-swagger java.lang.IllegalArgumentException
when Swagger specification don't have "scheme" object and get this
specification by by "file;" resource
Key: CAMEL-14746
URL: https://issues.apache.org/jira/browse/CAMEL-14746
Project: Camel
Issue Type: Bug
Components: camel-rest-swagger
Affects Versions: 2.25.0
Reporter: Mikhail Lukyanov
*camelContext*
__
_http://www.springframework.org/schema/beans"_
_xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"_
_xsi:schemaLocation="http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;>_
_http://camel.apache.org/schema/spring;
>_
__
__
__
__
__
__
__
__
__
__
__
__
*Swagger.json*
_{_
_"swagger": "2.0",_
_"info": {_
_"description": "Api Documentation",_
_"version": "1.0",_
_"title": "Api Documentation",_
_"termsOfService": "urn:tos",_
_"contact": {},_
_"license": {_
_"name": "Apache 2.0",_
_"url": "http://www.apache.org/licenses/LICENSE-2.0"_
_}_
_},_
_"host": "localhost:8182",_
_"basePath": "/manager",_
_"tags": [_
_{_
_"name": "Logs",_
_"description": "API for logs"_
_}_
_],_
_"paths": {_
_"/api/log/download": {_
_"get": {_
_"tags": [_
_"Работа с логами"_
_],_
_"summary": "Export",_
_"operationId": "downloadUsingGET",_
_"produces": [_
_"*/*"_
_],_
_"responses": {_
_"200": {_
_"description": "OK"_
_},_
_"401": {_
_"description": "Unauthorized"_
_},_
_"403": {_
"description": "Forbidden"
},
"404": {
"description": "Not Found"
}
},
"deprecated": false
}
}
}
}
*Error*
{color:#de350b}Caused by: org.apache.camel.FailedToCreateProducerException:
Failed to create Producer for endpoint:
swagger://file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET.
Reason: java.lang.IllegalArgumentException: The endpoint is not of type: class
org.apache.camel.component.http.HttpEndpoint but is:
org.apache.camel.component.file.FileEndpointCaused by:
org.apache.camel.FailedToCreateProducerException: Failed to create Producer for
endpoint:
swagger://file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET.
Reason: java.lang.IllegalArgumentException: The endpoint is not of type: class
org.apache.camel.component.http.HttpEndpoint but is:
org.apache.camel.component.file.FileEndpoint{color}
{color:#172b4d}When I get the same swagger specification through the resource
"http:" everything is ok{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14592) Correct the camel-gson documentation
[ https://issues.apache.org/jira/browse/CAMEL-14592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062653#comment-17062653 ] Claus Ibsen commented on CAMEL-14592: - It a bit how json dataformat was designed that it has some options that are only for X and Y and not Z etc. Its a bit of pain but we would need to markup which ones in the dataformat impl to have it exclude the ones it dont use > Correct the camel-gson documentation > > > Key: CAMEL-14592 > URL: https://issues.apache.org/jira/browse/CAMEL-14592 > Project: Camel > Issue Type: Task > Components: camel-gson >Affects Versions: 3.1.0 >Reporter: Alex Dettinger >Priority: Minor > Labels: help-wanted > Fix For: 3.2.0 > > > The doc says GsonDataFormat implements a useList option according to > [https://github.com/apache/camel/blob/master/components/camel-gson/src/main/docs/json-gson-dataformat.adoc]. > But, it turns out this is not true. Same applies for gson/allowUnmarshallType. > I suspect other json components may be impacted too. There may be an issue in > documentation generation from camel model. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14745) Navbar hamburger doesn't fit within the visible screen.
[ https://issues.apache.org/jira/browse/CAMEL-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062652#comment-17062652 ] Aemie commented on CAMEL-14745: --- I have already started working on the issue and will create a PR for this. > Navbar hamburger doesn't fit within the visible screen. > > > Key: CAMEL-14745 > URL: https://issues.apache.org/jira/browse/CAMEL-14745 > Project: Camel > Issue Type: Bug >Reporter: Aemie >Priority: Major > > For particular webpages, within a smaller screen width, due to a few links or > tables or text, the entire webpage doesn't fit within the screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14745) Navbar hamburger doesn't fit within the visible screen.
Aemie created CAMEL-14745: - Summary: Navbar hamburger doesn't fit within the visible screen. Key: CAMEL-14745 URL: https://issues.apache.org/jira/browse/CAMEL-14745 Project: Camel Issue Type: Bug Reporter: Aemie For particular webpages, within a smaller screen width, due to a few links or tables or text, the entire webpage doesn't fit within the screen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14208) camel-undertow: add option to secure endpoints with Keycloak on spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-14208?focusedWorklogId=406270=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-406270 ] ASF GitHub Bot logged work on CAMEL-14208: -- Author: ASF GitHub Bot Created on: 19/Mar/20 14:38 Start Date: 19/Mar/20 14:38 Worklog Time Spent: 10m Work Description: JiriOndrusek commented on pull request #3652: CAMEL-14208 camel-undertow: add option to secure endpoints with Keycl… URL: https://github.com/apache/camel/pull/3652 Issue: https://issues.apache.org/jira/browse/CAMEL-14208 Added SPI API for plugging security providers into camel-undertow component. Doc is updated, JUnit test created. Changes in camel-elytron are not so important. It will be hardly refactored in follow-up fix (see https://issues.apache.org/jira/browse/CAMEL-14743). 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: 406270) Remaining Estimate: 0h Time Spent: 10m > camel-undertow: add option to secure endpoints with Keycloak on spring-boot > --- > > Key: CAMEL-14208 > URL: https://issues.apache.org/jira/browse/CAMEL-14208 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Affects Versions: 3.0.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.x > > Time Spent: 10m > Remaining Estimate: 0h > > It should be possible to configure Keycloak adapter with spring-boot to > secure endpoints. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14744) camel-salesforce : lazy-login
[ https://issues.apache.org/jira/browse/CAMEL-14744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Tutak updated CAMEL-14744: -- Description: I'm using org.apache.camel.springboot:camel-salesforce-starter:3.1.0 Configuration *camel.component.salesforce.lazy-login* only seems to work when it's used in combination with *camel.component.salesforce.lazy-start-producer*. When used on it's own, method *_org.apache.camel.component.salesforce.internal.client.AbstractClientBase#start()_* will call method _*org.apache.camel.component.salesforce.internal.SalesforceSession#login()*_ without an appropriate guard statement. Is this intended behaviour? was: I'm using org.apache.camel.springboot:camel-salesforce-starter:3.1.0 Configuration *camel.component.salesforce.lazy-login* only ** seems to work when it's used in combination with *camel.component.salesforce.lazy-start-producer*. When used on it's own, method *_org.apache.camel.component.salesforce.internal.client.AbstractClientBase#start()_* will call method _*org.apache.camel.component.salesforce.internal.SalesforceSession#login()*_ without an appropriate guard statement. Is this intended behaviour? > camel-salesforce : lazy-login > - > > Key: CAMEL-14744 > URL: https://issues.apache.org/jira/browse/CAMEL-14744 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.1.0 >Reporter: Maarten Tutak >Priority: Minor > > I'm using org.apache.camel.springboot:camel-salesforce-starter:3.1.0 > Configuration *camel.component.salesforce.lazy-login* only seems to work when > it's used in combination with > *camel.component.salesforce.lazy-start-producer*. > When used on it's own, method > > *_org.apache.camel.component.salesforce.internal.client.AbstractClientBase#start()_* > will call method > _*org.apache.camel.component.salesforce.internal.SalesforceSession#login()*_ > without an appropriate guard statement. > Is this intended behaviour? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14744) camel-salesforce : lazy-login
Maarten Tutak created CAMEL-14744: - Summary: camel-salesforce : lazy-login Key: CAMEL-14744 URL: https://issues.apache.org/jira/browse/CAMEL-14744 Project: Camel Issue Type: Bug Components: camel-salesforce Affects Versions: 3.1.0 Reporter: Maarten Tutak I'm using org.apache.camel.springboot:camel-salesforce-starter:3.1.0 Configuration *camel.component.salesforce.lazy-login* only ** seems to work when it's used in combination with *camel.component.salesforce.lazy-start-producer*. When used on it's own, method *_org.apache.camel.component.salesforce.internal.client.AbstractClientBase#start()_* will call method _*org.apache.camel.component.salesforce.internal.SalesforceSession#login()*_ without an appropriate guard statement. Is this intended behaviour? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14743) camel-elytron: refactor component to use new SPI interface from camel-undertow
Jiri Ondrusek created CAMEL-14743: - Summary: camel-elytron: refactor component to use new SPI interface from camel-undertow Key: CAMEL-14743 URL: https://issues.apache.org/jira/browse/CAMEL-14743 Project: Camel Issue Type: Bug Components: camel-undertow Affects Versions: 3.2.0 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek As a part of the fix of https://issues.apache.org/jira/browse/CAMEL-14208 there is a new SPI APi for security providers. Component camel-elytron should be refactored to use that api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14605) EIP docs - The options are not automatic updated on build
[ https://issues.apache.org/jira/browse/CAMEL-14605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14605. - Resolution: Fixed Davids work should do this > EIP docs - The options are not automatic updated on build > - > > Key: CAMEL-14605 > URL: https://issues.apache.org/jira/browse/CAMEL-14605 > Project: Camel > Issue Type: Task > Components: build system, camel-core, documentation >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The EIP docs has // START // END markers for the options table. We should > automatic keep them up to date based on the .json metadata. This used to work > in the past. > The docs are in core/camel-core-engine/src/main/docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?focusedWorklogId=406154=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-406154 ] ASF GitHub Bot logged work on CAMEL-14742: -- Author: ASF GitHub Bot Created on: 19/Mar/20 13:08 Start Date: 19/Mar/20 13:08 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #3651: CAMEL-14742 - Prevent JMX rebinding URL: https://github.com/apache/camel/pull/3651 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: 406154) Remaining Estimate: 0h Time Spent: 10m > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1, 3.2.0, 3.1.1 > > Time Spent: 10m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14742) Prevent JMX rebinding
Colm O hEigeartaigh created CAMEL-14742: --- Summary: Prevent JMX rebinding Key: CAMEL-14742 URL: https://issues.apache.org/jira/browse/CAMEL-14742 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.2, 2.25.1, 3.2.0, 3.1.1 This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14741) The FluentProducerTemplate.withTemplateCustomizer is broken
[
https://issues.apache.org/jira/browse/CAMEL-14741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-14741.
-
Resolution: Fixed
> The FluentProducerTemplate.withTemplateCustomizer is broken
> ---
>
> Key: CAMEL-14741
> URL: https://issues.apache.org/jira/browse/CAMEL-14741
> Project: Camel
> Issue Type: Task
> Components: camel-core
>Reporter: Guillaume Nodet
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.2.0
>
>
> I think the {{withTemplateCustomizer}} is never called because it is only
> used when the {{DefaultFluentProducerTemplate}} is started (the first time
> {{template()}} is called, but this happens just after the
> {{DefaultFluentProducerTemplate}} is created inside the
> {{CamelContext.createFluentProducerTemplate()}} method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14741) The FluentProducerTemplate.withTemplateCustomizer is broken
[
https://issues.apache.org/jira/browse/CAMEL-14741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-14741:
Component/s: camel-core
> The FluentProducerTemplate.withTemplateCustomizer is broken
> ---
>
> Key: CAMEL-14741
> URL: https://issues.apache.org/jira/browse/CAMEL-14741
> Project: Camel
> Issue Type: Task
> Components: camel-core
>Reporter: Guillaume Nodet
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.2.0
>
>
> I think the {{withTemplateCustomizer}} is never called because it is only
> used when the {{DefaultFluentProducerTemplate}} is started (the first time
> {{template()}} is called, but this happens just after the
> {{DefaultFluentProducerTemplate}} is created inside the
> {{CamelContext.createFluentProducerTemplate()}} method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14741) The FluentProducerTemplate.withTemplateCustomizer is broken
[
https://issues.apache.org/jira/browse/CAMEL-14741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-14741:
Priority: Minor (was: Major)
> The FluentProducerTemplate.withTemplateCustomizer is broken
> ---
>
> Key: CAMEL-14741
> URL: https://issues.apache.org/jira/browse/CAMEL-14741
> Project: Camel
> Issue Type: Task
>Reporter: Guillaume Nodet
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.2.0
>
>
> I think the {{withTemplateCustomizer}} is never called because it is only
> used when the {{DefaultFluentProducerTemplate}} is started (the first time
> {{template()}} is called, but this happens just after the
> {{DefaultFluentProducerTemplate}} is created inside the
> {{CamelContext.createFluentProducerTemplate()}} method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14741) The FluentProducerTemplate.withTemplateCustomizer is broken
[
https://issues.apache.org/jira/browse/CAMEL-14741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-14741:
Fix Version/s: 3.2.0
> The FluentProducerTemplate.withTemplateCustomizer is broken
> ---
>
> Key: CAMEL-14741
> URL: https://issues.apache.org/jira/browse/CAMEL-14741
> Project: Camel
> Issue Type: Task
>Reporter: Guillaume Nodet
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.2.0
>
>
> I think the {{withTemplateCustomizer}} is never called because it is only
> used when the {{DefaultFluentProducerTemplate}} is started (the first time
> {{template()}} is called, but this happens just after the
> {{DefaultFluentProducerTemplate}} is created inside the
> {{CamelContext.createFluentProducerTemplate()}} method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-14741) The FluentProducerTemplate.withTemplateCustomizer is broken
[
https://issues.apache.org/jira/browse/CAMEL-14741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-14741:
---
Assignee: Claus Ibsen
> The FluentProducerTemplate.withTemplateCustomizer is broken
> ---
>
> Key: CAMEL-14741
> URL: https://issues.apache.org/jira/browse/CAMEL-14741
> Project: Camel
> Issue Type: Task
>Reporter: Guillaume Nodet
>Assignee: Claus Ibsen
>Priority: Major
>
> I think the {{withTemplateCustomizer}} is never called because it is only
> used when the {{DefaultFluentProducerTemplate}} is started (the first time
> {{template()}} is called, but this happens just after the
> {{DefaultFluentProducerTemplate}} is created inside the
> {{CamelContext.createFluentProducerTemplate()}} method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14741) The FluentProducerTemplate.withTemplateCustomizer is broken
[
https://issues.apache.org/jira/browse/CAMEL-14741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062526#comment-17062526
]
Claus Ibsen commented on CAMEL-14741:
-
Yeah or if you create a new template manually with new Default .. then you can
set the customizer and then start it.
We could re-init if the template customizer is set (used rarely anyway)
> The FluentProducerTemplate.withTemplateCustomizer is broken
> ---
>
> Key: CAMEL-14741
> URL: https://issues.apache.org/jira/browse/CAMEL-14741
> Project: Camel
> Issue Type: Task
>Reporter: Guillaume Nodet
>Priority: Major
>
> I think the {{withTemplateCustomizer}} is never called because it is only
> used when the {{DefaultFluentProducerTemplate}} is started (the first time
> {{template()}} is called, but this happens just after the
> {{DefaultFluentProducerTemplate}} is created inside the
> {{CamelContext.createFluentProducerTemplate()}} method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14679) Support DROP_ROOT_MODE in XStream JSON dataformat
[
https://issues.apache.org/jira/browse/CAMEL-14679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062499#comment-17062499
]
Claus Ibsen commented on CAMEL-14679:
-
You can now enable this but keep it disabled to be as before.
Mind that for json, then jackson or some of the other libraries are better.
xstream was for xml, and then they added some json support on top, but its not
first class imho.
> Support DROP_ROOT_MODE in XStream JSON dataformat
> --
>
> Key: CAMEL-14679
> URL: https://issues.apache.org/jira/browse/CAMEL-14679
> Project: Camel
> Issue Type: Improvement
> Components: camel-xstream
>Reporter: Peter Palaga
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.2.0
>
>
> It is currently not possible to configure
> {{org.apache.camel.dataformat.xstream.JsonDataFormat}} to produce standard
> JSON without the XStream specific root node.
> XStream JSON with root node:
> {code:json}
> {"org.apache.camel.quarkus.component.xstream.it.PojoA\:{"name":"Joe"}}{code}
> Standard JSON:
> {code:json}
> {"name":"Joe"}{code}
> With plain Xstream this can be reached via (see
> https://x-stream.github.io/json-tutorial.html#json-dropping-root )
> {code:java}
> XStream xstream = new XStream(new JsonHierarchicalStreamDriver() {
> public HierarchicalStreamWriter createWriter(Writer writer) {
> return new JsonWriter(writer, JsonWriter.DROP_ROOT_MODE);
> }
> });
> {code}
> But I have not found a way to configure the
> {{org.apache.camel.dataformat.xstream.JsonDataFormat}} in that way. So we
> probably need some change to allow this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14679) Support DROP_ROOT_MODE in XStream JSON dataformat
[
https://issues.apache.org/jira/browse/CAMEL-14679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-14679.
-
Resolution: Fixed
> Support DROP_ROOT_MODE in XStream JSON dataformat
> --
>
> Key: CAMEL-14679
> URL: https://issues.apache.org/jira/browse/CAMEL-14679
> Project: Camel
> Issue Type: Improvement
> Components: camel-xstream
>Reporter: Peter Palaga
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.2.0
>
>
> It is currently not possible to configure
> {{org.apache.camel.dataformat.xstream.JsonDataFormat}} to produce standard
> JSON without the XStream specific root node.
> XStream JSON with root node:
> {code:json}
> {"org.apache.camel.quarkus.component.xstream.it.PojoA\:{"name":"Joe"}}{code}
> Standard JSON:
> {code:json}
> {"name":"Joe"}{code}
> With plain Xstream this can be reached via (see
> https://x-stream.github.io/json-tutorial.html#json-dropping-root )
> {code:java}
> XStream xstream = new XStream(new JsonHierarchicalStreamDriver() {
> public HierarchicalStreamWriter createWriter(Writer writer) {
> return new JsonWriter(writer, JsonWriter.DROP_ROOT_MODE);
> }
> });
> {code}
> But I have not found a way to configure the
> {{org.apache.camel.dataformat.xstream.JsonDataFormat}} in that way. So we
> probably need some change to allow this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14741) The FluentProducerTemplate.withTemplateCustomizer is broken
Guillaume Nodet created CAMEL-14741:
---
Summary: The FluentProducerTemplate.withTemplateCustomizer is
broken
Key: CAMEL-14741
URL: https://issues.apache.org/jira/browse/CAMEL-14741
Project: Camel
Issue Type: Task
Reporter: Guillaume Nodet
I think the {{withTemplateCustomizer}} is never called because it is only used
when the {{DefaultFluentProducerTemplate}} is started (the first time
{{template()}} is called, but this happens just after the
{{DefaultFluentProducerTemplate}} is created inside the
{{CamelContext.createFluentProducerTemplate()}} method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14733) Properties of class Map does not work with Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-14733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062436#comment-17062436
]
Andrea Cosentino commented on CAMEL-14733:
--
Build the code by yourself. First build camel branch master, then build
camel-spring-boot master.
> Properties of class Map does not work with Spring Boot
> --
>
> Key: CAMEL-14733
> URL: https://issues.apache.org/jira/browse/CAMEL-14733
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot-starters
>Affects Versions: 3.1.0
> Environment: Camel 3.1.0
>Reporter: Hemang Ajmera
>Priority: Major
> Fix For: 3.2.0
>
> Attachments: Screenshot 2020-03-18 at 11.13.08.png
>
>
> We were migrating the salesforce component code from version 2.24.2 to
> version 3.1.0. However we are getting error
> {code}
> Caused by: org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.salesforce.httpclientproperties.requestbuffersize=65536)
> with name: httpclientproperties.requestbuffersize on bean:
> org.apache.camel.component.salesforce.SalesforceComponent@497cd25 with value:
> 65536
> {code}
> Earlier also there was issue with Map properties, which was raised in
> CAMEL-13770 and it was fixed by commit
> https://github.com/apache/camel/commit/2566504f56212b87ff5532a181cb85dfc00f2286
> This seems to be new issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14733) Properties of class Map does not work with Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-14733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062431#comment-17062431
]
Hemang Ajmera commented on CAMEL-14733:
---
I am not sure how the entire build works on master branch, but there is no
version 3.2.0-SNAPSHOT for salesforce component at
https://repository.apache.org/content/groups/snapshots/org/apache/camel/springboot/camel-salesforce-starter/
> Properties of class Map does not work with Spring Boot
> --
>
> Key: CAMEL-14733
> URL: https://issues.apache.org/jira/browse/CAMEL-14733
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot-starters
>Affects Versions: 3.1.0
> Environment: Camel 3.1.0
>Reporter: Hemang Ajmera
>Priority: Major
> Fix For: 3.2.0
>
> Attachments: Screenshot 2020-03-18 at 11.13.08.png
>
>
> We were migrating the salesforce component code from version 2.24.2 to
> version 3.1.0. However we are getting error
> {code}
> Caused by: org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.salesforce.httpclientproperties.requestbuffersize=65536)
> with name: httpclientproperties.requestbuffersize on bean:
> org.apache.camel.component.salesforce.SalesforceComponent@497cd25 with value:
> 65536
> {code}
> Earlier also there was issue with Map properties, which was raised in
> CAMEL-13770 and it was fixed by commit
> https://github.com/apache/camel/commit/2566504f56212b87ff5532a181cb85dfc00f2286
> This seems to be new issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14733) Properties of class Map does not work with Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-14733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062431#comment-17062431
]
Hemang Ajmera edited comment on CAMEL-14733 at 3/19/20, 10:18 AM:
--
I am not sure how the entire build works on master branch, but there is no
version 3.2.0-SNAPSHOT for salesforce starter component at
https://repository.apache.org/content/groups/snapshots/org/apache/camel/springboot/camel-salesforce-starter/
was (Author: hemangajmera):
I am not sure how the entire build works on master branch, but there is no
version 3.2.0-SNAPSHOT for salesforce component at
https://repository.apache.org/content/groups/snapshots/org/apache/camel/springboot/camel-salesforce-starter/
> Properties of class Map does not work with Spring Boot
> --
>
> Key: CAMEL-14733
> URL: https://issues.apache.org/jira/browse/CAMEL-14733
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot-starters
>Affects Versions: 3.1.0
> Environment: Camel 3.1.0
>Reporter: Hemang Ajmera
>Priority: Major
> Fix For: 3.2.0
>
> Attachments: Screenshot 2020-03-18 at 11.13.08.png
>
>
> We were migrating the salesforce component code from version 2.24.2 to
> version 3.1.0. However we are getting error
> {code}
> Caused by: org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.salesforce.httpclientproperties.requestbuffersize=65536)
> with name: httpclientproperties.requestbuffersize on bean:
> org.apache.camel.component.salesforce.SalesforceComponent@497cd25 with value:
> 65536
> {code}
> Earlier also there was issue with Map properties, which was raised in
> CAMEL-13770 and it was fixed by commit
> https://github.com/apache/camel/commit/2566504f56212b87ff5532a181cb85dfc00f2286
> This seems to be new issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14682) Upgrade the version of Yarn
[ https://issues.apache.org/jira/browse/CAMEL-14682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062420#comment-17062420 ] Esther Itolima edited comment on CAMEL-14682 at 3/19/20, 10:09 AM: --- [~zregvart] This Discription " h4. Description We currently use version 1.22.0, we could upgrade to to 1.22.1, or even better switch to 2.0 (berry) as it includes improvements to the PnP. Switching to 2.0 (berry) would most likely require migration effort for some of the dependencies we use. The version needs to change both for the website build and for the antora-ui-camel. Note that we vendor the Yarn within both of them via [policies|https://classic.yarnpkg.com/en/docs/cli/policies]. " Is not giving me a detailed information on how to work on the issue locally from my system. was (Author: itolimaesther): This Discription " h4. Description We currently use version 1.22.0, we could upgrade to to 1.22.1, or even better switch to 2.0 (berry) as it includes improvements to the PnP. Switching to 2.0 (berry) would most likely require migration effort for some of the dependencies we use. The version needs to change both for the website build and for the antora-ui-camel. Note that we vendor the Yarn within both of them via [policies|https://classic.yarnpkg.com/en/docs/cli/policies]. " Is not giving me a detailed information on how to work on the issue locally from my system. > Upgrade the version of Yarn > --- > > Key: CAMEL-14682 > URL: https://issues.apache.org/jira/browse/CAMEL-14682 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Minor > Labels: help-wanted > > We currently use version 1.22.0, we could upgrade to to 1.22.1, or even > better switch to 2.0 (berry) as it includes improvements to the PnP. > Switching to 2.0 (berry) would most likely require migration effort for some > of the dependencies we use. > The version needs to change both for the website build and for the > antora-ui-camel. Note that we vendor the Yarn within both of them via > [policies|https://classic.yarnpkg.com/en/docs/cli/policies]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14682) Upgrade the version of Yarn
[ https://issues.apache.org/jira/browse/CAMEL-14682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062420#comment-17062420 ] Esther Itolima commented on CAMEL-14682: This Discription " h4. Description We currently use version 1.22.0, we could upgrade to to 1.22.1, or even better switch to 2.0 (berry) as it includes improvements to the PnP. Switching to 2.0 (berry) would most likely require migration effort for some of the dependencies we use. The version needs to change both for the website build and for the antora-ui-camel. Note that we vendor the Yarn within both of them via [policies|https://classic.yarnpkg.com/en/docs/cli/policies]. " Is not giving me a detailed information on how to work on the issue locally from my system. > Upgrade the version of Yarn > --- > > Key: CAMEL-14682 > URL: https://issues.apache.org/jira/browse/CAMEL-14682 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Minor > Labels: help-wanted > > We currently use version 1.22.0, we could upgrade to to 1.22.1, or even > better switch to 2.0 (berry) as it includes improvements to the PnP. > Switching to 2.0 (berry) would most likely require migration effort for some > of the dependencies we use. > The version needs to change both for the website build and for the > antora-ui-camel. Note that we vendor the Yarn within both of them via > [policies|https://classic.yarnpkg.com/en/docs/cli/policies]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14739) RouteContext missing for RedeliveryErrorHandler
[
https://issues.apache.org/jira/browse/CAMEL-14739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062412#comment-17062412
]
Guillaume Nodet edited comment on CAMEL-14739 at 3/19/20, 9:51 AM:
---
[~uncl] do you have a simple route setup to make it easier to test ?
As [~davsclaus] indicated, the RouteContext has been removed in 3.2-SNAPSHOT,
but there should still be the stack of {{Route}}s in the {{UnitOfWork}}.
was (Author: gnt):
[~uncl] do you have a simple route setup to make it easier to test ?
> RouteContext missing for RedeliveryErrorHandler
> ---
>
> Key: CAMEL-14739
> URL: https://issues.apache.org/jira/browse/CAMEL-14739
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.1.0
>Reporter: Nathan
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.2.0
>
>
> The RedeliveryErrorHandler needs the RouteContext to determine which
> onException rule to use.
> The RouteContext is set at the start of a route, when leaving a route the
> RouteContext should be set to the route that called it. However it is
> apparently null, which means that if an error happens at that point it cannot
> use the onException rules that have been set.
> In 3.0 the RouteContext was a stack so it kept track of all the routes that
> it passed, meaning automatically returned to the parent RouteContext value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14739) RouteContext missing for RedeliveryErrorHandler
[ https://issues.apache.org/jira/browse/CAMEL-14739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062412#comment-17062412 ] Guillaume Nodet commented on CAMEL-14739: - [~uncl] do you have a simple route setup to make it easier to test ? > RouteContext missing for RedeliveryErrorHandler > --- > > Key: CAMEL-14739 > URL: https://issues.apache.org/jira/browse/CAMEL-14739 > Project: Camel > Issue Type: Bug > Components: came-core >Affects Versions: 3.1.0 >Reporter: Nathan >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.2.0 > > > The RedeliveryErrorHandler needs the RouteContext to determine which > onException rule to use. > The RouteContext is set at the start of a route, when leaving a route the > RouteContext should be set to the route that called it. However it is > apparently null, which means that if an error happens at that point it cannot > use the onException rules that have been set. > In 3.0 the RouteContext was a stack so it kept track of all the routes that > it passed, meaning automatically returned to the parent RouteContext value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14739) RouteContext missing for RedeliveryErrorHandler
[ https://issues.apache.org/jira/browse/CAMEL-14739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062409#comment-17062409 ] Claus Ibsen commented on CAMEL-14739: - The route context is removed onwards. So if you have some sample project with error handling that now works differently, then put together a sample project and attach as zip or on github. And also try with 3.2 SNAPSHOT > RouteContext missing for RedeliveryErrorHandler > --- > > Key: CAMEL-14739 > URL: https://issues.apache.org/jira/browse/CAMEL-14739 > Project: Camel > Issue Type: Bug > Components: came-core >Affects Versions: 3.1.0 >Reporter: Nathan >Priority: Major > > The RedeliveryErrorHandler needs the RouteContext to determine which > onException rule to use. > The RouteContext is set at the start of a route, when leaving a route the > RouteContext should be set to the route that called it. However it is > apparently null, which means that if an error happens at that point it cannot > use the onException rules that have been set. > In 3.0 the RouteContext was a stack so it kept track of all the routes that > it passed, meaning automatically returned to the parent RouteContext value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14739) RouteContext missing for RedeliveryErrorHandler
[ https://issues.apache.org/jira/browse/CAMEL-14739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14739: Fix Version/s: 3.2.0 > RouteContext missing for RedeliveryErrorHandler > --- > > Key: CAMEL-14739 > URL: https://issues.apache.org/jira/browse/CAMEL-14739 > Project: Camel > Issue Type: Bug > Components: came-core >Affects Versions: 3.1.0 >Reporter: Nathan >Priority: Major > Fix For: 3.2.0 > > > The RedeliveryErrorHandler needs the RouteContext to determine which > onException rule to use. > The RouteContext is set at the start of a route, when leaving a route the > RouteContext should be set to the route that called it. However it is > apparently null, which means that if an error happens at that point it cannot > use the onException rules that have been set. > In 3.0 the RouteContext was a stack so it kept track of all the routes that > it passed, meaning automatically returned to the parent RouteContext value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14739) RouteContext missing for RedeliveryErrorHandler
[ https://issues.apache.org/jira/browse/CAMEL-14739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-14739: --- Assignee: Guillaume Nodet > RouteContext missing for RedeliveryErrorHandler > --- > > Key: CAMEL-14739 > URL: https://issues.apache.org/jira/browse/CAMEL-14739 > Project: Camel > Issue Type: Bug > Components: came-core >Affects Versions: 3.1.0 >Reporter: Nathan >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.2.0 > > > The RedeliveryErrorHandler needs the RouteContext to determine which > onException rule to use. > The RouteContext is set at the start of a route, when leaving a route the > RouteContext should be set to the route that called it. However it is > apparently null, which means that if an error happens at that point it cannot > use the onException rules that have been set. > In 3.0 the RouteContext was a stack so it kept track of all the routes that > it passed, meaning automatically returned to the parent RouteContext value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14740) Error binding property in servlet-starter
[
https://issues.apache.org/jira/browse/CAMEL-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-14740:
Fix Version/s: 3.2.0
> Error binding property in servlet-starter
> -
>
> Key: CAMEL-14740
> URL: https://issues.apache.org/jira/browse/CAMEL-14740
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Reporter: Efanov Alexey
>Priority: Trivial
> Labels: starter
> Fix For: 3.2.0
>
>
> Hi,
> I have this dependencies
> {code:java}
> // Camel
> implementation 'org.apache.camel.springboot:camel-spring-boot-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-jackson-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-jacksonxml-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-activemq-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-servlet-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-rest-starter:3.1.0' {code}
> My application.properties
> {code:java}
> camel.component.servlet.mapping.enabled=true
> camel.component.servlet.mapping.context-path=/rest/*
> camel.rest.component=servlet
> camel.rest.binding-mode=json{code}
> When i run application i see this stacktrace
> {code:java}
> Exception in thread "CamelMainRunController" java.lang.RuntimeException:
> org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
> bean: org.apache.camel.component.servlet.ServletComponent@62562970 with
> value: true
> at
> org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:90)
> at
> org.apache.camel.spring.boot.CamelMainRunController$DaemonTask.run(CamelMainRunController.java:53)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
> bean: org.apache.camel.component.servlet.ServletComponent@62562970 with
> value: true
> at
> org.apache.camel.main.BaseMainSupport.setPropertiesOnTarget(BaseMainSupport.java:176)
> at
> org.apache.camel.main.BaseMainSupport.autoConfigurationFromProperties(BaseMainSupport.java:993)
> at
> org.apache.camel.main.BaseMainSupport.autoconfigure(BaseMainSupport.java:545)
> at
> org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:587)
> at
> org.apache.camel.main.BaseMainSupport.initCamelContext(BaseMainSupport.java:423)
> at org.apache.camel.main.Main.doInit(Main.java:109)
> at
> org.apache.camel.support.service.ServiceSupport.init(ServiceSupport.java:83)
> at
> org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:112)
> at org.apache.camel.main.MainSupport.run(MainSupport.java:82)
> at
> org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:85)
> ... 2 more
> {code}
> It always throw error on any first servlet property in configuration but all
> servlet properties binds correctly and works.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14740) spring-boot - Error binding property in servlet-starter
[
https://issues.apache.org/jira/browse/CAMEL-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-14740:
Priority: Major (was: Trivial)
> spring-boot - Error binding property in servlet-starter
> ---
>
> Key: CAMEL-14740
> URL: https://issues.apache.org/jira/browse/CAMEL-14740
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Reporter: Efanov Alexey
>Priority: Major
> Labels: starter
> Fix For: 3.2.0
>
>
> Hi,
> I have this dependencies
> {code:java}
> // Camel
> implementation 'org.apache.camel.springboot:camel-spring-boot-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-jackson-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-jacksonxml-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-activemq-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-servlet-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-rest-starter:3.1.0' {code}
> My application.properties
> {code:java}
> camel.component.servlet.mapping.enabled=true
> camel.component.servlet.mapping.context-path=/rest/*
> camel.rest.component=servlet
> camel.rest.binding-mode=json{code}
> When i run application i see this stacktrace
> {code:java}
> Exception in thread "CamelMainRunController" java.lang.RuntimeException:
> org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
> bean: org.apache.camel.component.servlet.ServletComponent@62562970 with
> value: true
> at
> org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:90)
> at
> org.apache.camel.spring.boot.CamelMainRunController$DaemonTask.run(CamelMainRunController.java:53)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
> bean: org.apache.camel.component.servlet.ServletComponent@62562970 with
> value: true
> at
> org.apache.camel.main.BaseMainSupport.setPropertiesOnTarget(BaseMainSupport.java:176)
> at
> org.apache.camel.main.BaseMainSupport.autoConfigurationFromProperties(BaseMainSupport.java:993)
> at
> org.apache.camel.main.BaseMainSupport.autoconfigure(BaseMainSupport.java:545)
> at
> org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:587)
> at
> org.apache.camel.main.BaseMainSupport.initCamelContext(BaseMainSupport.java:423)
> at org.apache.camel.main.Main.doInit(Main.java:109)
> at
> org.apache.camel.support.service.ServiceSupport.init(ServiceSupport.java:83)
> at
> org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:112)
> at org.apache.camel.main.MainSupport.run(MainSupport.java:82)
> at
> org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:85)
> ... 2 more
> {code}
> It always throw error on any first servlet property in configuration but all
> servlet properties binds correctly and works.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14740) spring-boot - Error binding property in servlet-starter
[
https://issues.apache.org/jira/browse/CAMEL-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-14740:
Summary: spring-boot - Error binding property in servlet-starter (was:
Error binding property in servlet-starter)
> spring-boot - Error binding property in servlet-starter
> ---
>
> Key: CAMEL-14740
> URL: https://issues.apache.org/jira/browse/CAMEL-14740
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Reporter: Efanov Alexey
>Priority: Trivial
> Labels: starter
> Fix For: 3.2.0
>
>
> Hi,
> I have this dependencies
> {code:java}
> // Camel
> implementation 'org.apache.camel.springboot:camel-spring-boot-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-jackson-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-jacksonxml-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-activemq-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-servlet-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-rest-starter:3.1.0' {code}
> My application.properties
> {code:java}
> camel.component.servlet.mapping.enabled=true
> camel.component.servlet.mapping.context-path=/rest/*
> camel.rest.component=servlet
> camel.rest.binding-mode=json{code}
> When i run application i see this stacktrace
> {code:java}
> Exception in thread "CamelMainRunController" java.lang.RuntimeException:
> org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
> bean: org.apache.camel.component.servlet.ServletComponent@62562970 with
> value: true
> at
> org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:90)
> at
> org.apache.camel.spring.boot.CamelMainRunController$DaemonTask.run(CamelMainRunController.java:53)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
> bean: org.apache.camel.component.servlet.ServletComponent@62562970 with
> value: true
> at
> org.apache.camel.main.BaseMainSupport.setPropertiesOnTarget(BaseMainSupport.java:176)
> at
> org.apache.camel.main.BaseMainSupport.autoConfigurationFromProperties(BaseMainSupport.java:993)
> at
> org.apache.camel.main.BaseMainSupport.autoconfigure(BaseMainSupport.java:545)
> at
> org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:587)
> at
> org.apache.camel.main.BaseMainSupport.initCamelContext(BaseMainSupport.java:423)
> at org.apache.camel.main.Main.doInit(Main.java:109)
> at
> org.apache.camel.support.service.ServiceSupport.init(ServiceSupport.java:83)
> at
> org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:112)
> at org.apache.camel.main.MainSupport.run(MainSupport.java:82)
> at
> org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:85)
> ... 2 more
> {code}
> It always throw error on any first servlet property in configuration but all
> servlet properties binds correctly and works.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14740) Error binding property in servlet-starter
[
https://issues.apache.org/jira/browse/CAMEL-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062405#comment-17062405
]
Claus Ibsen commented on CAMEL-14740:
-
Should be fixed in Camel 3.2, but can you verify with SNAPSHOT, you can build
from source or try the apache snapshot repo
> Error binding property in servlet-starter
> -
>
> Key: CAMEL-14740
> URL: https://issues.apache.org/jira/browse/CAMEL-14740
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Reporter: Efanov Alexey
>Priority: Trivial
> Labels: starter
>
> Hi,
> I have this dependencies
> {code:java}
> // Camel
> implementation 'org.apache.camel.springboot:camel-spring-boot-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-jackson-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-jacksonxml-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-activemq-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-servlet-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-rest-starter:3.1.0' {code}
> My application.properties
> {code:java}
> camel.component.servlet.mapping.enabled=true
> camel.component.servlet.mapping.context-path=/rest/*
> camel.rest.component=servlet
> camel.rest.binding-mode=json{code}
> When i run application i see this stacktrace
> {code:java}
> Exception in thread "CamelMainRunController" java.lang.RuntimeException:
> org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
> bean: org.apache.camel.component.servlet.ServletComponent@62562970 with
> value: true
> at
> org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:90)
> at
> org.apache.camel.spring.boot.CamelMainRunController$DaemonTask.run(CamelMainRunController.java:53)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
> bean: org.apache.camel.component.servlet.ServletComponent@62562970 with
> value: true
> at
> org.apache.camel.main.BaseMainSupport.setPropertiesOnTarget(BaseMainSupport.java:176)
> at
> org.apache.camel.main.BaseMainSupport.autoConfigurationFromProperties(BaseMainSupport.java:993)
> at
> org.apache.camel.main.BaseMainSupport.autoconfigure(BaseMainSupport.java:545)
> at
> org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:587)
> at
> org.apache.camel.main.BaseMainSupport.initCamelContext(BaseMainSupport.java:423)
> at org.apache.camel.main.Main.doInit(Main.java:109)
> at
> org.apache.camel.support.service.ServiceSupport.init(ServiceSupport.java:83)
> at
> org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:112)
> at org.apache.camel.main.MainSupport.run(MainSupport.java:82)
> at
> org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:85)
> ... 2 more
> {code}
> It always throw error on any first servlet property in configuration but all
> servlet properties binds correctly and works.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14740) Error binding property in servlet-starter
Efanov Alexey created CAMEL-14740:
-
Summary: Error binding property in servlet-starter
Key: CAMEL-14740
URL: https://issues.apache.org/jira/browse/CAMEL-14740
Project: Camel
Issue Type: Bug
Components: camel-servlet
Reporter: Efanov Alexey
Hi,
I have this dependencies
{code:java}
// Camel
implementation 'org.apache.camel.springboot:camel-spring-boot-starter:3.1.0'
implementation 'org.apache.camel.springboot:camel-jackson-starter:3.1.0'
implementation 'org.apache.camel.springboot:camel-jacksonxml-starter:3.1.0'
implementation 'org.apache.camel.springboot:camel-activemq-starter:3.1.0'
implementation 'org.apache.camel.springboot:camel-servlet-starter:3.1.0'
implementation 'org.apache.camel.springboot:camel-rest-starter:3.1.0' {code}
My application.properties
{code:java}
camel.component.servlet.mapping.enabled=true
camel.component.servlet.mapping.context-path=/rest/*
camel.rest.component=servlet
camel.rest.binding-mode=json{code}
When i run application i see this stacktrace
{code:java}
Exception in thread "CamelMainRunController" java.lang.RuntimeException:
org.apache.camel.PropertyBindingException: Error binding property
(camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
bean: org.apache.camel.component.servlet.ServletComponent@62562970 with value:
true
at
org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:90)
at
org.apache.camel.spring.boot.CamelMainRunController$DaemonTask.run(CamelMainRunController.java:53)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.apache.camel.PropertyBindingException: Error binding property
(camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
bean: org.apache.camel.component.servlet.ServletComponent@62562970 with value:
true
at
org.apache.camel.main.BaseMainSupport.setPropertiesOnTarget(BaseMainSupport.java:176)
at
org.apache.camel.main.BaseMainSupport.autoConfigurationFromProperties(BaseMainSupport.java:993)
at
org.apache.camel.main.BaseMainSupport.autoconfigure(BaseMainSupport.java:545)
at
org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:587)
at
org.apache.camel.main.BaseMainSupport.initCamelContext(BaseMainSupport.java:423)
at org.apache.camel.main.Main.doInit(Main.java:109)
at
org.apache.camel.support.service.ServiceSupport.init(ServiceSupport.java:83)
at
org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:112)
at org.apache.camel.main.MainSupport.run(MainSupport.java:82)
at
org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:85)
... 2 more
{code}
It always throw error on any first servlet property in configuration but all
servlet properties binds correctly and works.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14739) RouteContext missing for RedeliveryErrorHandler
[ https://issues.apache.org/jira/browse/CAMEL-14739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-14739: - Priority: Major (was: Critical) > RouteContext missing for RedeliveryErrorHandler > --- > > Key: CAMEL-14739 > URL: https://issues.apache.org/jira/browse/CAMEL-14739 > Project: Camel > Issue Type: Bug > Components: came-core >Affects Versions: 3.1.0 >Reporter: Nathan >Priority: Major > > The RedeliveryErrorHandler needs the RouteContext to determine which > onException rule to use. > The RouteContext is set at the start of a route, when leaving a route the > RouteContext should be set to the route that called it. However it is > apparently null, which means that if an error happens at that point it cannot > use the onException rules that have been set. > In 3.0 the RouteContext was a stack so it kept track of all the routes that > it passed, meaning automatically returned to the parent RouteContext value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14739) RouteContext missing for RedeliveryErrorHandler
Nathan created CAMEL-14739: -- Summary: RouteContext missing for RedeliveryErrorHandler Key: CAMEL-14739 URL: https://issues.apache.org/jira/browse/CAMEL-14739 Project: Camel Issue Type: Bug Components: came-core Affects Versions: 3.1.0 Reporter: Nathan The RedeliveryErrorHandler needs the RouteContext to determine which onException rule to use. The RouteContext is set at the start of a route, when leaving a route the RouteContext should be set to the route that called it. However it is apparently null, which means that if an error happens at that point it cannot use the onException rules that have been set. In 3.0 the RouteContext was a stack so it kept track of all the routes that it passed, meaning automatically returned to the parent RouteContext value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-14738) Create a camel-platform-http-vertx component
[ https://issues.apache.org/jira/browse/CAMEL-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-14738 started by Luca Burgazzoli. --- > Create a camel-platform-http-vertx component > > > Key: CAMEL-14738 > URL: https://issues.apache.org/jira/browse/CAMEL-14738 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 3.2.0 > > > camel-quarkus has an implmentation of the camel-platform-http engine based on > vert.x that has no dependencies on quarkus itself so as a similar > implementation would be useful also for camel-k we should create a > camel-platform-http-vertx subprojects can use -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14738) Create a camel-platform-http-vertx component
Luca Burgazzoli created CAMEL-14738: --- Summary: Create a camel-platform-http-vertx component Key: CAMEL-14738 URL: https://issues.apache.org/jira/browse/CAMEL-14738 Project: Camel Issue Type: New Feature Reporter: Luca Burgazzoli Assignee: Luca Burgazzoli Fix For: 3.2.0 camel-quarkus has an implmentation of the camel-platform-http engine based on vert.x that has no dependencies on quarkus itself so as a similar implementation would be useful also for camel-k we should create a camel-platform-http-vertx subprojects can use -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14737) Spring-boot closes datasource before the last inflight messages are processed
Nicolas Gillet created CAMEL-14737: -- Summary: Spring-boot closes datasource before the last inflight messages are processed Key: CAMEL-14737 URL: https://issues.apache.org/jira/browse/CAMEL-14737 Project: Camel Issue Type: Bug Components: camel-spring-boot, camel-sql Affects Versions: 3.1.0, 3.0.1 Environment: Windows 10 x64 adopt open jdk 11 spring-boot 2.2.5-RELEASE postgresql 12 Reporter: Nicolas Gillet As reported on Stack Overflow ([https://stackoverflow.com/questions/60654265/springboot-camel-datasource-already-closed-on-graceful-shutdown]) I created a simple spring-boot application that fetches logs (camel-ftp) extract some data line by line and insert them in a database (camel-sql). When I stop the application (gracefully) spring shortly closes the datasource but there is still an inflight exchange and I get "datasource already closed" errors. I was looking for a way to tell spring to not close the datasource until all inflight exchanges are processed (or timed out ?) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (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=17062356#comment-17062356 ] Aashna Jena edited comment on CAMEL-13780 at 3/19/20, 8:03 AM: --- Yes [~Aemie], I have already started working on this issue. Can you please take up another one, so that we don't have any conflicting PRs? Thanks! I've been asked to wait for some structural changes to be merged before I start working on this issue :) was (Author: aashnajena): Yes [~Aemie], I have already started working on this issue. Can you please take up another one, so that we don't have any conflicting PRs? Thanks! > 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 > Labels: help-wanted > Fix For: 3.2.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.4#803005)
[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=17062356#comment-17062356 ] Aashna Jena commented on CAMEL-13780: - Yes [~Aemie], I have already started working on this issue. Can you please take up another one, so that we don't have any conflicting PRs? Thanks! > 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 > Labels: help-wanted > Fix For: 3.2.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.4#803005)
[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=17062353#comment-17062353 ] Aemie commented on CAMEL-13780: --- This problem persist for both user manual and component reference docs? > 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 > Labels: help-wanted > Fix For: 3.2.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.4#803005)
[jira] [Assigned] (CAMEL-14679) Support DROP_ROOT_MODE in XStream JSON dataformat
[
https://issues.apache.org/jira/browse/CAMEL-14679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-14679:
---
Assignee: Claus Ibsen
> Support DROP_ROOT_MODE in XStream JSON dataformat
> --
>
> Key: CAMEL-14679
> URL: https://issues.apache.org/jira/browse/CAMEL-14679
> Project: Camel
> Issue Type: Improvement
> Components: camel-xstream
>Reporter: Peter Palaga
>Assignee: Claus Ibsen
>Priority: Major
>
> It is currently not possible to configure
> {{org.apache.camel.dataformat.xstream.JsonDataFormat}} to produce standard
> JSON without the XStream specific root node.
> XStream JSON with root node:
> {code:json}
> {"org.apache.camel.quarkus.component.xstream.it.PojoA\:{"name":"Joe"}}{code}
> Standard JSON:
> {code:json}
> {"name":"Joe"}{code}
> With plain Xstream this can be reached via (see
> https://x-stream.github.io/json-tutorial.html#json-dropping-root )
> {code:java}
> XStream xstream = new XStream(new JsonHierarchicalStreamDriver() {
> public HierarchicalStreamWriter createWriter(Writer writer) {
> return new JsonWriter(writer, JsonWriter.DROP_ROOT_MODE);
> }
> });
> {code}
> But I have not found a way to configure the
> {{org.apache.camel.dataformat.xstream.JsonDataFormat}} in that way. So we
> probably need some change to allow this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14679) Support DROP_ROOT_MODE in XStream JSON dataformat
[
https://issues.apache.org/jira/browse/CAMEL-14679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-14679:
Fix Version/s: 3.2.0
> Support DROP_ROOT_MODE in XStream JSON dataformat
> --
>
> Key: CAMEL-14679
> URL: https://issues.apache.org/jira/browse/CAMEL-14679
> Project: Camel
> Issue Type: Improvement
> Components: camel-xstream
>Reporter: Peter Palaga
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.2.0
>
>
> It is currently not possible to configure
> {{org.apache.camel.dataformat.xstream.JsonDataFormat}} to produce standard
> JSON without the XStream specific root node.
> XStream JSON with root node:
> {code:json}
> {"org.apache.camel.quarkus.component.xstream.it.PojoA\:{"name":"Joe"}}{code}
> Standard JSON:
> {code:json}
> {"name":"Joe"}{code}
> With plain Xstream this can be reached via (see
> https://x-stream.github.io/json-tutorial.html#json-dropping-root )
> {code:java}
> XStream xstream = new XStream(new JsonHierarchicalStreamDriver() {
> public HierarchicalStreamWriter createWriter(Writer writer) {
> return new JsonWriter(writer, JsonWriter.DROP_ROOT_MODE);
> }
> });
> {code}
> But I have not found a way to configure the
> {{org.apache.camel.dataformat.xstream.JsonDataFormat}} in that way. So we
> probably need some change to allow this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14711) Disable RabbitMQ Java serialization by default
[ https://issues.apache.org/jira/browse/CAMEL-14711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14711. - Resolution: Fixed > Disable RabbitMQ Java serialization by default > -- > > Key: CAMEL-14711 > URL: https://issues.apache.org/jira/browse/CAMEL-14711 > Project: Camel > Issue Type: Improvement > Components: camel-rabbitmq >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1, 3.2.0, 3.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to disable the Rabbit MQ Java serialization functionality by > default due to security reasons. It can be re-enabled using an > "allowMessageBodySerialization" parameter. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13800) Mobile usability issues reported in Google search console
[ https://issues.apache.org/jira/browse/CAMEL-13800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062327#comment-17062327 ] JyotiAttri commented on CAMEL-13800: Hi [~zregvart] , *Issue: Viewport not set (3 pages)* In this issue, there are three pages which don't include viewport command. I didn't find where are these pages. I want to add Viewport into it. Please help me. > Mobile usability issues reported in Google search console > - > > Key: CAMEL-13800 > URL: https://issues.apache.org/jira/browse/CAMEL-13800 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot_2019-07-29 Mobile Usability.png, > cxf_component_mobile_screenshot.png > > > Google search console reports issues in mobile usability: > * Clickable elements too close together > * Text too small to read > * Content wider than screen -- This message was sent by Atlassian Jira (v8.3.4#803005)
