Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

iBatis + Derby + Vaadin

Jerry Stafurik
1 decade ago Oct 25, 2009 5:17am
Jens Jansson
1 decade ago Oct 25, 2009 7:37am

I haven't used iBatis myself but I've had a look on their tutorials etc. I'd recommend the same as what I would recommend with any database system. Keep your business logic and UI code completely separate - so far that you could control the whole application from a console if you'd have to. This way it doesn't matter which UI library you use, in theory you could switch when ever you want.

One place where you probably have to bind the two sides together, however, are with the containers in Vaadin. Vaadin uses containers (IndexedContainer, HierarcialContainer, BeanItemContainer) to show data inside Vaadin fields (Table, Select, Tree etc.). To build those you'll only need a List or Set of the objects from the businesslogic side that you want to show in the fields. Usually you only need a front controller which would be the glue between an UI class and the businesslogic.

Last updated on Oct, 25th 2009