1. opensymphony
  2. osworkflow


osworkflow / docs / Functions.html

<html><head><title>OSWorkflow Functions</title></head><body>
<ul class="star">
<li>Up to <a href="Documentation.html">Documentation</a></li>
<li>Back to <a href="Workflow_Concepts.html">Workflow Concepts</a></li>
<li>Forward to <a href="Java-based_Function.html">Java-based Function</a></li>
</ul><p class="paragraph"></p>Functions in OSWorkflow are where you can perform the "meat" of your workflow-based application. They can be executed before and after (pre- and post-) transitions from one state to another in the finite state machine. OSWorkflow supports the following forms of functions:
<h3 class="heading-1-1"><a href="Java-based_Function.html">Java-based Function</a>
<ul class="minus">
<li>Java classes loaded by a ClassLoader</li>
<li>Java classes retrieved via JNDI</li>
<li>Remote EJBs</li>
<li>Local EJBs</li>
<h3 class="heading-1-1"><a href="BeanShell_Functions.html">BeanShell Functions</a> 
<h3 class="heading-1-1"><a href="BSF_Functions.html">BSF Functions</a> (perlscript, vbscript, javascript) 
<h3 class="heading-1-1"><a href="Utility_Functions.html">Utility Functions</a>
</h3><p class="paragraph"></p>OSWorkflow also includes a small set of <a href="Utility_Functions.html">Utility Functions</a> that will start you off in the right direction. Some of these utility functions are extremely valuable in creating dynamic workflow definitions.</body></html>