Hi Again,

No one got back to me but I did learn a few things today:

1. No need to tell the system class path about the WEB-INF area.  All I need
to do is compile from WEB-INF/classes and JDK finds all of my custom
packages.  This is b/c by default . is added to JDK's path.

2. I think I know why TOMCAT can't find my classes. That's b/c I do not have
a /WEB-INF/lib folder.  I think this folder should contain the webapp class
loader among other things.

When I installed TOMCAT 3.2.1 out of the box - the examples webapp did not
have a /WEB-INF/lib folder (unless I accidentally deleted it!).

Question: Where do I download the required files for the /WEB-INF/lib
folder?  Or do I have to build them?

Dennis

Dennis Murphy wrote:

> Hi,
>
> I'm new to JSP.
>
> I desire to use the class reloadable="YES" feature in TOMCAT so that I
> can develop my JAVA BEANS and quickly test them without restarting
> TOMCAT for every little change.
>
> I believe that the reloadable feature will not work if I inform the
> system CLASSPATH where my JSP application classes are located.  The
> reason for this is that the once the SYSTEM CLASS LOADER loads my
> classes the TOMCAT CLASSLOADER has no control and is unable to
> unload/reload my classes.
>
> Okay if I'm right on my understanding of this, then how do you setup a
> development environment.  In order for me to compile my JAVA BEANS using
> JDK javac, I must tell JDK where my classes are located in the SYSTEM
> CLASS PATH ... else it won't be able to pickup my custom packages that
> are part of my application.
>
> So is this like a trade-off? Compile JAVA BEANS or use the TOMCAT class
> reloading feature - but not both?
>
> Can someone please shed some light on how one should setup a development
> environment?  I would like to have the ability to compile and then test
> with tomcat configured to reload classes.
>
> Thank you,
> Dennis

Reply via email to