...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
JSPs (the front end)
You can usually base your jsps off one of the example pages, enter_search_criteria.jsp or search_results.jsp. There has been no choice made on whether we should use bean/logic tags or c tags, so that's up to you although c tags are easier to use.
TBD - this needs to be filled in more on insidemit css layout, js, etc.
TBD - talk about how to go to different actions from the jsp using the hidden thingy
TBD - talk about how to do ajax once Seth figures it out
Taglibs
Standard jstl and struts taglibs are in the app, including:
- c
- fmt
- html
- html-el
- logic
- logic-el
- bean
- bean-el
- tiles
In addition, some extra jakarta taglibs are included:
- string
- datetime
Application settings and messages
Application settings and messages are in the file ApplicationResources.properties.
This file should contain all the messages that the app will display.
It also contains a few other settings:
These need to be configured for each app:
- sap.proxy.pkg - is the name of the proxy package in your app; the sap2java library uses this property to know where your proxies are; e.g. edu.mit.vpis.proxy
- appname - this should be set to the name of your app, e.g. vpis
These are standard: - app.message.generic - this is a generic message that is used to output RFC messages
- errors.gateway - this message is output by IDDAction if you enter via a non EntryAction
- errors.required - not sure what this is...
Sap2Java
See sap2java.
Building and running an app
...