dhis2-devs team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

2009/4/14 Lars Helge Øverland <larshelge@xxxxxxxxx>:
>
> A few comments:
>
> - I agree that we could define and implement the various use-cases more
> properly in the service layer, and see if more code could be moved from the
> web layer (I actually had a go at this last week for the reporting module).
> The way I see it this applies the most to the customized data entry part and
> the Indian local modules.

Agreed.  There seems to be a bunch of code in dhis-web-commons
relating to ordering of data elements which might also be pushed down.
 Lets open a new blueprint item to start collecting these cases.  I
haven't looked much at the Indian local modules yet though I know we
will have to start picking at the mysql specific code soon if we are
to be able to deploy on h2.

>
> - The Ibatis code is related to connecting to a MS Access database for the
> DHIS 1.4 file import.

I thought this was the case.  BTW if people are looking for
MSAccess-like functionality, I've been fiddling with my h2 databases
using OpenOffice Base and its pretty good.  Check
http://www.h2database.com/html/tutorial.html#open_office for simple
setup.

>
> - We should definitely see if optimizing Hibernate could be done before
> reimplementing the persistence layer. The pooling can be tuned (even
> switched off), have a look here:
>
> http://www.hibernate.org/214.html
>
> Otherwise, we should maybe make it easier to switch persistence layer
> implementations by collecting all beans dealing with persistence in a
> separate maven project. Changing the persistence layer would then be a
> matter of modifying a dependency definition in a POM.

This sounds like the right approach to me,

Bob