camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From João Loureiro (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5243) jt400: program call should support binary format
Date Mon, 07 May 2012 11:07:48 GMT

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

João Loureiro commented on CAMEL-5243:
--------------------------------------

Sorry I forgot about the text description:

(There is also the detail of the possibility "omitting" a parameter, which is an AS/400 concept).
The text under "Remote program call (Camel 2.7)" can then be rephrased thus:

This endpoint expects the input to be either a String array or byte[] array (depending on
format) and handles all the CCSID handling through the native jt400 library mechanisms. A
parameter can be _omitted_ by passing null as the value in its position (the remote program
has to support it). After the program execution the endpoint returns either a String array
or byte[] array with the values as they were returned by the program (the input only parameters
will contain the same data as the beginning of the invocation)
This endpoint does not implement a provider endpoint!

The "Remote program call example (Camel 2.7)" text remains valid because the default format
is "text".
                
> jt400: program call should support binary format
> ------------------------------------------------
>
>                 Key: CAMEL-5243
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5243
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 2.9.2
>         Environment: AS/400 system
>            Reporter: João Loureiro
>            Assignee: Claus Ibsen
>              Labels: jt400
>             Fix For: 2.10.0
>
>         Attachments: patch.txt
>
>
> Data queue message exchange supports both text and binary formats and so should the remote
program call exchange. The specification is the same as the one for the data queue.
> Additionally, this patch supports the concept of ommiting a parameter. This is achieved
by passing null as the parameter value.
> Implementation note:
> Since I don't know Camel's policy regarding API breaking, I opted to refer to Jt400DataQueueEndpoint.Format;
but Format should now be a top-level class, since the concept is the same for data queues
and programs.

--
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

       

Mime
View raw message