• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Bear Bibeault
  • Rob Spoor
  • Henry Wong
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Frits Walraven
  • Himai Minh
  • Jj Roberts

What in the world happened to JWS ??????

Ranch Hand
Posts: 87
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear friends
I am a new enthusiast of servlets. I had started studying Servlets in August from the famous Jason Hunter book. That time I had Java Web Server (for windows 98 on a month trial basis) and by some minor miracle (!?) had got it configured and working absolutely fine, but then gave up the whole thing in favour of preparing for SCJP. With the grace of god and due help from this site, I have cleared it now but when I tried to restart my work on servlets, it seems the world has changed. For one, I am unable to locate the trial version of Java Web Server for windows 98 ( the one available is for windows NT). I tried to download tomcat after reading on this site about it, but I find that also a minor trick which I am not able to understand. Can someone help me? I'll treat the guy with Stock options in my future Company (***!!!@@@@@)
Ranch Hand
Posts: 255
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I never knew that JWS was free!!! as far as i know it was neer free and never compatible with win98 in fact nothing of the j2EE is compactible with win98 unless you develop it in an IDE.

I wish there was a button on my monitor to turn up the intellegince.
Theres a button called 'brightness' but it doesn't work
Sanjeev Verma
Ranch Hand
Posts: 87
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Brett
Someone rightly said - "Ignorance is Bliss".
Anyway, no thanx to your comments, I got my tomcat up and running within half an hour of that posting. I found the instructions listed below to be of great help:
When the book went to print, only Tomcat 3.0
was available as an official release; Tomcat 3.1
was still in beta. Since then, Tomcat 3.1 has been
officially released, and most readers want to use it
instead of Tomcat 3.0. (JRun, ServletExec and
Resin continue to be other good alternatives for
JSP 1.1 support, and the JSWDK and the Java
Web Server are still acceptable JSP 1.0 options).
So, following is a quick summary of how you
would install and set up Tomcat 3.1 as a
standalone servlet and JSP engine. Integrating
Tomcat with the regular Apache server is more complicated. That is
valuable for a deployment scenario, but my goal here is to show how to
set it up as a development server on your desktop. Regardless of what
deployment server you use, you'll want a standalone server on your
desktop to use for development.
The examples here assume you are using Windows, but can be easily
adapted for Solaris, Linux, and other versions of Unix. I've gotten reports
of successful use on MacOS X, but don't know the setup details.
1.Download Tomcat.
Get it from http://jakarta.apache.org/tomcat/
2.Unzip it.
These example will assume you unzip into C:\, so Tomcat gets
installed in C:\jakarta-tomcat\...
3.Change the port from 8080 to 80.
Edit C:\jakarta-tomcat\conf\server.xml and change the line that says
<Parameter name="port"
value="8080"/> to
<Parameter name="port" value="80"/>.
This is optional, but if you have no other server already running on
port 80, it will make it easier to enter URLs.
4.Modify the startup and shutdown scripts to include
These files are called startup.bat and shutdown.bat and are in
C:\jakarta-tomcat\bin. For example, on my system Java is installed
in C;\JDK1.3, so in startup.bat, after the line
if not "%TOMCAT_HOME%" == "" goto
I added the two lines:
SET TOMCAT_HOME=C:\jakarta-tomcat
Make the same changes to shutdown.bat.
5.Make sure your PATH includes the JDK bin directory.
JSP requires javac, not just java, so your PATH can't just
include the JRE. I set my PATH to include C:\JDK1.3\bin. On
Windows NT/2000 you set the PATH by going to the Start menu,
selecting Settings, choosing System, then choosing Environment.
On Windows 95/98 you probably put the setting in your
autoexec.bat. General directions are in Chapter 1.
6.Update your CLASSPATH.
Make sure it includes:
The top of your package hierarchy. For example, if your
development directory is C:\ServletCode, then your
package-specific classes will go in
C:\ServletCode\packageName, but your CLASSPATH will
include just C:\ServletCode. This is no different from how
you use packages in general in Java, and this is already
described in the book (nothing changed with Tomcat 3.1).
7.Start the server.
Double click on startup.bat. I recommend you make a shortcut (not
a copy!) to startup.bat and shutdown.bat in your development
directories or even on your desktop, so that it is easy to start and
stop the server any time. If you get an error message when starting
the server regarding "Out of Environment Space", then you should
R-click on startup.bat, select Properties, select Memory, and then
find the entry (top right) that says "Initial Environment". Change the
value to 2816 and hit the "OK" button. Repeat for shutdown.bat.
Then try again.
8.Test the server.
Start a browser and enter http://localhost/ as the URL. You should
get a Tomcat home page. Click on a couple of the JSP examples to
verify that the server can find the Java compiler.
9.Compile and install your servlet classes.
The .class files go in
C:\jakarta-tomcat\webapps\ROOT\WEB-INF\classes or
I highly recommend making a shortcut to one of these directories
within your development directory. Then, every time you compile,
just drag the .class files onto the shortcut to install them. You can
also use a script and the -D option to javac to install them
automatically, as described in the book. If you know about defining
your own Web applications, you can change the install location.
But that is not worth bothering with when first starting out, IMHO.
10.Test your servlet classes.
Use a URL of http://localhost/servlet/ServletName or
http://localhost/servlet/yourPackage.ServletName. This is the same
as described in the book.
11.Install your HTML and JSP files.
These go in C:\jakarta-tomcat\webapps\ROOT or
C:\jakarta-tomcat\webapps\ROOT\yourDirectory. Again, I
recommend making a shortcut to this directory from whatever
directory you use for your original HTML and JSP files, and then
just drag them over to copy. (Use the right mouse and select
"Copy" -- I actually copy entire subdirectories over each time.)
12.Test your HTML and JSP files.
Use a URL of http://localhost/yourFileName or
13.Use Tomcat for all the book examples.
Just note that the search engine front end that uses cookies to
remember previous searches won't work. For some reason, the
final release of Tomcat 3.1 doesn't support setting cookies in
servlets that do sendRedirect. It works fine in other servers.
14.Have fun and start programming.
When you become a CEO of an e-commerce company, will you
let me buy stock at your IPO price?
So guys
Enjoy !!!
If you are using a rototiller, you are doing it wrong. Even on this tiny ad:
SKIP - a book about connecting industrious people with elderly land owners
    Bookmark Topic Watch Topic
  • New Topic