camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-1596) camel-ibatis - Option to control the iBatis operation used so we can use it like camel-jdbc or camel-sql
Date Sun, 10 May 2009 16:22:50 GMT

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

Claus Ibsen resolved CAMEL-1596.
--------------------------------

    Resolution: Fixed

trunk: 773359

> 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: 2.0-M1
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 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.


Mime
View raw message