[jira] Updated: (CAMEL-1596) camel-ibatis - Option to control the iBatis operation used so we can use it like camel-jdbc or camel-sql

["Claus Ibsen (JIRA)" <ji...@apache.org>]

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

Claus Ibsen updated CAMEL-1596:
-------------------------------

    Affects Version/s: 1.6.0
        Fix Version/s: 1.6.1

Will backport it to 1.6.1 as the old behavior is just to odd and not useable. In fact you could not pass in arguments to a SELECT statement.

trunk: 773471

> camel-ibatis - Option to control the iBatis operation used so we can use it like camel-jdbc or camel-sql
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1596
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1596
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-ibatis
>    Affects Versions: 1.6.0, 2.0-M1
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 1.6.1, 2.0.0
>
>
> In a route like this
> {code}
> from("xxx")
>    .to("ibatis:selectOrderById")
>    .to("bean:handleOrder")
> {code}
> Does not work as the current codebase expects to insert data when you produce data to it (or select all if body is null). This is kinda {{odd}} behavior.
> So what we need is a new option to specify which operation on SqlMapClient to invoke
> - queryForObject
> - queryForList
> - insert
> - update
> - delete

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