Home >> All

•	nectar.action.* (36)	•	nectar.configuration.* (9)	•	nectar.data.* (27)	•	nectar.form.* (25)
•	nectar.record.* (44)	•	nectar.reda.* (137)	•	nectar.scheduler.* (7)	•	nectar.services.* (7)
•	nectar.template.* (20)	•	nectar.view.* (24)

• nectar: Javadoc index of package nectar.


Package Samples:

• nectar.data.mysql: nectar.data contains the Data Access Classes, including the Query (and related) clases, the DataAdapterService and the DataSource drivers.  
• nectar.template.blocks: The Classes that read and process the page_config.xml configuration file, and construct template and block data elements for web requests.  
• nectar.view.beans: RecordView Implementations and other utility classes to handle records and produce data-driven output.  
• nectar.view: nectar contains all the code for the base system of Nectar WebServices.  
• nectar.reda.io.pgp: The encrypted/compressed client-server communication implementation.  
• nectar.record.datatypes: The Record Classes, data models for the Nectar System.  
• nectar.reda.server.action: The Reda Server implementation.  
• nectar.action
• nectar.configuration
• nectar.data
• nectar.form
• nectar.record
• nectar.reda.client.action
• nectar.reda.client.base.dynacomp
• nectar.reda.client.base
• nectar.reda.io
• nectar.reda.recordeditor.client.action
• nectar.reda.recordeditor.client.tasks
• nectar.reda.recordeditor.client
• nectar.reda.recordeditor.server

Classes:

• RecordDataElement: The top-level class for all record data elements. Record Classes store their property values in the classes that inherit from this abstract class. The RecordDataElement classes offer an input validation method, convert the Object received from the DataAdapter into their base type and convert this type back into a DataAdapter readable String value. Each implementing class must also implement a public * getDataValue(); method, which returns a copy of the value in an approriate object type. RecordInteger has, for example: public Integer getDataValue() { if (value == null) { return null; } else { return ...
• Record: The abstract base model element for data records. To retrieve records from the datasource, you must first know their ID numbers. To do this, see nectar.data.DataAdapterService on how to build and execute queries that will return relevant ID numbers. Once you have one or more ID number, you should retrieve records through the nectar.services.RecordService methods which return record instances. You can then use all the Record.get[*]() methods on the record to retrieve raw data objects from the record, or retrieve a nectar.view.RecordView through the Record.getView() method. Use the set*() methods ...
• RecordConnector: The RecordConnector refers to a special table in the database which allows the linking of multiple records to multiple others. For example, a single ObjectRecord may be linked to several CategoryRecord's while a single CategoryRecord contains multiple ObjectRecord's. Since rows from the Connector shouldn't be accessed directly, this class only provides the field names that should be used for Query objects.
• NectarPlugin: The Struts-style PlugIn Object that initializes and shuts down the various Services in the Nectar System. This is essentially the entry point (ie, main) for all services. It mainly interfaces with ServicesUtil, which in turn initializes the ConfigurationService, which in turn initializes all the Services present in the nectar_config.xml file.
• Query: Query objects are used to define the criteria for a query to the DataSource. It is essentially an object oriented analogy to SQL's SELECT statement. With this analogy, the variables that a Query is defined by could be described as: SELECT (list of fieldnames) FROM (list of tables) WHERE (dataConditions tree) (list of postElements).
• Service: This class must by overridden to implement a Service within the Nectar system. Note that you also need to override the Configuration nectar.configuration.Configuration class for your Service to function properly.
• InternalException: InternalException's are caused by the internal works of the Servlet, for example the DataException (a class that inherits from InternalException) to notify SQL errors. They are eventually handled and logged a little differently in the Action classes.
• NectarException: NectarException is the top-level exception for the Nectar Servlet/System. It can't be instantied directly, you should rather throw it's inheritants to provide more details on the event that caused the Exception.
• RedaModuleDescriptor: Descriptor class for JAR files that contain modules for the Reda Client. This class is mainly used for transporting info about modules available on the server to the client through actions.
• GetRecordListAction: Returns with a list of PersonRecords, built from a list of ID numbers. throws ClientActionException if any of the id number can't be found or data related errors occur.
• CMButtonPanel: A wrapper JPanel for RecordView panels (CMDocCompactPanel, CMNewsEditPanel, etc) that handles the edit toggle button, the delete button, and drag and drop operations.
• ClientPushAction: ClientPushActions are actions sent by the server that aren't responses to direct commands. Some Actions may "subscribe" to ClientPushAction's through the ActionPump.
• ClientCommandAction: ClientCommandActions follow the command response model. The thread that submits a ClientCommandAction to the ActionPump will block until the reponse is received.
• SchedulerConfiguration: This is the Configuration Class for the SchedulerService, it parse the nectar_config.xml file for scheduled tasks, and sets them up in the SchedulerService.
• OrderByPostElement: Analogous to the SQL "order by field_name [asc|desc]" clause. You can append several sorting fields by using the append method.
• ServiceException: Used to signal internal startup, shutdown and runtime exceptions that occur in the implementations of Services.
• ControllerThread: Thread control utilities for creating a thread tree that ensures the shutdown of it's child Threads...
• LogoutAction: This Action is called when a logout attempt is made by the user. It simply invalidates the session.
• DataAdapterService: The DataAdapterService allows access to the DataSource configured in the struts_config.xml file.
• GetModuleList: Retrieves the [module-name] => [version] mapping of the modules available on the server.
• ClientComThread: Client Communication Thread -- handles all the data communication with the server.
• ServicesUtil: A collection of static methods to quickly retrieve the fundamental Services.
• UserView: A value object for that wraps all of the user's security information

Home | Contact Us | Privacy Policy | Terms of Service