Gyorgy Knyihar wrote: > Hello Thomas, > > I downloaded the latest version and compiled it. It works now. But I think the > problem was that I modified the workflow.xml without creating a new version. I > didn't know that it is not allowed. After modifying the workflow.xml I simply > reloaded the templates. Then when I started a new workflow the changes were > reflected but it looks like that it caused some problems in the system. Do you > mean on textual changes modifying descriptions and notifications?
A started workflow will forever run based on its initial definition. The state of the workflow instance is stored in the db, but it needs its template file to read descriptions for example. So if a workflow is started and its workflow definition gets changed in between it may have trouble finding its node definitions in it afterwards. Changes in texts, scripts and notifications can be made as long as they don't change the workflow structure. To make structural changes, simply start a new workflow version, SWAMP will always start new workflows from the (alphabetical) latest version. > I have a test system and a live one. After testing things on the test system > or > upgrading the test system I move the whole apache-tomcat directory with swamp > to the live system and then I modify the hostname related things in the > webswamp directory. (I undeploy axis and webswamp with tomcat manager before > the upgrade.) I do not change the DB on the live system, so it always contains > the live old data. Do you think is it OK? Or should I expect additional > problems? Of course I stop apache-tomcat before moving and I start it only > after move is done. Sounds OK as long as there are no incompatible changes made in workflow versions that already have running instances on the live server. When there are changes in the database structure you have to take care to convert your live system. I will write to the UPGRADING file when there are those changes. Greetings -- Thomas Schmidt (tschmidt [at] suse.de) SUSE Linux Products GmbH :: Research & Development :: Internal Tools "Wer die Vergangenheit kontrolliert, kontrolliert die Zukunft. Wer die Gegenwart kontrolliert, kontrolliert die Vergangenheit.", 1984 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ swamp-devel mailing list swamp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/swamp-devel http://swamp.sf.net
