You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@empire-db.apache.org by "Rainer Döbele (JIRA)" <em...@incubator.apache.org> on 2016/10/29 11:21:58 UTC

[jira] [Commented] (EMPIREDB-227) Spring Integration

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

Rainer Döbele commented on EMPIREDB-227:
----------------------------------------

Can we Close this issue?

> Spring Integration
> ------------------
>
>                 Key: EMPIREDB-227
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-227
>             Project: Empire-DB
>          Issue Type: Improvement
>            Reporter: Ivan Nemeth
>            Assignee: Ivan Nemeth
>         Attachments: empire-db-spring.zip
>
>
> Starting point for a Spring-Empire integration. Code is based on Spring's JdbcTemplate model. 
> There are corresponding classes for Spring's RowMapper, RowCallbackHandler and ResultSetExtractor (EmpireDataReader, EmpireRowCallbackHandler, EmpireReaderExtractor).
> Two examples is inculeded:
> SampleSpringApp does the same as the spring example I've found on Git.
> EmployeeApp: on the same db but with a different apporach (dummy ORM style)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)