dirkv 2003/11/22 09:31:58
Added: workflow/xdocs downloads.xml index.xml navigation.xml
Log:
some pages for a minimal site
Revision Changes Path
1.1 jakarta-commons-sandbox/workflow/xdocs/downloads.xml
Index: downloads.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Downloads</title>
<author email="[EMAIL PROTECTED]">Commons Documentation Team</author>
<revision>$Id: downloads.xml,v 1.1 2003/11/22 17:31:58 dirkv Exp $</revision>
</properties>
<body>
<section name="Releases">
<p>There are no releases available.</p>
<!--
<p>The following releases are available:</p>
<ul>
<li>Version 1.1 - 20 October 2003</li>
<li>Version 1.0 - 12 August 2002</li>
</ul>
<br/>
<p>
The latest binary release is always available on the
<a href="http://jakarta.apache.org/site/binindex.cgi#commons-workflow";>
Jakarta Binary Downloads page</a>,
its source is available from
<a
href="http://jakarta.apache.org/site/sourceindex.cgi#commons-workflow";>
Jakarta Source Downloads page</a>.
</p>
<p>
Older releases are retained by the Apache Software Foundation but are
moved into a
<a href="http://archive.apache.org/dist/jakarta/commons/workflow/";>
special archive area</a>.
</p>
-->
<p>
<a
href="http://cvs.apache.org/builds/jakarta-commons/nightly/commons-workflow/";>
Nightly source and binary drops</a> are available.
</p>
<p>
Access to the source tree to see the latest and greatest code is possible
through <a href="cvs-usage.html">anonymous CVS access</a>.
</p>
</section>
<!--
<section name="Release Candidate">
<p>
Release candidates for the upcoming 1.1 release can be downloaded
<a href="http://cvs.apache.org/~dirkv/builds/";>here</a>.
</p>
<p>
Please review and report any problem on the
<a href="mail-lists.html">mailing list</a>.
</p>
<p>
Final release target is 20 October 2003.
</p>
</section>
-->
</body>
</document>
1.1 jakarta-commons-sandbox/workflow/xdocs/index.xml
Index: index.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>Overview</title>
<author email="[EMAIL PROTECTED]">Commons Documentation Team</author>
</properties>
<body>
<section name="The Workflow Component">
<p>Modern application architecture and design practices recommend the concept
of "composition" (of existing modules and components) in the assembly of an
overall application, to maximize the resuse of previously built functionality.
However, it is still generally necessary to write original code that "glues"
the components together. It would be useful if individuals familiar with the
business requirements of their systems could create "scripts" to represent
the linkages between components, rather than requiring Java code. The
<em>Workflow</em> proposal intends to create support for just such a
capability.</p>
<p>Scripted workflows is an idea that can be used in many different
application environments and use cases. In particular, a highly desired use
is in managing the interaction with web application users, where the
transaction being performed requires more than one HTML page to be displayed.
However, the <em>Workflow</em> implementation will be strictly layered so
that the underlying scripting engine can be used without any reliance on
web layer APIs</p>
<p>The <em>Workflow</em> project shall create and maintain an engine to
manage and execute scripts, codified in XML. The basic engine shall be
environment independent, but specialized implementations of the basic engine
can adapt the engine to that environment.</p>
<p>One specialized implementation will be included in the <em>Workflow</em>
package itself - an adapter to integrate the workflow engine into the web
layer, by mapping the Workflow concept of bean scopes into the scopes
provided by the Servlet API (request, session, and application). This
implementation will be independent of any particular web application
framework - it is expected that frameworks will further specialize the
web layer implementation in order to integrate the framework's own
capabilities and features.</p>
<p>Scripts for the workflow engine will be codified in XML. It shall be
possible for specialized implementations to register their own sets of custom
Step implementations, under a specific XML namespace, to transparently extend
the set of built in Step implementations that is available to workflow
engine users.</p>
</section>
<section name="Releases">
<p>
See the <a href="downloads.html">downloads</a> page for information on
obtaining releases.
</p>
<br/><br/><br/>
</section>
<section name="Documentation">
<p>
The <a href="apidocs/index.html">JavaDoc API documents</a> are available online.
</p>
</section>
</body>
</document>
1.1 jakarta-commons-sandbox/workflow/xdocs/navigation.xml
Index: navigation.xml
===================================================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE org.apache.commons.menus SYSTEM
'../../../jakarta-commons/xdocs/stylesheets/menus/org-apache-commons-menus.dtd'>
<project name="Commons Workflow">
<title>Commons Workflow</title>
<body>
&top-menus;
<menu name="Commons Workflow">
<item name="Overview" href="/index.html" />
<!-- <item name="Configuration"
href="/configuration.html" /> -->
<item name="API Documentation" href="/apidocs/index.html"/>
<!--
<item name="Developers Guide" href="/guide/index.html"
collapse="true">
<item name="Class Diagrams"
href="/guide/classdiagrams.html"/>
<item name="Sequence Diagrams"
href="/guide/sequencediagrams.html"/>
</item>
<item name="Examples"
href="http://cvs.apache.org/viewcvs/jakarta-commons/cache/doc/"/>
-->
<item name="Downloads" href="/downloads.html"/>
</menu>
&bottom-menus;
</body>
</project>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
