Package com.veriplace.web.views

Veriplace can be configured to display "status views" to the end user under certain conditions.

See:
Description

Interface Summary

StatusViewRenderer

Interface for an object that can display "status views" to the end user under certain conditions.

Class Summary

AbstractStatusViewRenderer

Basic implementation of StatusViewRenderer which defines a view name for each error condition and for the "please wait" page, and automatically stores the VeriplaceState object and callback URL in request attributes.

Exception Summary

RespondedWithStatusViewException	Indicates that the application should stop handling the current HTTP request because Veriplace has determined that a transaction cannot be completed at present (either because of an error, or because it is in a waiting state), and has automatically served up a response page from a StatusViewRenderer.
StatusViewException	Thrown if a StatusViewRenderer encounters an error and cannot output the requested status view.

Package com.veriplace.web.views Description

Veriplace can be configured to display "status views" to the end user under certain conditions. These include errors (failed location request) and intermediate steps in a request flow (a "please wait" page). To avoid dependencies on any specific web application framework, Veriplace abstracts this process into a StatusViewRenderer interface.

The SDK includes simple implementations of this interface for servlets (ServletStatusViewRenderer) and Spring servlets (SpringStatusViewRenderer). If you use the AbstractVeriplaceServlet class or the JSP tags, a ServletStatusViewRenderer is created for you; see VeriplaceServletHelper for how to customize its properties. Spring applications should define their own SpringStatusViewRenderer bean if desired.

You do not need to use a StatusViewRenderer at all, as long as your code checks for exceptions and returns the appropriate output. Be sure to handle the WaitingException if you will be making asynchronous requests.