dhis2-devs team mailing list archive

[Murodullo Latifov <murodlatifov@xxxxxxxxx>]

Hi people,

If you like I can commit my work on struts2 integration into bazaar. These are copy of modules from existing webwork implementations, we can have all in one and even exclude new modules from the rest via poms. Currently two main modules - support-struts2 and web-commons-resources-struts2 and one working module - web-importexport-struts2 are converted.

regards,
murod




________________________________
From: Lars Helge Øverland <larshelge@xxxxxxxxx>
To: Bob Jolliffe <bobjolliffe@xxxxxxxxx>
Cc: Ola Hodne Titlestad <olati@xxxxxxxxxx>; Sundeep Sahay <sundeep.sahay@xxxxxxxxx>; Ola Hodne Titlestad <olati@xxxxxxxxxxxxxxxxxxxxx>; Kristin Braa <kristin.braa@xxxxxxxxx>; Jørn Braa <jornbraa@xxxxxxxxx>; dhis2-devs <dhis2-devs@xxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, May 27, 2009 11:01:21 AM
Subject: Re: [Dhis2-devs] Coding layout - Community-Based Health Information System (CBHIS)





Similarly there has been some talk of *possible* migration of DHIS2
towards struts 2 - at least there is a reasonably clear migration path
and I know Murod has done some work with experimental module.  Is this
something to be considered?   Lars what do you think?

Regards
Bob
 

 I actually gave it a try yesterday. Migrating action classes/interceptors is easy. I ran into some problems though:

- I got some incomprehensible errors related to SAX xml parsing. 
- It's harder to get hold of the xwork ConfigurationManager (must be done trough a DispatcherListener) which is required for the portal.
- Our old acegi security framework had some issues with xwork2. This should be upgraded to Spring security, but will require more work.

Anyways I think this is the way to go if we are to upgrade the existing webwork code as this requires little modification to the hundreds of action classes and interceptors, in contrast to eg spring mvc.


When it comes to technology stack for the houshold system my opinion is that using something completely new like j2ee 6 is unrealistic if we are gonna come up with something pretty soon as it requires all of us to learn new technologies and start from scratch. I believe that, if necessary, we could upgrade a few things in dhis2, like acegi and webwork, and then continue with the same technology / components as today. If we want to use more Spring out-of-the-box components later there is nothing stopping us. 


Lars