-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle binary and non-jms header names #1
Conversation
</execution> | ||
</executions> | ||
</plugin> | ||
<!-- <plugin>--> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
couldn't get this plugin to behave, so commented for now
src/main/java/com/amazon/sqs/javamessaging/message/SQSMessage.java
Outdated
Show resolved
Hide resolved
import com.amazon.sqs.javamessaging.SQSMessagingClientConstants; | ||
import com.amazon.sqs.javamessaging.SQSQueueDestination; | ||
import com.amazon.sqs.javamessaging.acknowledge.Acknowledger; | ||
import com.amazonaws.services.sqs.model.MessageAttributeValue; | ||
import org.apache.commons.logging.LogFactory; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
temporary for now?
} else if (BINARY.equals(type)) { | ||
// if Binary, getBinaryValue() should be used but should require an userland mapper | ||
// it must map to one of Boolean, Byte, Short, Integer, Long, Float, Double, and String. | ||
// TODO userland mapper, but for now we're just going to log and skip it. The key won't be added |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks ok to me. I feel like we might run into some issues keeping the groupId of the artifact the same, though.
Agreed, I think ultimately this is a placeholder while we test, and make available for manual builds. I wouldn't publish the artifacts of this one directly. I am going to refactor for the v2 release of the library and craft a real PR with upstream. |
Closing this for now, we have an internal branch of this, and will likely refactor for v2 instead. |
This Pull Request uses a branch-fork from the last aws-sdk v1 tag from the upstream library. We can use this branch to maintain any fixes until all v1 uses are deprecated and removed.
These changes should be able to port forward to the v2 branch at a later date.
The JMS consumer has a couple gotchas that can cause un-rescuable issues when consuming SQS messages from outside sources.
This PR tackles the following issues:
\w
word characters)\W
regex)Relevant upstream tickets:
Similar: