Technology Stack and Common Programming Procedures
From OSPDocs
Technology Stack and Common Programming Procedures
Technology Stack
From view back to persistence layer, we use the layers described below:
- View - JSPs are the view that the users interact with.
- Control - Plain old java objects (POJOs) are used to do most of the computational heavy lifting, but some of this is still done in the JSPs. (Yuck, yes).
- Model - Hibernate is used to persist the objects back to a MySQL database. Currently at least 2 schemas are used. One schema contains user information and information about the other schema(s). The other schema(s) can be associated with a particular real world organization, such as the USIP, and contain actual simulation data. They also contain some user information, in particular if the user is cleared to be a facilitator, author or admin in that particular schema.
Common Programming Procedures
Below are listed programming procedures we have used to get this project started. They may well not be 'best practice' but they work. As they are replaced, we will move some of this material into the section above. (Its easier to say 'we use framework x' than spell out all of our idiosyncrasies, but for now we have to do the later.)
- Only one properties file is used (other than the log4j properties file). This is the USIP_OSP_Properties_en_US.properties file. It dishes up various variables depending upon whether the run environment has been determined to be 'remote' or 'local.'
- Currently most every JSP containing a form calls itself when the user hits the submit button. In the top of the form the JSP may act directly on the submitted data, or more commonly, call a procedure in its associated ParticipantSessionObject.
