Hi Wolfram,  Thanks for your message.  I had already done what you
suggested.  The challenge is in changing the weblogic.xml and web.xml files
to make things work. 

I made progress today when I discovered the working-directory parameter
caused the java files generated during jsp compilation to be placed where
Weblogic couldn't find them.  (Weblogic 6.1 seems to have a strong
preference for a central location.)  Once I changed the working directory to
one Weblogic liked better, I finally got parts of the chapter 3 application
to come up and run.  

Now the problem is that the CustomerSearch jsp page doesn't compile because
WebLogic puts it in the default package for jsp's (jsp_servlet) rather than
the same package as the servlets (jsw.c03) even though the weblogic.xml
config file states explicitly that the package should be jsw.c03. 

My problem  with Weblogic was getting a connection to Oracle8i with
Jdriver, I got
the message: "no weblogicoci37 in java.library.path".  Which environment
settings
did you perform so that it worked????

I added the directory .\bin\oci816_8 to my path (full path on my machine is
c:bea\wlserver6.1\bin\oci816_8)
:runWebLogic
echo on
set PATH=.\bin;.\bin\oci816_8;%PATH%
set
CLASSPATH=.;.\lib\j2ee12.jar;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.\bin\
oci816_8

In my case, weblogic is installed in c:\bea so the oci drivers show up in
c:\bea\wlserver6.1\bin\oci816_7  oci816_8 and oci817_8  

 
Thanks in advance for any info.

> The code in Professional J2EE with BEA Weblogic assumes Weblogic version
> 5.1.  Has anyone got it working on Weblogic 6.1? (5.1 is no longer
> available from BEA or I would have used it.) Any pointers or code you can
> share?
>
> After a lot of manual editing, I finally can get the Weblogic server to
> start up and the Oracle Jdriver to work, but have not yet got the JSP's to
> compile and run.
>
> Thanks for any info.
>
> Bob