You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jeff Costello (Updated) (JIRA)" <ji...@apache.org> on 2012/02/19 13:36:34 UTC
[jira] [Updated] (CAMEL-5015) camel-jt400: add support for
KeyedDataQueue
[ https://issues.apache.org/jira/browse/CAMEL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Costello updated CAMEL-5015:
---------------------------------
Attachment: camel-jt400-add-keyed-dataqueues.patch
Patch to add support for keyed data queues
> camel-jt400: add support for KeyedDataQueue
> -------------------------------------------
>
> Key: CAMEL-5015
> URL: https://issues.apache.org/jira/browse/CAMEL-5015
> Project: Camel
> Issue Type: New Feature
> Affects Versions: 2.9.0
> Environment: JVM / IBM iSeries
> Reporter: Jeff Costello
> Labels: camel, jt400, patch
> Attachments: camel-jt400-add-keyed-dataqueues.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> The current DTAQ support is limited to non-keyed data queues. I have created a patch that adds support for keyed data queues. Configuration is done via options on the endpoint, which is the standard.
> When writing to a keyed data queue, the message header "KEY" must contain the desired message key. This can be binary or text, depending upon the Format used.
> When reading from a keyed data queue, the searchKey and searchType must be set.
> Example endpoint configurations
> ------------------------------
> Writing to keyed data queue from JMS
> from("jms:queue:input").
> to("jt400://username:password@system/lib.lib/MSGINDQ.DTAQ?keyed=true");
> ------------------------------
> Reading from keyed data queue to JMS
> from("jt400://username:password@system/lib.lib/MSGOUTDQ.DTAQ?keyed=true&searchKey=MYKEY&searchType=GE").
> to("jms:queue:output");
> ------------------------------
> In addition, I have added the iSeries DTAQ Sender Information to the message header for messages read from a DTAQ.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira