This wiki does not contain official documentation and is currently deprecated and read only. Please try reading the documentation on the Liferay Developer Network, the new site dedicated to Liferay documentation. DISCOVER Build your web site, collaborate with your colleagues, manage your content, and more. DEVELOP Build applications that run inside Liferay, extend the features provided out of the box with Liferay's APIs. DISTRIBUTE Let the world know about your app by publishing it in Liferay's marketplace. PARTICIPATE Become a part of Liferay's community, meet other Liferay users, and get involved in the open source project. Using the LR-Workflow Portlet with SAW-WEB
LR-Workflow Portlet can now be used with saw-web.
The saw-api.jar is also available in the app server classpath (lib/ext in tomcat and domains/domain1/lib in Glassfish).
The advantage of using SAW is that, you could change to a different workflow engine with mininal code changes.
For more on SAW, see here.
saw-web is available along with the LR-plugins ie \liferay-plugins\trunk\webs\saw-web.
saw-web currently supports jbpm-3.1.2.
Modify hibernate.cfg.xml in , saw-web\docroot\WEB-INF\lib\saw-impl-jbpm.jar, to select the right dialect and the hibernate parameters.
Deploy saw-web using the "ant" target.
If the jbpm tables are not created in the "lportal" DB, they would be created.
Deploying the Workflow Portlet
Set use.saw=true in workflow-portlet\docroot\WEB-INF\src\portlet.properties.
The saw-web-service.jar is added to the workflow-portlet\WEB-INF\lib.
The workflow-portlet talks to the saw-web using the ClassLoaderProxy.
