|Home >> All >> org >> scopemvc >> view >> [ servlet Javadoc ]|
|||org.scopemvc.view.servlet.jsp.* (2)||||org.scopemvc.view.servlet.xml.* (4)|
org.scopemvc.view.servlet: Javadoc index of package org.scopemvc.view.servlet.
org.scopemvc.view.servlet.xml: Contains ServletView , a "container" used to hold a set of Page s that a Controller in a web application manages.
ServletView: A container View to aggregate a set of Page s the allows the currently visible Page to be set. In a servlet application, a Controller's View must 'contain' all the possible pages that the user could be interacting with because the user is free to hit the browser's forward and back buttons, use history or bookmarks etc. This "View" therefore acts as a simple container for other Views ( Page s) that represent the actual interfaces that the user interacts with. It forwards any setController(org.scopemvc.core.Controller) 55 and setBoundModel(java.lang.Object) 55 calls to all children. A Controller ...
Page: Base class for views used by servlet implementation. Pages in a browser do not communicate with the web server, so this class does not implement ModelChangeListener. Model objects in a web application shouldn't bother to implement ModelChangeEventSource unless change notification is used for some purpose other than updating Views. In a servlet application, a Controller must use a ServletView that contains all possible Page s that the Controller can show. Pages must be created with unique View IDs to allow incoming requests to be linked to the correct parent View instance in ScopeServlet. eg http://localhost/scope/servlet/Test?view=TestView&action=TestControl ...
AbstractXSLPage: A ServletView that references an XSLT URI used to transform an XML representation of the View's bound model objects. The XSLT is assumed to describe the entire view, not just a part of the overall page, even when this view is a subview or a parent of subviews. Model objects are turned to a SAX source in a concrete subclass, which is transformed with the XSLT to a SAX stream that gets fed to a SAX ContentHandler (eg an HTML serializer) that writes to an OutputStream (eg the HTTPResponse's output stream). This abstract base class does some generic XSLT handling, including caching compiled stylesheets. ...
ModelToXML: Converts a model into an XML document (as SAX events driving a ContentHandler). Uses a PropertyIDGenerator to create "path" attributes for all elements, and "id" attributes for model elements. Handles circular references using the "ID" and "IDREF" pattern. (data id='_root') (name path='name')Steve(/name) (pets path='pets') (element index='0' path='pets.0') (data id='pets.0') (name path='pets.0.name')Trevor(/name) (/data) (/element) (/pets) (/data)
XSLPage: A concrete AbstractXSLPage that uses Scope's ModelManager implementations to serialise its entire bound model object to an XML document. A better strategy would be to use a more intelligent view that selectively serialises relevant parts of the model object. Handles circular references using the "ID" and "IDREF" pattern.
PropertyIDGenerator: Generates IDs to identify properties during the traversal of the model containment hierarchy. Used by ModelToXML. The ids in the xml could be used as form parameters to identify properties to be populated with user input. This is used by the ID generators defined as inner classes in XSLPage .
JSPPage: A concrete org.scopemvc.view.servlet.Page . ***** Doesn't do the populateModel stuff yet
ValidationFailure: Object to describe a failure to populate a model property with a certain value.
PropertyTag: JSP tag to fetch a named property from the JSPView's bound model.