[jira] Updated: (SM-1130) FtpPoller should offer configurable targetOperation

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/SM-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated SM-1130:
--------------------------------

    Fix Version/s: servicemix-ftp-2008.01

> FtpPoller should offer configurable targetOperation
> ---------------------------------------------------
>
>                 Key: SM-1130
>                 URL: https://issues.apache.org/activemq/browse/SM-1130
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-ftp
>    Affects Versions: 3.1.2
>            Reporter: Philippe Pinheiro
>            Assignee: Bruce Snyder
>             Fix For: 3.2.2, 3.3, servicemix-ftp-2008.01
>
>         Attachments: SM1130_patch.txt, SMX-1130.txt
>
>
> Same issue as for FilePoller :  SM-1115
> FtpPoller currently does not use a target operation when sending a message to a target service. The operation must be set, for example, when sending a file to a Ode SU. If not set, Ode throws sort of NPE complaining operation is not set.
> FtpPoller should offer a targetOperation property configurable via XBeans.
> This can be achieved by adding a targetOperation property 
> ...
> private QName targetOperation = null;
> ...
> public QName getTargetOperation() { return targetOperation; }
> public void setTargetOperation(QName targetOperation) { this.targetOperation = targetOperation; }
> ...
> protected void processFile(File aFile) throws Exception { ... exchange.setInMessage(message); if (getTargetOperation() != null) exchange.setOperation(getTargetOperation()); // <--- NEW marshaler.readMessage(exchange, message, in, name); ... }
> Then, the SU may be configured properly as follows:
> <f:poller
> service="proj:inbox"
> endpoint="inbox"
> targetService="process:receive"
> targetOperation="process:receive"
> ...
> </f:poller>
> In case the attribute is not set in the xbean.xml, the current behaviour is not changed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.