[
https://issues.apache.org/jira/browse/EMPIREDB-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968661#comment-14968661
]
Ivan Nemeth commented on EMPIREDB-227:
--------------------------------------
I've committed some changes to git, mainly code cleanup and simplify.
1. Removed some trivial classes (EmpireStringValueReader etc.)
2. Renamed classes to match both Empire and Sring naming conventions
EmpireDataReader => DbRecordMapper
EmpireRowCallbackHandler => DbRecordCallbackHandler
EmpireReaderExtractor => DbReaderExtractor
EmpireRecordWriter => DbRecordWriter
3. New methods in EmpireTemplate (getBeanList etc.)
4. Example updates
Regards,
Ivan
> Spring Integration
> ------------------
>
> Key: EMPIREDB-227
> URL: https://issues.apache.org/jira/browse/EMPIREDB-227
> Project: Empire-DB
> Issue Type: Improvement
> Reporter: 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)
