By vihangpathak on Aug 24, 2007
In an effort to enable workflow functionality within products, SAW was conceived. However, a value added feature that has emerged out of it is that it abstracts the interaction with different workflow engines. As the diagram in Understanding SAW guide depicts, the intent of SAW is to be able to integrate with different workflow engines, thereby keeping the product using SAW pretty oblivious to changes.
Currently, SAW comes with a default integration with Java CAPS. For folks having Java CAPS(5.1.3) installation, it should be a matter of minutes to get the client stubs required to perform workflow. After having defined a simple workflow as indicated in my article Incorporating Workflow into Portals with Sun Java CAPS, they should be able to play around with SAW. Ofcourse, alternatively, SAW User Guide offers a typical way of using SAW.
I am sure many of the developer friends will be interested in knowing more about SAW's details. And this is precisely why, the Java Docs are there too.
I invite/request you all to go through all this exhaustive material that we have around SAW and explore/give feedback at firstname.lastname@example.org , join SAW and help enrich it.