The Jaxcent.Web namespace contains Jaxcent programming classes except the HTML tag specific classes. The class that will be used most frequently in this namespace is the JaxcentPage class, objects of which class manage the Jaxcent connection and interactions between server and a particular web page.


  All Types     Classes      Interfaces     Delegates  
  Name Description
When using Jaxcent table-cell editing features, this event can be used to listen to changes made by user to any given cell.
Data related to click operations
A request was received from the client, via the client executing "JaxcentServerRequest( args... );" function defined by the Jaxcent JavaScript file.
If using Jaxcent drag-drop features, this event will fire when a drag-drop enabled HTML object has been dropped on another HTML object marked as a drag-drop target.
A Jaxcent event corresponds to an event at the client web-page, such as a mouse-click.
Events with "click data", which indicates if any keys such as control/alt etc were pressed at the time of the click operation.
Listening to these events will cause the client web-page to send all the page form data along with the event. The data will also include table data when Jaxcent table-editing features are used.
Exception handler
This event can be used to receive notification of upload completion. If "success" is true, this event will be followed by the JaxcentFileUploaded event which includes the uploaded data
This event can be used to receive notification of the completion of an upload operation. The "uploadParams" map contains string values for any data in the form. For file data, it will contain a filename. The "fileBytes" map contains byte[] values for any file(s) in the form.
This event can be used to receive intermediate notifications of upload progress. It can be used to display feedback to the user. It indicates "bytesReceived" out of "totalBytes" bytes have been received. "totalBytes" includes length of any files, plus header bytes.
This event can be used to receive notifications when user has started a file upload in a JaxcentUploadForm.
Event to receive form data during page unloading. The data has the same format as GetAllFormData. But at this time, no further interactions with the page are possible. The data can be saved in the session, or otherwise processed. Field verifications cannot be done here. For field verifications, add handler on buttons or other fields, and retrieve the data either individually or by calling getAllFormData().
Jaxcent events that have an integer (index) parameter.
Base class for Jaxcent paged objects.
JaxcentPage is the base class from which all Jaxcent URL handlers need to be derived. In cases where no particular handler is needed (when using auto-session-management and when no data verification is needed), this class can be specified directly as the handler.

This class provides events to process page level operations (load/unload.) It also provides various common utility methods, such as showing JavaScript alert (dialog box) messages.

Data retrieved from the page. For higher network efficiency (less round-trips), it is better to retrieve any required page data along with the click event. The "pageData" member will contain all the data on the page except for tables. If there is any table data to be retrieved from the page (this is usually the case when tables have been made user-editable), the "tableData" member will be non-null, and will contain the table contents.
This event can be used to listen to the Jaxcent "page loaded" event.
This event can be used to listen to the Jaxcent "page unloaded" event.
When using Jaxcent "Delete Row" buttons, this event can be used to listen to row-deletion events by the user.
Jaxcent can (optionally) maintain a "session" (similar to the System.Web.SessionState.WebSessionState that is accessible from "Session" from the HttpContext in ASPX programming.) It is not the same session as ASPX, but does provide some similar features, and can be used in the same way. It is available from JaxcentPage, and is not deleted (except it can be programmatically deleted) as long as the browser is visiting and staying on one or more pages containing the session. When the browser is gone from all such pages, timeout starts, and upon expiry of the timeout, the session is deleted. Default timeout is 5 minutes.

To enable the session, "use-session" must be specified as true for the page, otherwise the session will be null. Session is established at page-load.

Objects can be stored and retrieved from the session on string keys.

The session is not synchronized, if there is a possibility of using the session from multiple threads, access should be synchronized.

Jaxcent session events
Jaxcent events that have a string parameter.
Common Jaxcent exception
This interface is used to retrieve results from a search for multiple elements.
Thrown when page has not yet been loaded, but operations are attempted on it
Thrown when operations are attempted after page has been unloaded.
RelationType provides options for searching for HTML tag elements on the page using node relations such as "next sibling", "previous sibling". These are not available for all searches, but are only provided in a limited fashion, therefore the SearchType class doesn't include these.
The SearchType class provides search constants useful in locating HTML elements on the page. The constants in this class correspond to various options available for searching for HTML tag elements on the page. Note that "search" in this context may not actually be a search, because this class also provides a "createNew" enumeration!