...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
Overview
Projects are "dynamic web app" eclipse projects. They contain this structure:
maybe make each of these their own separate wiki page and have its specific documentation there. So the table below can be converted to a {children} tree.
...
src/
...
...
source
...
...
edu.mit.appname.controller.action
...
where struts actions go
...
...
edu.mit.appname.controller.data
...
where struts forms go
...
...
.
...
where database methods go (for projects that use hibernate)
...
...
edu.mit.appname.model
...
where biz objects go that are passed to the front end
...
...
edu.mit.appname.proxy
...
where generated rfc call and data objects go (for sap projects)
...
...
edu.mit.appname.service
...
where the methods the actions call to get backend data converted to the model go
...
...
conf
...
used on the server for deploying the app to OAS (ignore this directory)
...
WebContent/
...
...
front end
...
...
css
...
contains app_layout.css, etc
...
...
js
...
contains app_specific.js, etc
...
...
WEB-INF/classes
...
where ApplicationResources.properties goes, etc
...
site-template
...
...
a set of template files for your site dir
...
site
...
...
where your local machine specific properties files go, initially copied from site-template
...
...
ApplicationLocal.properties
...
where you place props local to your machine, see below
...
...
build.properties
...
where you put build info local to your machine
...
...
log4j.properties
...
where you configure logging local to your machine
...
build.xml
...
...
In SAP based apps, the service does most of the conversion between SAP objects (proxy) and biz objects, as opposed to Hibernate based apps where the conversion is done by Hibernate in the dao classes.
...