|
Class Summary |
| JOTDataHolder |
JOT user data will be stored in this object
The getter and setters are in JOTDataHolderHelper too minimize this object footprint in memory. |
| JOTDataHolderHelper |
Implementation methods for JOTDataHolder, to keep JOTDataHolder small. |
| JOTFlowClassCache |
Cache that stores "Class" objects requested by flow.conf (ie: controllers and views)
Such as class.forName won't have to be called repeatedly. |
| JOTFlowConfig |
Object representation of the flow config file: flow.conf
Also provide validation methods to cross-check the flow.conf. |
| JOTFlowConfigParser |
This parses flow.conf into a JOTFlowConfig objects
It makes extensive use of Regular Expression to do this. |
| JOTFlowDirective |
Object representation of a flow directive, from flow.conf |
| JOTFlowManager |
High level manager that handles loading and parsing flow.conf. |
| JOTFlowPage |
Object representation of a page/view in flow.conf |
| JOTFlowRequest |
This is a custom extension of the standard HttpServletRequestWrapper with added functionality. |
| JOTMainFilter |
This is the Main entry point for JOT when used in a webapp
This is the main object, that will catch all the requests and process them. |
| JOTRequestCounter |
Use to "throttle" requests
You create a counter with a unique name and how many minutes it stores data for (in memory)
then call addRequest() to count how many request for this IP, in the time span. |
| JOTRewrittenRequest |
Extension of JOTFlowRequest allowing rewriting of the request URL "on the fly" without loosing the original request and associated parameters/attributes
The original request is "wrapped" in a new request with the url, manipulated |
| JOTTemplateCache |
Allow the caching in memory of the templates. |