Changeset 2706

Timestamp:

02/17/05 11:57:27 (8 years ago)

Author:

hauma

Message:

Proof of concept for a JavaParty RMI server (ticket:224)

• Allow to specify a custom JP access code when starting the runtime environment.
• If no main class is specified, just start the environment without the invocation of a main() method.

File:

• trunk/jp/bin/jpinvite (modified) (5 diffs)

trunk/jp/bin/jpinvite

@@ -46 +46 @@
      layout.
 
+  -code <JP access code>
+     Use a custom access code for the started runtime
+     environment. When contacting the runtime manager, an access code
+     must be given. This prevents virtual machines accidentally
+     registering at the wrong runtime manager. 
+
+     By default an arbitrary but unique code is used. This is
+     sufficient in almost all cases. Only if the runtime environment
+     should be contacted by an external client application, a known
+     access code must be arranged.
+
   -D<property-name>=<value>
      Set a system property consistent on all participating virtual
@@ -219 +230 @@
             shift ; shift ;;
 
+        -code)
+            code="${2}"
+            shift ; shift ;;
+
         -frontend)
             rmIsFrontend=""
@@ -251 +266 @@
     esac
 done
+
+
+if [ ${#*} -gt 0 ] ; then
+    invokeMain=1
+fi
 
 
@@ -314 +334 @@
 host=${nodenames[0]}
 port=1099
-code="JP-${UID}-${RANDOM}"
+code=${code:="JP-${UID}-${RANDOM}"}
 
 nodecnt=${#nodenames[*]}
@@ -382 +402 @@
      -nodename '@NODENAME@' $JPQ_VM_OPTIONS"
 
-execCmd="\
+execCmd="${invokeMain:+\
   exec -host '$host' -port '$port' \
        -code '$code' $verbose \
        -killonexit $JPQ_EXEC_OPTIONS \
-       $quoted_arguments"
+       $quoted_arguments}"
 
 rshCmd="\