Documentation updated - Overview of GWT application architecture based on GWT-PF article was added.

This overview will help to understand the place and role of GWT-PF in the project.

We are going to take part in Ukrainian Conference for Free Software Developers and Users" during 26-27 of October 2007.

According preliminary conference plan we would have a speech at 17:40 27/10/2007.

Speech topic:   Rich-web user interfaces, projects for creating UI for relation-based (GWT-PF) and semantic-based (ODB-UI) data models.

Short description:   Rich-web UI development, technologies, GWT (Google Web Toolkit). Data representation approaches and appropriate projects for creating UI to them - open source GWT-PF for relation-based models, ODB-UI prototype for semantic models.

When a developers team is starting a project, they are choosing tools, IDE, source control system and the way they are going to stay in touch. We chose Eclipse IDE for development and Subversion (SVN) for code sharing. This is popular combination because it is useful for Java development and specially for GWT.

Successful project code compilation requests GWT libraries, but different developers project sources and GWT libraries is placed in different places on file system. We suggest solution for common project workspace for all developers based on Eclipse environment variables. Testing was done on Eclipse 3.2 and 3.3.

In this arcticle you'll find out two ways about how GWT-application could access the database on the server side using iBATIS. This materials will be useful for developers who create GWT-applications such as database front-ends.

Why iBATIS?

Frequently developers have task to create useful and functional user interface applications to manipulate data (we refered this in post about our solution of  this problev -  GWT-PF). GWT is perfectly applicable for these tasks as good instrument for creating interface and client-server communications. For this purposes GWT has own RPC-interface to remote procedure call or possibility of using JSON-structures to exchange data with server.

But when you have to interact with database on the server-side appears the question about how to unify and automate this process...