Source

osworkflow / docs / Interface_choices.html

Full commit
<html><head><title>OSWorkflow Interface choices</title></head><body>
<ul class="star">
<li>Up to <a href="Documentation.html">Documentation</a></li>
<li>Back to <a href="Palettes.html">Palettes</a></li>
<li>Forward to <a href="Creating_a_new_workflow.html">Creating a new workflow</a></li>
</ul><p class="paragraph"></p>OSWorkflow provides several implementations of the <b class="bold">com.opensymphony.workflow.Workflow</b> interface that can be used in your application.
<h3 class="heading-1">BasicWorkflow
</h3><p class="paragraph"></p>The BasicWorkflow has no transactional support, though depending upon your persistence implementation, transactional support can be wrapped around this. It is created by doing  <div class="wikicode"><pre>Workflow wf = <span class="java&#45;keyword">new</span> BasicWorkflow(username)</pre></div> where username is the user who is associated with the current request.
<h3 class="heading-1">EJBWorkflow
</h3><p class="paragraph"></p>The EJB workflow uses the EJB container to manage transactions. This is configured in <b class="bold">ejb-jar.xml</b>. It is created by doing <div class="wikicode"><pre>Workflow wf = <span class="java&#45;keyword">new</span> EJBWorkflow()</pre></div>. There is no need to give the username (as in BasicWorkflow and OfbizWorkflow) since that is automatically pulled in from the EJB container once the user has been authorized.
<h3 class="heading-1">OfbizWorkflow
</h3><p class="paragraph"></p>The OfbizWorkflow is exactly like the BasicWorkflow in every way, except that methods that require transactional support are wrapped with ofbiz TransactionUtil calls.<p class="paragraph"></p></body></html>