camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Costello (Updated) (JIRA)" <>
Subject [jira] [Updated] (CAMEL-5015) camel-jt400: add support for keyed data queues
Date Sun, 19 Feb 2012 12:38:34 GMT


Jeff Costello updated CAMEL-5015:

    Summary: camel-jt400: add support for keyed data queues  (was: camel-jt400: add support
for KeyedDataQueue)
> camel-jt400: add support for keyed data queues
> ----------------------------------------------
>                 Key: CAMEL-5015
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message