Java Component web application structure and contents
Java Component generates web pages using a set of default JSPs then sends the web pages to a web browser. Actuate Java Component JSPs use cascading style sheets, JavaScript, and custom tags to generate dynamic web page content. The JavaScript and tags provide access to other JSPs, JavaBeans, and Java classes.
The Java Component web application organizes these interoperating components into a Model-View-Controller (MVC) architecture. To operate a web application, the MVC components perform the following functions:
*
Model contains the logic for sending requests to and processing responses from the repository. This component is the data model for Java Component.
*
View contains the pages that display data prepared by actions. This component is the presentation portion of Java Component.
*
Controller contains the servlets that implement actions. This component is the program control logic for Java Component and manages actions initiated from the browser.
The controller maps actions, designated by URLs with the .do extension, to an actionServlet. The actionServlet is configured with action paths specified in <WAR file root>\WEB-INF\struts-config.xml.
Typically, an action path leads to a JSP with parameters as a web resource. Actuate Java Component file and directory names are case-sensitive. The first time you use a JSP, your web server compiles it into a servlet. Servlets are compiled Java programs or JSPs that run as part of a network service such as a web server. After compiling a JSP into a servlet, a web server can fulfill subsequent requests quickly, provided that the JSP source does not change between requests.
Users make requests to view the contents of a repository, run and view reports, and so on. Each JSP processes any URL parameters by passing them to JSP tags.
You specify the user’s file system repository location. To specify the locale and time zone to which to connect, use parameter values in an Actuate Java Component request within a URL or by specifying the desired values in the login form. For example, the following URL specifies the en_US locale for U.S. English, and the Pacific standard time for the timezone parameter:
http://localhost:8080/ContextRoot/login.do?locale=en_US&timezone=PST

Additional Links:

Copyright Actuate Corporation 2012