[jira] Issue Comment Edited: (CAMEL-3741) Add new options to camel-jt400

["Luis Santos (JIRA)" <ji...@apache.org>]

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

Luis Santos edited comment on CAMEL-3741 at 3/3/11 3:07 PM:
------------------------------------------------------------

@Willem Jiang  
I'm attaching a better excpetion handling when the execution fails. You weere righ, i belive that in case the execution is not successfull (ie program crash/error) the messages should be encapsulated in a excption to camel.

As i'm seeing this the path will only be applied to the trunk so only this patch is being submited now, is this correct?

@Claus Ibsen  
I'm attaching a reviewd documentation page for the camel-jt400 component








      was (Author: luis.santos):
    @Willem Jiang  
I'm attaching a better excpetion handling when the execution fails
As i'm seeing this the path will only be applied to the trunk so only this patch is being submited now

@Claus Ibsen  
I'm attaching a reviewd documentation page for the camel-jt400 component







  
> Add new options to camel-jt400
> ------------------------------
>
>                 Key: CAMEL-3741
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3741
>             Project: Camel
>          Issue Type: New Feature
>    Affects Versions: 2.6.0
>            Reporter: Luis Santos
>            Assignee: Willem Jiang
>              Labels: component, features, jt400
>             Fix For: 2.8.0, 3.0.0
>
>         Attachments: patch_camel-jt400_pgm_call_2.6.0.txt, patch_camel-jt400_pgm_call_exception_handling_trunk.txt, patch_camel-jt400_pgm_call_trunk.txt
>
>
> I've added a new feature to the existing camel-jt400 component to enable the remote program call of iSeries programs.
> This implementation was successfully tested with the jt400 library already included in the pom dependencies against real systems running the version V5R4 od the OS.
> The usage of this new feature is exactly the same of the DATQ feature except the path now has to point to a PGM file and there are 2 mandatory arguments: outputFieldsIdx and fieldsLength.
> *outputFieldsIdx* register which parameters of the program will be INPUT/OUTPUT (as oposed of only INPUT)
> *fieldsLength*: registers the mandatory parameters length
> Sample usage in a route (included in the test case)
> from("direct:a").to("jt400://user:password@host/QSYS.LIB/library.LIB/program.pgm?outputFieldsIdx=1,2&fieldsLength=4,512,2").to("mock:a");
> I'm including a patch to both 2.6.0 and trunk as of today.
> Please let me know if something is not OK.. I'm more than happy to make the adjustments.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira