火烧径-make life easier

[Q]Is there an example of passing a list to a workflows formal parameter? I'd like to pass to a workflow process different string parameters as a list, as the number of parameters varies. How to do that?

[A]The best way to do it is to declare a new type in XPDL. It should be defined as ExternalReference type, which Location attribute is
java.util.ArrayList (in JaWE, go to Package->Type declarations to do it).
After that, you should create a FormalParameter of workflow process, and define its type to be Declared type by choosing the one you declared for the list.
Shark will accept such XPDL, and if your client application handles this variable properly, everything will work fine.

having a subflow process instance, you can get the parent process as following:
 
// we know that the requester of the subflow process is an activity
WfActivity subflwAct=(WfActivity)subProc.requester();
WfProcess parentProc=subflwAct.container();

JaWE depends on JGraph Swing Component (www.jgraph.com), and it generally steers look 'n' feel of JaWE.

Property dialogs follow XPDL specification. They're implemented in org.enhydra.jawe.xml package.

I use GNU/Emacs and eclipse.

regards
--
Vladimir Puskas
Together, Serbia

can each process have a time-out options
> hi,
>
> can each process set a time-out option?
> if it failed to do in a range of time, then it would fall into some other process?
>
> is that possible to do so in the existing system?

Yes. You can set a limit (both on process and activity), and you'll be informed if it expires.

Additionally XPDL specification defines deadlines, which are implemented too.

See (for limit example): test-JavaScript.xpdl or test-BeanShell.xpdl.
For deadlines: deadlineexamples.xpdl.

hope this helps
--
Vladimir Puskas
Together, Serbia

Who runs the Shark project？

The Enhydra Shark project is mainly driven/sponsored by "Together Teaml飉ungen" in Austria, developed by great guys and girls in "Together Teamsolutions" in Belgrade/Serbia plus a lot of help from the community/other companies (like OpenWide) and has the goal to create a complete WfMC/OMG compliant open source workflow engine framework including a set of standard implementations for all plugin APIs and wrappers (like Corba,...).

Different users/developers from the community are already using the flexibility of Shark to provide adapters for other environments like EJBs.

Webservice wrappers EJB session beans APIs will follow.

We are currently also thinking about a .NET port...

The architecture of Shark corresponds to the goals defined by the "Workflow Working Group" of ObjectWeb (www.objectweb.org).

The final vision is to provide a de-facto standard implementation of WfMC/OMG specifications based on principals of Objectweb for open source middleware (LGPL, standards compliant, commercially usable, flexible component architecture, adoptability to different environments, integration with other ObjectWeb technologies,...).

Shark will be included into commercial products of Together Teaml飉ungen but of course the engine/framework itself will stay LGPL on objectweb.org.

Hope that helps.

Greetings.

Alfred Madl