Changes between Version 438 and Version 439 of WikiStart

Timestamp:

07/28/21 10:56:44 (3 years ago)

Author:

wouter

Comment:

--

WikiStart

@@ -1001 +1001 @@
 For stand-alone running you need to 
 * download the stand-alone runner, eg download from [http://artifactory.ewi.tudelft.nl/artifactory/libs-release/geniusweb/simplerunner/ geniusweb artifactory] select latest version simplerunner-<latestversion>-jar-with-dependencies.jar. Easiest is to clone the project with {{{svn co https://tracinsy.ewi.tudelft.nl/pub/svn/GeniusWeb/simplerunner}}} 
-* The parties you want to run (in compiled form) must be in your classpath. Typically by adding them to the pom of the stand-alone runner.
+* The parties you want to run (in compiled form) must be java-based (using GeniusWeb, not GeniusWebPython) and in your classpath. Typically by adding them to the pom of the stand-alone runner.
 * The profiles you want to provide to the parties (alternatively you can refer to a profile on a running profile server)
 * A settings.json file containing the [source:/protocol/src/main/java/geniusweb/protocol/session SessionSettings] eg SAOP Settings. [source:/simplerunner/src/test/resources/settings.json view example file]. 
@@ -1014 +1014 @@
 * With stand-alone runner, your parties are run together in a single
  classloader. The main implication is that there may arise version conflicts
- between parties.
+ between parties. 
+* You can only use GeniusWeb-based parties, not GeniusWebPython-based parties
 * Stand-alone runner does NOT enforce the time deadline. Parties may
   continue running indefinitely and thus bog down the JVM and stalling