[jira] [Resolved] (CAMEL-13471) Support TCP + TLS in Camel CoAP
[ https://issues.apache.org/jira/browse/CAMEL-13471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13471. - Resolution: Fixed Fix Version/s: (was: 3.x) > Support TCP + TLS in Camel CoAP > --- > > Key: CAMEL-13471 > URL: https://issues.apache.org/jira/browse/CAMEL-13471 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > > This task is to support TCP + TLS in Camel CoAP as per > https://tools.ietf.org/html/rfc8323 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13471) Support TCP + TLS in Camel CoAP
[ https://issues.apache.org/jira/browse/CAMEL-13471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-13471: Fix Version/s: 3.0.0-M3 3.x > Support TCP + TLS in Camel CoAP > --- > > Key: CAMEL-13471 > URL: https://issues.apache.org/jira/browse/CAMEL-13471 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 3.x, 3.0.0-M3 > > > This task is to support TCP + TLS in Camel CoAP as per > https://tools.ietf.org/html/rfc8323 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13489) camel-undertow: consumer thrown NPE when the body cannot be converted to ByteBuffer
[
https://issues.apache.org/jira/browse/CAMEL-13489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-13489:
-
Fix Version/s: 2.24.0
> camel-undertow: consumer thrown NPE when the body cannot be converted to
> ByteBuffer
> ---
>
> Key: CAMEL-13489
> URL: https://issues.apache.org/jira/browse/CAMEL-13489
> Project: Camel
> Issue Type: Bug
> Components: camel-undertow
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, 2.24.0
>
>
> Assuming we have a simple route like:
> {code}
> from("undertow:http://localhost:{{port}}/incompatibleData;)
> .transform().constant(Collections.singletonMap("key", "val"));
> {code}
> This code will cause an NPE on UndertowConsumer because the body cannot be
> converted to a ByteBuffer [1], instead of an NPE we should use
> mandatoryConvertTo so the exception is more clear.
> [1]
> https://github.com/apache/camel/blob/master/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/UndertowConsumer.java#L156
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13489) camel-undertow: consumer thrown NPE when the body cannot be converted to ByteBuffer
[
https://issues.apache.org/jira/browse/CAMEL-13489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13489.
--
Resolution: Fixed
> camel-undertow: consumer thrown NPE when the body cannot be converted to
> ByteBuffer
> ---
>
> Key: CAMEL-13489
> URL: https://issues.apache.org/jira/browse/CAMEL-13489
> Project: Camel
> Issue Type: Bug
> Components: camel-undertow
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, 2.24.0
>
>
> Assuming we have a simple route like:
> {code}
> from("undertow:http://localhost:{{port}}/incompatibleData;)
> .transform().constant(Collections.singletonMap("key", "val"));
> {code}
> This code will cause an NPE on UndertowConsumer because the body cannot be
> converted to a ByteBuffer [1], instead of an NPE we should use
> mandatoryConvertTo so the exception is more clear.
> [1]
> https://github.com/apache/camel/blob/master/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/UndertowConsumer.java#L156
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13489) camel-undertow: consumer thrown NPE when the body cannot be converted to ByteBuffer
[
https://issues.apache.org/jira/browse/CAMEL-13489?focusedWorklogId=238434=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-238434
]
ASF GitHub Bot logged work on CAMEL-13489:
--
Author: ASF GitHub Bot
Created on: 07/May/19 12:58
Start Date: 07/May/19 12:58
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #2906: CAMEL-13489:
camel-undertow: consumer thrown NPE when the body cannot be converted to
ByteBuffer
URL: https://github.com/apache/camel/pull/2906
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: 238434)
Time Spent: 10m
Remaining Estimate: 0h
> camel-undertow: consumer thrown NPE when the body cannot be converted to
> ByteBuffer
> ---
>
> Key: CAMEL-13489
> URL: https://issues.apache.org/jira/browse/CAMEL-13489
> Project: Camel
> Issue Type: Bug
> Components: camel-undertow
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, 2.24.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Assuming we have a simple route like:
> {code}
> from("undertow:http://localhost:{{port}}/incompatibleData;)
> .transform().constant(Collections.singletonMap("key", "val"));
> {code}
> This code will cause an NPE on UndertowConsumer because the body cannot be
> converted to a ByteBuffer [1], instead of an NPE we should use
> mandatoryConvertTo so the exception is more clear.
> [1]
> https://github.com/apache/camel/blob/master/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/UndertowConsumer.java#L156
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13490) Consider API key in query parameters when configuring REST producers
[
https://issues.apache.org/jira/browse/CAMEL-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-13490.
---
Resolution: Fixed
> Consider API key in query parameters when configuring REST producers
>
>
> Key: CAMEL-13490
> URL: https://issues.apache.org/jira/browse/CAMEL-13490
> Project: Camel
> Issue Type: New Feature
> Components: camel-rest-swagger
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0-M3
>
>
> Using API keys in query parameters as the calling code is quite a bit removed
> from the component performing the HTTP call, making it difficult to introduce
> additional query parameters not referenced in the request definition.
> When API key in query parameters is defined in the OpenAPI specification's
> {{securityDefinition}} then {{RestProducerFactory::createProducer}}
> invocation needs to include those parameters the {{queryParameters}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13491) CamelTestSupport.isCreateCamelContextPerClass no longer works for junit4 tests
Jan Hallonsten created CAMEL-13491:
--
Summary: CamelTestSupport.isCreateCamelContextPerClass no longer
works for junit4 tests
Key: CAMEL-13491
URL: https://issues.apache.org/jira/browse/CAMEL-13491
Project: Camel
Issue Type: Bug
Components: camel-test
Affects Versions: 2.23.0
Reporter: Jan Hallonsten
With the changes in
org.apache.camel.test.junit4.CamelTestSupport done during the work on
https://issues.apache.org/jira/browse/CAMEL-12534 the camel context is now
recreated for every test regardless of the return value from
isCreateCamelContextPerClass()
. Since junit4 creates a new instance of the class for every test the variable
tests will be recreated and initialized to 0 for every test.
This condition in tearDown will always be true
{code:java}
// code placeholder
if (tests.compareAndSet(v, v - 1)) {
if (v == 1) {
{code}
which stops the camel context after every test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13192) Path resolution in rest-swagger fails to include the whole path
[
https://issues.apache.org/jira/browse/CAMEL-13192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-13192:
--
Fix Version/s: (was: 2.24.0)
> Path resolution in rest-swagger fails to include the whole path
> ---
>
> Key: CAMEL-13192
> URL: https://issues.apache.org/jira/browse/CAMEL-13192
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.21.0, 2.21.1, 2.21.2, 2.21.3, 2.21.4, 2.22.0, 2.22.1,
> 2.22.2, 2.22.3, 2.23.0, 2.23.1
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0
>
>
> When trying to resolve paths from a given OpenAPI 2.0 document the trailing
> part of the path after the last path parameter placeholder is lost.
> For example path with:
> {code:java}
> /path/{param}/will/be/lost{code}
> Is resolved as:
> {code:java}
> /path/{param}{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13192) Path resolution in rest-swagger fails to include the whole path
[
https://issues.apache.org/jira/browse/CAMEL-13192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-13192:
--
Fix Version/s: (was: 2.22.4)
(was: 2.23.2)
2.24.0
> Path resolution in rest-swagger fails to include the whole path
> ---
>
> Key: CAMEL-13192
> URL: https://issues.apache.org/jira/browse/CAMEL-13192
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.21.0, 2.21.1, 2.21.2, 2.21.3, 2.21.4, 2.22.0, 2.22.1,
> 2.22.2, 2.22.3, 2.23.0, 2.23.1
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0, 2.24.0
>
>
> When trying to resolve paths from a given OpenAPI 2.0 document the trailing
> part of the path after the last path parameter placeholder is lost.
> For example path with:
> {code:java}
> /path/{param}/will/be/lost{code}
> Is resolved as:
> {code:java}
> /path/{param}{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work started] (CAMEL-13490) Consider API key in query parameters when configuring REST producers
[
https://issues.apache.org/jira/browse/CAMEL-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-13490 started by Zoran Regvart.
-
> Consider API key in query parameters when configuring REST producers
>
>
> Key: CAMEL-13490
> URL: https://issues.apache.org/jira/browse/CAMEL-13490
> Project: Camel
> Issue Type: New Feature
> Components: camel-rest-swagger
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0-M3
>
>
> Using API keys in query parameters as the calling code is quite a bit removed
> from the component performing the HTTP call, making it difficult to introduce
> additional query parameters not referenced in the request definition.
> When API key in query parameters is defined in the OpenAPI specification's
> {{securityDefinition}} then {{RestProducerFactory::createProducer}}
> invocation needs to include those parameters the {{queryParameters}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13490) Consider API key in query parameters when configuring REST producers
Zoran Regvart created CAMEL-13490:
-
Summary: Consider API key in query parameters when configuring
REST producers
Key: CAMEL-13490
URL: https://issues.apache.org/jira/browse/CAMEL-13490
Project: Camel
Issue Type: New Feature
Components: camel-rest-swagger
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Fix For: 3.0.0-M3
Using API keys in query parameters as the calling code is quite a bit removed
from the component performing the HTTP call, making it difficult to introduce
additional query parameters not referenced in the request definition.
When API key in query parameters is defined in the OpenAPI specification's
{{securityDefinition}} then {{RestProducerFactory::createProducer}} invocation
needs to include those parameters the {{queryParameters}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13470) Publish security advisories
[
https://issues.apache.org/jira/browse/CAMEL-13470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-13470.
---
Resolution: Fixed
We now have a Hugo archetype for security advisories and the existing security
advisories have been migrated to the (currently) staging website.
> Publish security advisories
> ---
>
> Key: CAMEL-13470
> URL: https://issues.apache.org/jira/browse/CAMEL-13470
> Project: Camel
> Issue Type: Sub-task
> Components: website
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We have a number of [security
> advisories|https://github.com/apache/camel/tree/master/docs/user-manual/en/security-advisories]
> that we need to publish and are not currently publishing on the new website.
> We should create a Hugo archetype and copy over the current advisories to the
> {{camel-website}} git repository.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13470) Publish security advisories
[
https://issues.apache.org/jira/browse/CAMEL-13470?focusedWorklogId=238351=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-238351
]
ASF GitHub Bot logged work on CAMEL-13470:
--
Author: ASF GitHub Bot
Created on: 07/May/19 10:04
Start Date: 07/May/19 10:04
Worklog Time Spent: 10m
Work Description: zregvart commented on pull request #34: CAMEL-13470:
Publish security advisories
URL: https://github.com/apache/camel-website/pull/34
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: 238351)
Time Spent: 20m (was: 10m)
> Publish security advisories
> ---
>
> Key: CAMEL-13470
> URL: https://issues.apache.org/jira/browse/CAMEL-13470
> Project: Camel
> Issue Type: Sub-task
> Components: website
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We have a number of [security
> advisories|https://github.com/apache/camel/tree/master/docs/user-manual/en/security-advisories]
> that we need to publish and are not currently publishing on the new website.
> We should create a Hugo archetype and copy over the current advisories to the
> {{camel-website}} git repository.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13481) Upgrade to shiro 1.4.1
[ https://issues.apache.org/jira/browse/CAMEL-13481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13481. -- Resolution: Fixed > Upgrade to shiro 1.4.1 > -- > > Key: CAMEL-13481 > URL: https://issues.apache.org/jira/browse/CAMEL-13481 > Project: Camel > Issue Type: Improvement > Components: camel-shiro >Reporter: Francois Papon >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.0.0, 2.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13481) Upgrade to shiro 1.4.1
[ https://issues.apache.org/jira/browse/CAMEL-13481?focusedWorklogId=238282=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-238282 ] ASF GitHub Bot logged work on CAMEL-13481: -- Author: ASF GitHub Bot Created on: 07/May/19 06:51 Start Date: 07/May/19 06:51 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #2902: [CAMEL-13481] Upgrade to shiro 1.4.1 URL: https://github.com/apache/camel/pull/2902 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: 238282) Time Spent: 20m (was: 10m) > Upgrade to shiro 1.4.1 > -- > > Key: CAMEL-13481 > URL: https://issues.apache.org/jira/browse/CAMEL-13481 > Project: Camel > Issue Type: Improvement > Components: camel-shiro >Reporter: Francois Papon >Priority: Minor > Fix For: 3.0.0, 2.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13481) Upgrade to shiro 1.4.1
[ https://issues.apache.org/jira/browse/CAMEL-13481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13481: Assignee: Andrea Cosentino > Upgrade to shiro 1.4.1 > -- > > Key: CAMEL-13481 > URL: https://issues.apache.org/jira/browse/CAMEL-13481 > Project: Camel > Issue Type: Improvement > Components: camel-shiro >Reporter: Francois Papon >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.0.0, 2.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
