[jira] [Commented] (CAMEL-12927) SQS: Optionally wait for transaction complete to send messages in SqsProducer

2018-12-07 Thread Craig (JIRA)


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

Craig commented on CAMEL-12927:
---

That's code I'm submitting for consideration to solve the issue.

 It is not currently in 
[SqsProducer|https://github.com/apache/camel/blob/camel-2.23.0/components/camel-aws/src/main/java/org/apache/camel/component/aws/sqs/SqsProducer.java].

> SQS: Optionally wait for transaction complete to send messages in SqsProducer
> -
>
> Key: CAMEL-12927
> URL: https://issues.apache.org/jira/browse/CAMEL-12927
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.22.1
>Reporter: Craig
>Priority: Major
>
> Currently, SQS sends messages immediately not waiting for the transaction to 
> commit. Since SQS doesn't support transactional message sending, this 
> behavior is as expected. However, Camel could emulate transaction support for 
> SQS by waiting for the current transaction to commit before sending the 
> message. This would make SQS behave more in line with JMS.
> In SqsConfiguration, add one new property:
>  * transacted
> When transactioned=false (default), behavior is as it is today.
> When transaction=true, don't send the message until the transaction 
> completes. In SqsProducer, wrap the call to
> {code:java}
> SendMessageResult result = getClient().sendMessage(request);{code}
> like so:
> {code:java}
>     
> org.springframework.transaction.support.TransactionSynchronizationManager.registerSynchronization(new
>  org.springframework.transaction.support.TransactionSynchronizationAdapter() {
>             @Override
>             public void afterCommit() {
>                 SendMessageResult result = getClient().sendMessage(request);
>             }
>             
>         });{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-12927) SQS: Optionally wait for transaction complete to send messages in SqsProducer

2018-11-09 Thread Craig (JIRA)
Craig created CAMEL-12927:
-

 Summary: SQS: Optionally wait for transaction complete to send 
messages in SqsProducer
 Key: CAMEL-12927
 URL: https://issues.apache.org/jira/browse/CAMEL-12927
 Project: Camel
  Issue Type: Improvement
  Components: camel-aws
Affects Versions: 2.22.1
Reporter: Craig


Currently, SQS sends messages immediately not waiting for the transaction to 
commit. Since SQS doesn't support transactional message sending, this behavior 
is as expected. However, Camel could emulate transaction support for SQS by 
waiting for the current transaction to commit before sending the message. This 
would make SQS behave more in line with JMS.

In SqsConfiguration, add one new property:
 * transacted

When transactioned=false (default), behavior is as it is today.

When transaction=true, don't send the message until the transaction completes. 
In SqsProducer, wrap the call to

{code:java}
SendMessageResult result = getClient().sendMessage(request);{code}
like so:

{code:java}
    
org.springframework.transaction.support.TransactionSynchronizationManager.registerSynchronization(new
 org.springframework.transaction.support.TransactionSynchronizationAdapter() {

            @Override
            public void afterCommit() {
                SendMessageResult result = getClient().sendMessage(request);
            }
            
        });{code}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-12593) Source and javadoc jars not published to snapshot maven repository

2018-06-22 Thread Craig (JIRA)
Craig created CAMEL-12593:
-

 Summary: Source and javadoc jars not published to snapshot maven 
repository
 Key: CAMEL-12593
 URL: https://issues.apache.org/jira/browse/CAMEL-12593
 Project: Camel
  Issue Type: Bug
  Components: build system
Reporter: Craig


The [https://repository.apache.org/content/repositories/snapshots/] maven 
repository does not have source or javadoc jars for Camel:

[https://repository.apache.org/content/repositories/snapshots/org/apache/camel/camel-core/2.22.0-SNAPSHOT/]

Note that the source and javadoc jars are absent; compare to 
[http://central.maven.org/maven2/org/apache/camel/camel-core/2.21.1/]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-12572) Upgrade to jaxb 2.3.0.1

2018-06-11 Thread Craig (JIRA)
Craig created CAMEL-12572:
-

 Summary: Upgrade to jaxb 2.3.0.1
 Key: CAMEL-12572
 URL: https://issues.apache.org/jira/browse/CAMEL-12572
 Project: Camel
  Issue Type: Improvement
  Components: build system
Reporter: Craig


Camel master (soon to be 2.22) is using jaxb 2.3.0. The latest version of jaxb 
is 2.3.0.1.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12507) SqsProducer support for Number custom data types

2018-05-11 Thread Craig (JIRA)

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

Craig commented on CAMEL-12507:
---

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

> SqsProducer support for Number custom data types
> 
>
> Key: CAMEL-12507
> URL: https://issues.apache.org/jira/browse/CAMEL-12507
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.3, 2.21.0
>Reporter: Craig
>Priority: Major
>
> According to 
> [https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-message-attributes.html]
>  it is nice for SQS producers to use extended data types (ex "Number.int" 
> instead of just "Number").
> amazon-sqs-java-messaging-lib does this: 
> [https://github.com/awslabs/amazon-sqs-java-messaging-lib/blob/1.0.4/src/main/java/com/amazon/sqs/javamessaging/SQSMessagingClientConstants.java#L39]
> Camel should as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12506) SqsProducer doesn't support Boolean attributes

2018-05-11 Thread Craig (JIRA)

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

Craig commented on CAMEL-12506:
---

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

> SqsProducer doesn't support Boolean attributes
> --
>
> Key: CAMEL-12506
> URL: https://issues.apache.org/jira/browse/CAMEL-12506
> Project: Camel
>  Issue Type: Bug
>  Components: camel-aws
>Affects Versions: 2.20.3, 2.21.0
>Reporter: Craig
>Priority: Major
>
> SqsProducer doesn't support Boolean attributes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-12507) SqsProducer support for Number custom data types

2018-05-11 Thread Craig (JIRA)
Craig created CAMEL-12507:
-

 Summary: SqsProducer support for Number custom data types
 Key: CAMEL-12507
 URL: https://issues.apache.org/jira/browse/CAMEL-12507
 Project: Camel
  Issue Type: Improvement
  Components: camel-aws
Affects Versions: 2.21.0, 2.20.3
Reporter: Craig


According to 
[https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-message-attributes.html]
 it is nice for SQS producers to use extended data types (ex "Number.int" 
instead of just "Number").

amazon-sqs-java-messaging-lib does this: 
[https://github.com/awslabs/amazon-sqs-java-messaging-lib/blob/1.0.4/src/main/java/com/amazon/sqs/javamessaging/SQSMessagingClientConstants.java#L39]

Camel should as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-12506) SqsProducer doesn't support Boolean attributes

2018-05-11 Thread Craig (JIRA)
Craig created CAMEL-12506:
-

 Summary: SqsProducer doesn't support Boolean attributes
 Key: CAMEL-12506
 URL: https://issues.apache.org/jira/browse/CAMEL-12506
 Project: Camel
  Issue Type: Bug
  Components: camel-aws
Affects Versions: 2.21.0, 2.20.3
Reporter: Craig


SqsProducer doesn't support Boolean attributes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-12500) Incorrect URL for AWS SQS queues

2018-05-09 Thread Craig (JIRA)
Craig created CAMEL-12500:
-

 Summary: Incorrect URL for AWS SQS queues
 Key: CAMEL-12500
 URL: https://issues.apache.org/jira/browse/CAMEL-12500
 Project: Camel
  Issue Type: Bug
  Components: camel-aws
Affects Versions: 2.22.0
Reporter: Craig


There should be a . between the region and the host. The queueUrl is, for 
example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be 
{{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.

 

This bug was caused by 
https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12425) SqsProducer doesn't support Number attributes

2018-04-05 Thread Craig (JIRA)

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

Craig commented on CAMEL-12425:
---

[https://github.com/apache/camel/pull/2282]

> SqsProducer doesn't support Number attributes
> -
>
> Key: CAMEL-12425
> URL: https://issues.apache.org/jira/browse/CAMEL-12425
> Project: Camel
>  Issue Type: Bug
>  Components: camel-aws
>Affects Versions: 2.20.2, 2.21.0
>Reporter: Craig
>Priority: Major
>
> SqsProducer doesn't support Number attributes. It only supports attributes 
> with a value of type String or ByteBuffer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-12425) SqsProducer doesn't support Number attributes

2018-04-05 Thread Craig (JIRA)
Craig created CAMEL-12425:
-

 Summary: SqsProducer doesn't support Number attributes
 Key: CAMEL-12425
 URL: https://issues.apache.org/jira/browse/CAMEL-12425
 Project: Camel
  Issue Type: Bug
  Components: camel-aws
Affects Versions: 2.21.0, 2.20.2
Reporter: Craig


SqsProducer doesn't support Number attributes. It only supports attributes with 
a value of type String or ByteBuffer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)