Free persistence script

Major Features:

1. Headers and their contents to expand/collapse on the page are identified through the use of shared CSS class names for easy set up.
2. Ability to specify which contents should be expanded by default when the page first loads.
3. Specify whether only one content should be open at any given time (collapse previous before expanding current.
4. Enable optional persistence so when the user expands a header then returns to the page within the same browser session, the content state is preserved.
5. Style the two states of the headers easily by setting two different CSS classes to be added to the header depending on whether its content is expanded or collapsed. You can also add additional HTML to the beginning or end of each header, such as an icon image that reflects the current state of the content.
6. Arbitrary links can be defined elsewhere on the page performing the same functions as if the user had directly clicked on a header, such as expand a particular header, toggle a header, or expand all headers within a group.
7. A link from another page linking to the target page can cause the desired headers on the later to expand when loaded, via the URL parameter string.
8. Two event handlers on-in-it() and on-open-close() can be used to run custom code when an Accordion Content first loads and whenever a header is opened/closed, respectively.

Major Features:.

1. Serialization support can often be added to types without modifying those types, or them even being aware they are playing along.
2. Out of the box it supports all STL containers (and work a likes), nested arbitrarily deep.
3. Clients can easily extend it to support their own types using, often non-intrusively.
4. It is data-format agnostic, meaning it doesn't internally care about any file formats. It is container-centric, not stream-centric. The provided i/o layer is just one potential solution to i/o, and the core library can be used with arbitrary client-side i/o mechanisms. The core inherently supports in-memory serialization, not requiring any i/o layer whatsoever (this is useful for serializing over a clipboard-like mechanism and for "casting via serialization").
5. Comes with support for several different file formats, and add-on can be written to provide further formats (e.g., sqlite3 databases).

Quartz 1.6.5 brings you a useful scheduling system that can be integrated with, or used along side virtually any J2EE or J2SE application

Applications can vary from the largest e-commerce system to the smallest stand-alone application. Quartz can be used to create simple or complex schedules for executing tens, hundreds, or even tens-of- tousands of jobs; jobs whose tasks are defined as standard Java components or EJBs.

The Quartz Scheduler includes many enterprise-class features, such as JTA transactions and clustering.

Major Features

1. Job Scheduling:
   • At a certain time of day (to the millisecond)
   • On certain days of the week
   • On certain days of the month
   • On certain days of the year
   • Not on certain days listed within a registered Calendar (such as business holidays)
   • Repeated a specific number of times
   • Repeated until a specific time/date
   • Repeated indefinitely
   • Repeated with a delay interval
2. Job Execution:
   • Jobs can be any Java class that implements the simple Job interface, leaving infinite possibilities for the work the Jobs can perform.
   • Job class instances can be instantiated by Quartz, or by the applications framework.
   • When a Trigger occurs, the scheduler notifies zero or more Java objects implementing the JobListener and TriggerListener interfaces (listeners can be simple Java objects, or EJBs, or JMS publishers, etc.). These listeners are also notified after the Job has executed.
   • As Jobs are completed, they return a JobCompletionCode which informs the scheduler of success or failure. The JobCompletionCode can also instruct the scheduler of any actions it should take based on the success/fail code such as immediate re-execution of the Job.
3. Job Persistence:
   • The design of Quartz includes a JobStore interface that can be implemented to provide various mechanisms for the storage of jobs.
   • With the use of the included JDBCJobStore, all Jobs and Triggers configured as "non-volatile" are stored in a relational database via JDBC.
   • With the use of the included RAMJobStore, all Jobs and Triggers are stored in RAM and therefore do not persist between program executions but this has the advantage of not requiring an external database.
4. Transactions:
   • Quartz can participate in JTA transactions, via the use of JobStoreCMT (a subclas of JDBCJobStore).
   • Quartz can manage JTA transactions (begin and commit them) around the execution of a Job, so that the work the Job does happens within a JTA transaction.
5. Clustering:
   • Fail-over.
   • Load balancing.
6. Listeners & Plug-Ins:
   • Applications can catch scheduling events to monitor or control job/trigger behavior by implementing one or more listener interfaces.
   • The Plug-In mechanism can be used add functionality to Quartz, such keeping a history of job executions, or loading job and trigger definitions from a file.
   • Quartz ships with a number of "factory built" plug-ins and listeners.
7. Runtime Environments:
   • Quartz can run embedded within another free standing application
   • Quartz can be instantiated within an application server (or servlet container), and participate in XA transactions
   • Quartz can run as a stand-alone program (within its own Java Virtual Machine), to be used via RMI
   • Quartz can be instantiated as a cluster of stand-alone programs (with load-balance and fail-over capabilities)

Enhancements

• Records in QRTZ_TRIGGER_LISTENERS table are deleted when trigger is paused and resumed
• Logging Trigger History Plugin.trigger Misfired writes incorrect message
• Send Destination Message Job throws naming exception
• Send Queue Message Job throws Class Cast Exception when used with xml plugin acquire Next Trigger executing on Managed Tx Connection when using JobStoreCMT and configured not to acquire triggers within lock

OSWorkflow 2.8.0 is considered as a smart and useful application that is known as a "low level" workflow implementation written in Java. It does not use a graphical tool for developing workflows, but can be configured by writing a xml file as the main conf file for the workflow process.

Graphical solutions dont provide the flexibility to properly fulfill all requirements in a full-blown application. In this way the programmer can go in and customize the OSWorkflow after his specific needs.

Situations like "loops" and "conditions" that might be represented by a graphical icon in other workflow systems must be "coded" in OSWorkflow.

Major Features:

Compiling from CSV: To get the latest version of OSWorkflow,it is recommend that the source via CSV is to be downloaded and compiled using the Jakarta Ant build script provided there. Compiling OSWorkflow from source is trivial with the following ant targets:

1. jar (default) - compiles the library osworkflow.jar
2. example-war - compiles and assembles osworkflow-2.8.0-example.war, which is configured to use memory persistence and should deploy without any configuration into most web containers.
3. example-ear - compiled and assembles osworkflow-2.8.0-example.ear, which is a J2EE application that is configured to use osworkflow with the EJB persistence store. Some configuration of data sources is required, as well as a full J2EE application server.
4. client-jar - compiled and assembles designer.jar, which is a Swing GUI workflow designer application that can be used to visually inspect and edit workflows.