[jira] [Updated] (CAMEL-11709) Camel-Milo component cannot write to newer server versions

[Dennis Pries (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Pries updated CAMEL-11709:
-
Description: Newer OPC UA Server implementations (for example: 
opcuaserver.com:48010) forbit setting sourceTime and serverTime in DataValue.  
(was: Newer OPC Server implementations forbit setting sourceTime and serverTime 
in DataValue.)

> Camel-Milo component cannot write to newer server versions
> --
>
> Key: CAMEL-11709
> URL: https://issues.apache.org/jira/browse/CAMEL-11709
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.19.2
>Reporter: Dennis Pries
>  Labels: newbie, patch
> Attachments: camel-milo.patch
>
>
> Newer OPC UA Server implementations (for example: opcuaserver.com:48010) 
> forbit setting sourceTime and serverTime in DataValue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11699) HealthCheck : grab service status from external service status repository

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-11699 started by Luca Burgazzoli.
---
> HealthCheck : grab service status from external service status repository
> -
>
> Key: CAMEL-11699
> URL: https://issues.apache.org/jira/browse/CAMEL-11699
> Project: Camel
>  Issue Type: New Feature
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>  Labels: health-check
> Fix For: 2.20.0
>
>
> There should be possible to retrieve service status from external source so 
> i.e. the twitter status is checked externally from camel and made available 
> to camel whiteout having every camel instance to check for twitter status.
> i.e. 
> # we can have a ConsulHealthCheckRegistry that grab service status from 
> consul exposing them to camel as standard HealthCheck so the check call will 
> ends up in simply grabbing the status from consul
> # we can have an AggregatingHealthCheckRegistry that aggregates multiple 
> registri in a single view.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11709) Camel-Milo component cannot write to newer server versions

[Dennis Pries (JIRA)]

Dennis Pries created CAMEL-11709:


 Summary: Camel-Milo component cannot write to newer server versions
 Key: CAMEL-11709
 URL: https://issues.apache.org/jira/browse/CAMEL-11709
 Project: Camel
  Issue Type: Bug
  Components: camel-milo
Affects Versions: 2.19.2
Reporter: Dennis Pries
 Attachments: camel-milo.patch

Newer OPC Server implementations forbit setting sourceTime and serverTime in 
DataValue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11709) Camel-Milo component cannot write to newer server versions

[Dennis Pries (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Pries updated CAMEL-11709:
-
Flags: Patch

> Camel-Milo component cannot write to newer server versions
> --
>
> Key: CAMEL-11709
> URL: https://issues.apache.org/jira/browse/CAMEL-11709
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.19.2
>Reporter: Dennis Pries
>  Labels: newbie, patch
> Attachments: camel-milo.patch
>
>
> Newer OPC Server implementations forbit setting sourceTime and serverTime in 
> DataValue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11709) Camel-Milo component cannot write to newer server versions

[Dennis Pries (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Pries updated CAMEL-11709:
-
Attachment: camel-milo.patch

> Camel-Milo component cannot write to newer server versions
> --
>
> Key: CAMEL-11709
> URL: https://issues.apache.org/jira/browse/CAMEL-11709
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.19.2
>Reporter: Dennis Pries
>  Labels: newbie, patch
> Attachments: camel-milo.patch
>
>
> Newer OPC Server implementations forbit setting sourceTime and serverTime in 
> DataValue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11707) spring boot code generation: there should be a way to exclude some properties from the code generation

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-11707:

Description: 
As today every property is exposed to spring boot auto configuration processor 
but sometimes you may want to hide some or them as they may be supposed to be 
used only internally or because you want to write your own code to manage 
complex configurations.

As this may also be needed to hide info from the catalog, we may have something 
like:

{code}
@Metadata(key = "ignore", value = "true", labels = "spring-boot,catalog")
{code}



  was:
As today every property is exposed to spring boot auto configuration processor 
but sometimes you may want to hide some or them as they may be supposed to be 
used only internally or because you want to write your own code to manage 
complex configurations.

As this may also be needed to hide info from the catalog, we may have something 
like:

{code}
@Metadata(key = "ignore", value = "true", labels="spring-boot,catalog")
{code}




> spring boot code generation: there should be a way to exclude some properties 
> from the code generation
> --
>
> Key: CAMEL-11707
> URL: https://issues.apache.org/jira/browse/CAMEL-11707
> Project: Camel
>  Issue Type: Improvement
>  Components: tooling
>Reporter: Luca Burgazzoli
> Fix For: 2.20.0
>
>
> As today every property is exposed to spring boot auto configuration 
> processor but sometimes you may want to hide some or them as they may be 
> supposed to be used only internally or because you want to write your own 
> code to manage complex configurations.
> As this may also be needed to hide info from the catalog, we may have 
> something like:
> {code}
> @Metadata(key = "ignore", value = "true", labels = "spring-boot,catalog")
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11707) spring boot code generation: there should be a way to exclude some properties from the code generation

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-11707:

Description: 
As today every property is exposed to spring boot auto configuration processor 
but sometimes you may want to hide some or them as they may be supposed to be 
used only internally or because you want to write your own code to manage 
complex configurations.

As this may also be needed to hide info from the catalog, we may have something 
like:

{code}
@Metadata(key = "ignore", value = "true", labels = "spring-boot,catalog")
{code}

Or have specific annotations.



  was:
As today every property is exposed to spring boot auto configuration processor 
but sometimes you may want to hide some or them as they may be supposed to be 
used only internally or because you want to write your own code to manage 
complex configurations.

As this may also be needed to hide info from the catalog, we may have something 
like:

{code}
@Metadata(key = "ignore", value = "true", labels = "spring-boot,catalog")
{code}




> spring boot code generation: there should be a way to exclude some properties 
> from the code generation
> --
>
> Key: CAMEL-11707
> URL: https://issues.apache.org/jira/browse/CAMEL-11707
> Project: Camel
>  Issue Type: Improvement
>  Components: tooling
>Reporter: Luca Burgazzoli
> Fix For: 2.20.0
>
>
> As today every property is exposed to spring boot auto configuration 
> processor but sometimes you may want to hide some or them as they may be 
> supposed to be used only internally or because you want to write your own 
> code to manage complex configurations.
> As this may also be needed to hide info from the catalog, we may have 
> something like:
> {code}
> @Metadata(key = "ignore", value = "true", labels = "spring-boot,catalog")
> {code}
> Or have specific annotations.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11707) spring boot code generation: there should be a way to exclude some properties from the code generation

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-11707:

Description: 
As today every property is exposed to spring boot auto configuration processor 
but sometimes you may want to hide some or them as they may be supposed to be 
used only internally or because you want to write your own code to manage 
complex configurations.

As this may also be needed to hide info from the catalog, we may have something 
like:

{code}
@Metadata(key = "ignore", value = "true", labels="spring-boot,catalog")
{code}



  was:
As today every property is exposed to spring boot auto configuration processor 
but sometimes you may want to hide some or them as they may be supposed to be 
used only internally or because you want to write your own code to manage 
complex configurations.

As this may also be needed to hide info from the catalog, we may have something 
like:

{code}
@Metadata(key = "ignore", value = "true", context="spring-boot")
{code}




> spring boot code generation: there should be a way to exclude some properties 
> from the code generation
> --
>
> Key: CAMEL-11707
> URL: https://issues.apache.org/jira/browse/CAMEL-11707
> Project: Camel
>  Issue Type: Improvement
>  Components: tooling
>Reporter: Luca Burgazzoli
> Fix For: 2.20.0
>
>
> As today every property is exposed to spring boot auto configuration 
> processor but sometimes you may want to hide some or them as they may be 
> supposed to be used only internally or because you want to write your own 
> code to manage complex configurations.
> As this may also be needed to hide info from the catalog, we may have 
> something like:
> {code}
> @Metadata(key = "ignore", value = "true", labels="spring-boot,catalog")
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11708) spring boot code generation: the nested property processor does not handle object hierarchies

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11708:
---

 Summary: spring boot code generation: the nested property 
processor does not handle object hierarchies
 Key: CAMEL-11708
 URL: https://issues.apache.org/jira/browse/CAMEL-11708
 Project: Camel
  Issue Type: Bug
  Components: tooling
Reporter: Luca Burgazzoli
 Fix For: 2.20.0


Assuming you have complex configuration object that inherits from another 
configuration object, the spring boot code generation will creates the 
configuration properties object only for the properties of the last class so 
i.e. for a simple hierarchy like:

{code}
Common {
String getX()
void setX(String);
}

Specific extends Common {
String getY()
void setY(String);
}
{code}

the generator will provides bindings only for

{code}
String getX()
setX(String)
{code}






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11707) spring boot code generation: there should be a way to exclude some properties from the code generation

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11707:
---

 Summary: spring boot code generation: there should be a way to 
exclude some properties from the code generation
 Key: CAMEL-11707
 URL: https://issues.apache.org/jira/browse/CAMEL-11707
 Project: Camel
  Issue Type: Improvement
  Components: tooling
Reporter: Luca Burgazzoli
 Fix For: 2.20.0


As today every property is exposed to spring boot auto configuration processor 
but sometimes you may want to hide some or them as they may be supposed to be 
used only internally or because you want to write your own code to manage 
complex configurations.

As this may also be needed to hide info from the catalog, we may have something 
like:

{code}
@Metadata(key = "ignore", value = "true", context="spring-boot")
{code}





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11704) Camel-RabbitMQ: Allow passive queue declaration

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141527#comment-16141527
 ] 

ASF GitHub Bot commented on CAMEL-11704:


Github user cschachinger closed the pull request at:

https://github.com/apache/camel/pull/1900


> Camel-RabbitMQ: Allow passive queue declaration
> ---
>
> Key: CAMEL-11704
> URL: https://issues.apache.org/jira/browse/CAMEL-11704
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-rabbitmq
>Reporter: C S
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> Could you introduce passive queues; I.e. create the endpoint parameter 
> "passive", and if that's set the queue is declared with 
> channel.queueDeclarePassive("queue_name")
> All other parameters like durable, exclusive, autodelete, queueArges can be 
> ignored in this case - since the assumption is that the queue is already 
> available on the server.
> Some RabbitMQ instances do not allow "active" declaration and therefore the 
> camel-component cannot be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11704) Camel-RabbitMQ: Allow passive queue declaration

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-11704.
--
   Resolution: Fixed
Fix Version/s: 2.20.0

> Camel-RabbitMQ: Allow passive queue declaration
> ---
>
> Key: CAMEL-11704
> URL: https://issues.apache.org/jira/browse/CAMEL-11704
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-rabbitmq
>Reporter: C S
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> Could you introduce passive queues; I.e. create the endpoint parameter 
> "passive", and if that's set the queue is declared with 
> channel.queueDeclarePassive("queue_name")
> All other parameters like durable, exclusive, autodelete, queueArges can be 
> ignored in this case - since the assumption is that the queue is already 
> available on the server.
> Some RabbitMQ instances do not allow "active" declaration and therefore the 
> camel-component cannot be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11704) Camel-RabbitMQ: Allow passive queue declaration

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino reassigned CAMEL-11704:


Assignee: Andrea Cosentino

> Camel-RabbitMQ: Allow passive queue declaration
> ---
>
> Key: CAMEL-11704
> URL: https://issues.apache.org/jira/browse/CAMEL-11704
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-rabbitmq
>Reporter: C S
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> Could you introduce passive queues; I.e. create the endpoint parameter 
> "passive", and if that's set the queue is declared with 
> channel.queueDeclarePassive("queue_name")
> All other parameters like durable, exclusive, autodelete, queueArges can be 
> ignored in this case - since the assumption is that the queue is already 
> available on the server.
> Some RabbitMQ instances do not allow "active" declaration and therefore the 
> camel-component cannot be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11706) Remove duplicate type converter methods from HBaseModelConverter

[James Netherton (JIRA)]

James Netherton created CAMEL-11706:
---

 Summary: Remove duplicate type converter methods from 
HBaseModelConverter
 Key: CAMEL-11706
 URL: https://issues.apache.org/jira/browse/CAMEL-11706
 Project: Camel
  Issue Type: Improvement
  Components: camel-hbase
Reporter: James Netherton
Priority: Minor


When the camel-hbase component is used the following log messages are observed:

{code}
11:16:32,852 WARN  [org.apache.camel.impl.converter.DefaultTypeConverter] 
(pool-3-thread-1) Overriding type converter from: StaticMethodTypeConverter: 
public static byte[] 
org.apache.camel.converter.IOConverter.toByteArray(java.lang.String,org.apache.camel.Exchange)
 throws java.io.IOException to: StaticMethodTypeConverter: public static byte[] 
org.apache.camel.component.hbase.converter.HBaseModelConverter.stringToBytes(java.lang.String)
11:16:32,852 WARN  [org.apache.camel.impl.converter.DefaultTypeConverter] 
(pool-3-thread-1) Overriding type converter from: StaticMethodTypeConverter: 
public static java.lang.String 
org.apache.camel.converter.IOConverter.toString(byte[],org.apache.camel.Exchange)
 throws java.io.IOException to: StaticMethodTypeConverter: public static 
java.lang.String 
org.apache.camel.component.hbase.converter.HBaseModelConverter.bytesToString(byte[])
{code}

I know these can effectively be ignored, but it is a little annoying. Can we 
clean up the duplicate @Converter methods?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11704) Camel-RabbitMQ: Allow passive queue declaration

[C S (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141392#comment-16141392
 ] 

C S commented on CAMEL-11704:
-

PR #1900 has been created

> Camel-RabbitMQ: Allow passive queue declaration
> ---
>
> Key: CAMEL-11704
> URL: https://issues.apache.org/jira/browse/CAMEL-11704
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-rabbitmq
>Reporter: C S
>
> Could you introduce passive queues; I.e. create the endpoint parameter 
> "passive", and if that's set the queue is declared with 
> channel.queueDeclarePassive("queue_name")
> All other parameters like durable, exclusive, autodelete, queueArges can be 
> ignored in this case - since the assumption is that the queue is already 
> available on the server.
> Some RabbitMQ instances do not allow "active" declaration and therefore the 
> camel-component cannot be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11704) Camel-RabbitMQ: Allow passive queue declaration

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141389#comment-16141389
 ] 

ASF GitHub Bot commented on CAMEL-11704:


GitHub user cschachinger opened a pull request:

https://github.com/apache/camel/pull/1900

CAMEL-11704

This PR allows a queue to be declared "passively". 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cschachinger/camel master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1900.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1900


commit cc0c9e9aa1fd9b4ed530257b9bda2125fd8bce25
Author: Christoph Schachinger 
Date:   2017-08-25T08:56:07Z

CAMEL-11704




> Camel-RabbitMQ: Allow passive queue declaration
> ---
>
> Key: CAMEL-11704
> URL: https://issues.apache.org/jira/browse/CAMEL-11704
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-rabbitmq
>Reporter: C S
>
> Could you introduce passive queues; I.e. create the endpoint parameter 
> "passive", and if that's set the queue is declared with 
> channel.queueDeclarePassive("queue_name")
> All other parameters like durable, exclusive, autodelete, queueArges can be 
> ignored in this case - since the assumption is that the queue is already 
> available on the server.
> Some RabbitMQ instances do not allow "active" declaration and therefore the 
> camel-component cannot be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11705) Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-11705.
--
Resolution: Fixed

> Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite
> ---
>
> Key: CAMEL-11705
> URL: https://issues.apache.org/jira/browse/CAMEL-11705
> Project: Camel
>  Issue Type: Bug
>  Components: camel-caffeine
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> In both CaffeineCache and CaffeineLoadCache we have
> {code}
> builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
> TimeUnit.SECONDS);
> builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
> TimeUnit.SECONDS);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11705) Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-11705:
-
Fix Version/s: 2.20.0

> Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite
> ---
>
> Key: CAMEL-11705
> URL: https://issues.apache.org/jira/browse/CAMEL-11705
> Project: Camel
>  Issue Type: Bug
>  Components: camel-caffeine
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> In both CaffeineCache and CaffeineLoadCache we have
> {code}
> builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
> TimeUnit.SECONDS);
> builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
> TimeUnit.SECONDS);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11705) Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-11705:
-
Component/s: camel-caffeine

> Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite
> ---
>
> Key: CAMEL-11705
> URL: https://issues.apache.org/jira/browse/CAMEL-11705
> Project: Camel
>  Issue Type: Bug
>  Components: camel-caffeine
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> In both CaffeineCache and CaffeineLoadCache we have
> {code}
> builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
> TimeUnit.SECONDS);
> builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
> TimeUnit.SECONDS);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11705) Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino reassigned CAMEL-11705:


Assignee: Andrea Cosentino

> Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite
> ---
>
> Key: CAMEL-11705
> URL: https://issues.apache.org/jira/browse/CAMEL-11705
> Project: Camel
>  Issue Type: Bug
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>
> In both CaffeineCache and CaffeineLoadCache we have
> {code}
> 
> builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
> TimeUnit.SECONDS);
> 
> builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
> TimeUnit.SECONDS);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11705) Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite

[Andrea Cosentino (JIRA)]

Andrea Cosentino created CAMEL-11705:


 Summary: Camel-Caffeine: ExpireAfterAccess set two times instead 
of ExpireAfterWrite
 Key: CAMEL-11705
 URL: https://issues.apache.org/jira/browse/CAMEL-11705
 Project: Camel
  Issue Type: Bug
Reporter: Andrea Cosentino


In both CaffeineCache and CaffeineLoadCache we have

{code}

builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
TimeUnit.SECONDS);

builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
TimeUnit.SECONDS);
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11705) Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-11705:
-
Description: 
In both CaffeineCache and CaffeineLoadCache we have

{code}
builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
TimeUnit.SECONDS);
builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
TimeUnit.SECONDS);
{code}

  was:
In both CaffeineCache and CaffeineLoadCache we have

{code}

builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
TimeUnit.SECONDS);

builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
TimeUnit.SECONDS);
{code}


> Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite
> ---
>
> Key: CAMEL-11705
> URL: https://issues.apache.org/jira/browse/CAMEL-11705
> Project: Camel
>  Issue Type: Bug
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>
> In both CaffeineCache and CaffeineLoadCache we have
> {code}
> builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
> TimeUnit.SECONDS);
> builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
> TimeUnit.SECONDS);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11704) Camel-RabbitMQ: Allow passive queue declaration

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-11704:
-
Summary: Camel-RabbitMQ: Allow passive queue declaration  (was: Allow 
passive queue declaration)

> Camel-RabbitMQ: Allow passive queue declaration
> ---
>
> Key: CAMEL-11704
> URL: https://issues.apache.org/jira/browse/CAMEL-11704
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-rabbitmq
>Reporter: C S
>
> Could you introduce passive queues; I.e. create the endpoint parameter 
> "passive", and if that's set the queue is declared with 
> channel.queueDeclarePassive("queue_name")
> All other parameters like durable, exclusive, autodelete, queueArges can be 
> ignored in this case - since the assumption is that the queue is already 
> available on the server.
> Some RabbitMQ instances do not allow "active" declaration and therefore the 
> camel-component cannot be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11704) Allow passive queue declaration

[Andrea Cosentino (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141334#comment-16141334
 ] 

Andrea Cosentino commented on CAMEL-11704:
--

You're welcome to work on a PR or a patch for this.
http://camel.apache.org/contributing.html
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

> Allow passive queue declaration
> ---
>
> Key: CAMEL-11704
> URL: https://issues.apache.org/jira/browse/CAMEL-11704
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-rabbitmq
>Reporter: C S
>
> Could you introduce passive queues; I.e. create the endpoint parameter 
> "passive", and if that's set the queue is declared with 
> channel.queueDeclarePassive("queue_name")
> All other parameters like durable, exclusive, autodelete, queueArges can be 
> ignored in this case - since the assumption is that the queue is already 
> available on the server.
> Some RabbitMQ instances do not allow "active" declaration and therefore the 
> camel-component cannot be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11704) Allow passive Queues

[C S (JIRA)]

C S created CAMEL-11704:
---

 Summary: Allow passive Queues
 Key: CAMEL-11704
 URL: https://issues.apache.org/jira/browse/CAMEL-11704
 Project: Camel
  Issue Type: New Feature
  Components: camel-rabbitmq
Reporter: C S


Could you introduce passive queues; I.e. create the endpoint parameter 
"passive", and if that's set the queue is declared with 

channel.queueDeclarePassive("queue_name")

All other parameters like durable, exclusive, autodelete, queueArges can be 
ignored in this case - since the assumption is that the queue is already 
available on the server.

Some RabbitMQ instances do not allow "active" declaration and therefore the 
camel-component cannot be used.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11704) Allow passive queue declaration

[C S (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

C S updated CAMEL-11704:

Summary: Allow passive queue declaration  (was: Allow passive Queues)

> Allow passive queue declaration
> ---
>
> Key: CAMEL-11704
> URL: https://issues.apache.org/jira/browse/CAMEL-11704
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-rabbitmq
>Reporter: C S
>
> Could you introduce passive queues; I.e. create the endpoint parameter 
> "passive", and if that's set the queue is declared with 
> channel.queueDeclarePassive("queue_name")
> All other parameters like durable, exclusive, autodelete, queueArges can be 
> ignored in this case - since the assumption is that the queue is already 
> available on the server.
> Some RabbitMQ instances do not allow "active" declaration and therefore the 
> camel-component cannot be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11703) Camel-AWS: Use builders instead of different constructors

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-11703.
--
Resolution: Fixed

> Camel-AWS: Use builders instead of different constructors
> -
>
> Key: CAMEL-11703
> URL: https://issues.apache.org/jira/browse/CAMEL-11703
> Project: Camel
>  Issue Type: Task
>  Components: camel-aws
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> As we did for S3 we have to align all the other components.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11703) Camel-AWS: Use builders instead of different constructors

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-11703:
-
Issue Type: Task  (was: Bug)

> Camel-AWS: Use builders instead of different constructors
> -
>
> Key: CAMEL-11703
> URL: https://issues.apache.org/jira/browse/CAMEL-11703
> Project: Camel
>  Issue Type: Task
>  Components: camel-aws
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> As we did for S3 we have to align all the other components.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11703) Camel-AWS: Use builders instead of different constructors

[Andrea Cosentino (JIRA)]

Andrea Cosentino created CAMEL-11703:


 Summary: Camel-AWS: Use builders instead of different constructors
 Key: CAMEL-11703
 URL: https://issues.apache.org/jira/browse/CAMEL-11703
 Project: Camel
  Issue Type: Bug
  Components: camel-aws
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
 Fix For: 2.20.0


As we did for S3 we have to align all the other components.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11430) Add support for Spring Boot 2.0.x

[Andrea Cosentino (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141260#comment-16141260
 ] 

Andrea Cosentino commented on CAMEL-11430:
--

We still have to choose if we'll drop support for Spring Boot 1.x and use only 
version 2 or have two different component-starters, v1 and v2.

> Add support for Spring Boot 2.0.x
> -
>
> Key: CAMEL-11430
> URL: https://issues.apache.org/jira/browse/CAMEL-11430
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot
>Reporter: Marcin Grzejszczak
> Fix For: 2.20.0
>
>
> Hello!
> It would be great to add compatibility with Boot 2.0.x . Spring Cloud 
> Contract uses Camel but in the 2.0.x branch (that is compatible with Boot 
> 2.0.x ) we can't actually use it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)