The suggested approach to avoid all the problems stated above. The Spring MVC controller–> this would be the best way available in OpenClinica.Base Controller as CoreSecureController–> In order to avoid the performance issues stated above with SecureController, we removed the SingleThreaded model and came up with this servlet controller for data entry module.As there is no reason to use SingleThreadedModel in OpenClinica application and this would choke up the system resources when many simultaneous requests are made. If you are developing a controller, please avoid extending this.
Base controller is SecureController –> This is used widely all across the application and extends SingleThreadedModel (which is deprecated Java Servlet API 2.4).There are 2(3) kinds of controllers used all across the OpenClinica application
The UI layer is common uses jsps, with JSTL libraries along with javascript and Jquery libraries. The business layer code implementation is based on a typical UI-Controller-transaction management model. If the code requires a database change, such as adding a table, altering a table etc, it is important to put in liquibase script. Liquibase does a good job in maintaining the OpenClinica versions and making sure scripts are run at install/upgrade time. Basics of the OpenClinica CodeĪ typical feature might consist of a database change as well as middle-tier and back end integration.įor database changes, OpenClinica uses a 3rd party library called liquibase to upgrade the database & schema from version to version.
#JREBEL ECLIPSE TUTORIAL HOW TO#
Read the overview of how to contribute here. 11 Developing for OpenClinica How to contribute and what to work on
0 kommentar(er)
