Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.chiba.adapter.* (5)org.chiba.connectors.* (1)org.chiba.test.* (36)org.chiba.tools.* (11)
org.chiba.util.* (3)org.chiba.xml.* (117)

Package Samples:

org.chiba.adapter.web
org.chiba.adapter
org.chiba.connectors.smtp
org.chiba.test.conformance.chapter3
org.chiba.test.tools.schemabuilder
org.chiba.test.xml.util
org.chiba.test.xml.xforms.config
org.chiba.test.xml.xforms.connector.file
org.chiba.test.xml.xforms.connector
org.chiba.test.xml.xforms.constraints
org.chiba.test.xml.xforms.ui
org.chiba.test.xml.xforms.xpath
org.chiba.test.xml.xforms
org.chiba.tools.schemabuilder
org.chiba.tools.xslt
org.chiba.util
org.chiba.xml.util
org.chiba.xml.xforms.action
org.chiba.xml.xforms.config
org.chiba.xml.xforms.connector.file

Classes:

SMTPSubmissionDriver: The SMTP submission driver serializes and submits instance data over SMTP (internet mail). Currently, the driver only supports the post submission method and the replace mode none . Support for form-data-post and urlencoded-post as suggested in 11.2 Submission Options is on the way. The driver requires the additional information about the SMTP server to use, the mail subject, and the sender. This information has to be provided in the query part of the submission's action URI. If you want the driver to authenticate a user with the SMTP server, just provide a username and a password . Support for ...
DOMComparator: The DOM Comparator provides a set of comparison methods to check wether two arbitrary DOM nodes may be considered equal. This may be helpful in testing as well as in editing environments. The comparison behaviour is controllable according to whitespace and namespaces. By default, the comparator ignores any whitespace outside element content and is aware of namespaces. NOTE: It is strongly recommended to normalize the nodes to be compared before comparison by calling the Node.normalize() . Since that method may affect changes in the DOM tree, the comparator won't do this to avoid costly cloning ...
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.
ChibaServlet: The ChibaServlet handles all interactions between client and form-processor (ChibaBean) for the whole lifetime of a form-filling session. The Processor will be started through a Get-request from the client pointing to the desired form-container. The Processor instance will be stored in a Session-object. All further interaction will be handled through Post-requests. Incoming request params will be mapped to data and action-handlers.
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.
AbstractSchemaFormBuilder: An abstract implementation of the SchemaFormBuilder interface allowing an XForm to be automatically generated for an XML Schema definition. This abstract class implements the buildForm and buildFormAsString methods and associated helper but relies on concrete subclasses to implement other required interface methods (createXXX, startXXX, and endXXX methods).
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.
DateUtil: This abstract class is responsible for calculations on and with Dates, for transformation of these to Strings vice versa. Main focus of calculations are Startdates(especially Startdates of calendarweeks). Additionally it extracts from a String that represents a Date only the day, the month and the year. It also gets the calendarweek.
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.
WrapperElementsBuilder: This interface provides methods to create the "wrappers" elements that will contain the XForms document. These elements can be: - the first "enveloppe" element - other elements specific to a destination language or platform (ex: XHTML tags)
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'.

Home | Contact Us | Privacy Policy | Terms of Service