Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 7 May 2012 11:07:48 +0000 (UTC)
From: =?utf-8?Q?Jo=C3=A3o_Loureiro_=28JIRA=29?= <jira@apache.org>
To: issues@camel.apache.org
Message-ID: 
 <2106084038.33836.1336388868512.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1825325274.22760.1336066131101.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-5243) jt400: program call should support
 binary format
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Jo=C3=A3o 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 nativ=
e 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 th=
e program execution the endpoint returns either a String array or byte[] ar=
ray with the values as they were returned by the program (the input only pa=
rameters 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 th=
e default format is "text".
               =20
> 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=C3=A3o 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 t=
he one for the data queue.
> Additionally, this patch supports the concept of ommiting a parameter. Th=
is 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 refe=
r to Jt400DataQueueEndpoint.Format; but Format should now be a top-level cl=
ass, 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 administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira