Contents
Primary Presentation
Element Catalog
under the namespace waf::controller::ejb
Parameter
Defines a parameter as a set of key, value and a direct (Boolean) value. Represents a java version of the parameter element in the screen-definitions XML file.
Screen
Defines a screen with a name, its template and a set of parameters. Represents a java version of the screen element in the screen-definitions XML file.
Screens
Defines a set of screens and a default template for them in case they do not have one. Represents a java version of the screen-definitions element in the screen-definitions XML file.
TemplateServer
Wraps€ multiple fine-grained enterprise bean operations in a single transaction, so only a single transaction is created, improving performance. In addition, reads within the single transaction are repeatable, maintaining isolation from other transactions, and data consistency within the view. Inits with the definitions found in the localized version of the file "/WEB-INF/screendefinitions.xml".
tags::InsertTag
Easy interface to the JSP template or other text that needs to be inserted.
Variability Guide
None
Other Information
In the Web tier, the template service assembles multiple JSP pages and Web resources into a single composite view. Much of the data in application views is generated by custom tags, which in turn use data resources such as entity beans with CMP, JDBC connections, connectors, or JMS providers. To ensure isolation, all access to such data resources for a single composite view must occur under the scope of a transaction.
There is no way to automatically start a transaction in response to executing a Web-tier method, as can be done with an enterprise bean method. Therefore, the pet store uses programmatic transaction control in the template service servlet TemplateServlet. TemplateServlet begins a UserTransaction before it forwards a request to the template JSP page, and ends the transaction after the forward has completed.
Related Views
- Parent. Package WAF.