User: starksm
Date: 01/03/29 00:27:53
Modified: documentation jboss1.html jboss_win32_1.html
Log:
Change the obsolete java -jar run.jar to run.bat and run.sh
Revision Changes Path
1.3 +1 -1 newsite/documentation/jboss1.html
Index: jboss1.html
===================================================================
RCS file: /cvsroot/jboss/newsite/documentation/jboss1.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jboss1.html 2001/02/08 05:31:32 1.2
+++ jboss1.html 2001/03/29 08:27:53 1.3
@@ -40,7 +40,7 @@
rm -f install.zip</pre>
<p> You could try running the server now.
Change to the <code>bin</code> directory, and run the program like this:
<pre>cd bin
-java -jar run.jar</pre>
+run.sh</pre>
<p> In a proper installation, the server
should start without any error messages or exceptions being thrown. It will produce
about three pages of output on startup.<br>
The JBoss distribution is supplied with
one test Bean, packaged as <code>bank.jar</code>. This is supplied in the `deploy'
subdirectory, which is where Beans are placed to deploy them. The effect of this is to
deploy the `bank' bean when the server starts up. This is fine the first time, as it
tests that the SQL server is working, but you can usefully move <code>bank.jar</code>
out of the <code>deploy</code> directory when you are sure that everything's OK, and
the server will start up more quickly.
<table border="1" cellspacing="0" cellpadding="5" bgcolor="#ffff80">
1.3 +1 -1 newsite/documentation/jboss_win32_1.html
Index: jboss_win32_1.html
===================================================================
RCS file: /cvsroot/jboss/newsite/documentation/jboss_win32_1.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jboss_win32_1.html 2001/02/08 05:31:33 1.2
+++ jboss_win32_1.html 2001/03/29 08:27:53 1.3
@@ -30,7 +30,7 @@
On a Windows NT system, you will not need
Administrator priviledges. <!-- Commented out... -- KJ Although Install Anywhere
may malfunction (you'll need to use "Other Java-enabled Platforms" instead)
--> JBoss itself will work perfectly well if installed in a user directory and run
as an ordinary user. I will assume in this tutorial that you are installing in
<code>c:\jboss</code>. If you haven't, change the paths as appropriate.</p>
<p>You could try running the server now. <!-- Again, commented out until
InstallAnywhere comes back. -- KJ You can either run the program from the menu like
<code>Start | Programs | jboss2 | Server_jboss2</code> or o --> Open a Command Prompt
(DOS window), change to the <code>\jboss\bin</code> directory and run</p>
<pre>cd c:\jboss\bin
-java -jar run.jar</pre>
+run.bat</pre>
<p> The server should start without any
error messages or exceptions being thrown. It will produce about three pages of output
on startup.<br>
To deploy your beans, put them in
<CODE>C:\jboss\deploy\</CODE>. JBoss' AutoDeploy system will detect a new or revised
<CODE>.jar</CODE> file and automatically deploy your beans. If you still have the
JBoss window open, you'll see some messages scroll by as your bean deploys. (Note:
<CODE>C:\jboss\deploy\</CODE> must exist when you start JBoss or you'll need to
restart the server to activate the AutoDeploy mechanism.) <br>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
