Author: objectiser Date: 2010-01-20 12:13:20 -0500 (Wed, 20 Jan 2010) New Revision: 469 Modified: trunk/docs/docbook/userguide/src/main/module/deploy.xml Log: Added further text about explicitly undeploying a version, and what happens to any active process instances associated with the undeployed version. Modified: trunk/docs/docbook/userguide/src/main/module/deploy.xml =================================================================== --- trunk/docs/docbook/userguide/src/main/module/deploy.xml 2010-01-20 17:09:46 UTC (rev 468) +++ trunk/docs/docbook/userguide/src/main/module/deploy.xml 2010-01-20 17:13:20 UTC (rev 469) @@ -229,6 +229,14 @@ </imageobject> <para> + If you expand the deployed project node, in the <emphasis>Server View</emphasis>, you will see that + both of the deployed versions are shown. The older version is retained as there may still be + BPEL process instances using that version of the process. If you right-click on each of the child nodes, you will + see that it is also possible to undeploy the specific versions. However, if you explicitly undeploy + a version, then any remaining active process instances for that version will be terminated. + </para> + + <para> You can then use the menu associated with the project, contained in the <emphasis>Server View</emphasis>, to undeploy the project (using the <emphasis>Add and Remove ...</emphasis> menu item) and finally use the menu associated with the server itself to <emphasis>Stop</emphasis> the server.