| Home >> All >> org >> chiba >> xml >> [ xforms Javadoc ] |
• org.chiba.xml.xforms: Javadoc index of package org.chiba.xml.xforms.
Package Samples:
• org.chiba.xml.xforms.action
• org.chiba.xml.xforms.config
• org.chiba.xml.xforms.connector.file
• org.chiba.xml.xforms.connector.http
• org.chiba.xml.xforms.connector
• org.chiba.xml.xforms.constraints
• org.chiba.xml.xforms.events
• org.chiba.xml.xforms.exception
• org.chiba.xml.xforms.ui
• org.chiba.xml.xforms.xpath
Classes:
• FileSubmissionDriver: The file submission driver serializes and submits instance data to a file. Currently, the driver only supports the put submission method and the replace mode none as suggested in 11.2 Submission Options . Another implementation could easily provide support for the get method, but we feel very insecure about it. The driver is quite simple: It just tries to serialize the instance data to the specified file. To make use of it, just provide an absolute file URL in a submission's action , e.g.: <xforms:submission id='file' xforms:action='file:///usr/local/xforms/instance.xml' /> Since file systems ...
• LocalValue: Some ModelItemProperties define inheritence rules for propagating constraints from parents to children in DOM. For correct evaluation of these Properties both the local value of a instance node and the inherited value must be combined. From the Spec.: Some model item properties define inheritance rules, in which case the XForms Processor needs to keep track of two separate values: 1) the local value, which is applied from an attribute of element bind, and 2) the inherited value, which is determined by combining the evaluated local value with the evaluated values from ancestor nodes in the instance ...
• URI: This class is a simple URI implementation which parses string and URLs. This is not complete URI implementation. Only the part before the first colon ( : ) is treated as a scheme. The part after a hashmark ( # ) is treated as a fragment. The part between a colon and a hashmark is treated as path. If there is no colon, the URI is regarded to have no scheme. If there is no hashmark, the URI is regarded to have no fragment, respectively. Thus, if there is neither a colon nor a hashmark, the URI is regarded to consist of a path only.
• HTTPSubmissionDriver: The HTTP submission driver serializes and submits instance data over HTTP/1.1. Currently, the driver supports the post and put submission methods. Support for get , form-data-post and urlencoded-post as suggested in 11.2 Submission Options is on the way. Maybe security functionality will be added later, thus becoming a HTTPS driver. See the '/web/forms/action.xml'-form for examples how to use HTTP submission.
• PreProcessor: Note: currently without use - may be re-activated later The PreProceesor handles all pre-initialization tasks as such: [1] validating the XForm Container to ensure structural and syntactical correctness of the input-form (not yet implemented) [2] check for correctness of references in form. These include: - existence of bind-elements (Chiba works only for documents with explicit bind elements) - correctness of binding link - correctness of nodeset reference
• ModelItemProperties: Instance data item objects are annotations to the DOM nodes which represent the instance data. State information resulting from such operations as recalculate and revalidate will be stored here. UI classes use the computed properties to fetch the current status of the bound item. ModelItemProperties are contributions to the infoset of a instance data node. Each of this contributions like readonly, relevant, required, constraint is a ModelItemProperty.
• FileURIResolver: This class resolves file URIs. It treats the denoted file resource as XML and returns the parsed response. If the specified URI contains a fragment part, the specified element is looked up via the getElementById . Thus, the parsed response must have an internal DTD subset specifiyng all ID attribute. Otherwise the element would not be found.
• HTTPURIResolver: This class resolves http URIs. It treats the denoted http resource as XML and returns the parsed response. If the specified URI contains a fragment part, the specified element is looked up via the getElementById . Thus, the parsed response must have an internal DTD subset specifiyng all ID attribute. Otherwise the element would not be found.
• XFormsSubmitError: 4.4.18 The xforms-submit-error Event Dispatched as an indication of: a failure of the submit process, as defined at 11 Submit Target: model Bubbles: Yes Cancelable: No Context Info: The submit method URI that failed (xsd:anyURI) Default processing for this event results in the following: None; notification event only.
• XFormsElementFactory: XFormsElementFactory creates objects for all DOM Nodes in the input Document that are in the XForms namespace or are bound to some instance node by XForms binding attributes. These objects holds the XForms semantics and are attached to their original DOM equivalent via the Xerces-specific getUserData/setUserData methods in ElementNSImpl.
• SubmissionDriver: A submission driver performs instance data serialization and submission over a specific transport protocol. Implementors of this interface are expected to return a map containing at least an input stream providing the submission response. Additional information like headers should be provided in the map, too.
• Container: This class represents a complete XForms document. It encapsulates the DOM document. The XForms document may consist of pure XForms markup or may contain mixed markup from other namespaces (e.g. html, svg, wap). Responsibilities are: - creation of Model objects found in input
• NamespaceCtx: This class wraps the namespace informations used by a given xforms model processed. It contains all namespaces and prefixes used by XForms and Chiba along with utility method for resolving namespace URIs and prefixes either from root or by context.
• XFormsBindingException: 4.5.1 The xforms-binding-exception Event Dispatched as an indication of: an illegal binding expression, or a model attribute that fails to point to the ID of a model element, or a bind attribute that fails to point to the ID of a bind element.
• InsertAction: Implements the action as defined in 9.3.5 The insert Element . * * @author Ulrich Nicolas Lissé * @version $Id: InsertAction.java,v 1.11 2003/09/18 17:33:03 joernt Exp $
• URIResolver: A URI resolver performs link traversal as postulated for linking attributes. Implementors of this interface are expected to return a DOM node as the link traversal result. Other object models may be supported in the future.
• XFormsActionGroup: Interface for all action group implementations. An action group is used to group multiple actions. It has to implement deferred update behaviour in terms of 10.1.1 The action Element .
• ConnectorFactory: Creates connector instances according to the URI schema passed in. Only absolute URIs are supported. This means they must have a scheme that identifies the protocol to be used.
• XMLBaseResolver: Basic Implementation of XML Base Recommendation 27 June 2001. This class handles only URIs embedded in the content of the document as described in '4.1 Relation to RFC 2396'.
• BindingResolver: The binding resolver implements the scoped resolution of model binding expressions as well as ui binding expressions. In future it may act as a binding factory.
• XFormsLinkError: 4.5.3 The xforms-link-error Event Dispatched as an indication of: a failure in link traversal of a linking attribute, in a situation not critical to form processing.
• CalculateVertex: The calculate vertex implementation used in the recalculation sequence algorithm. This class also implements the virtual value vertex.
• PathUtil: This class is a utility class which contains some static methods which deal with the manipulation of canonical xpathes (as defined by XForms).
• DOMFactory: Creates DOM-Elements for JXPathes that don't exist. It is used by the createPathAndSetValue method to create appropriate objects.
• XFormsDocument: Created by IntelliJ IDEA. User: Administrator Date: 22.09.2003 Time: 14:03:06 To change this template use Options | File Templates.
| Home | Contact Us | Privacy Policy | Terms of Service |