Hmmm... seems odd that JRun ever found the bean to begin with
since compile and reload were never set to true.
Also I didn't take notice of this earlier, but since you're
accessing the JSP via a servlet there's a lot that's potentially
going on behind the scenes and I don't have full access to your
code so it's a bit difficult to square this away, but let's try to
simply our troubleshooting.
First go ahead and make a copy of the existing jrun-web.xml
incase you need to revert back. Add the following lines after the
</session-config> tag (note this is the closing tag).
============================
<compile>true</compile>
<reload>true</reload>
===========================
Again this will force your JSPs and helper classes to
recompile. Restart the JRun instance for this to take effect.
Since your JavaBean seems to indicate it's not part of a
package you should place the file modified Java source code
LoginBean.java at
%app_webroot%\WEB-INF\classes
Make sure the filename is "LoginBean.java" it is case
sensitive. Your login JSP page should remain in the webroot. I am
using the term webroot a quite loosely, because if you were using
IIS you could configure your directories differently. Does the
directory WEB-INF already exist with directories such as cfusion,
classes, lib, jsp, etc.. underneath it?
You said that your login JSP page contains the code....
<%@ page import="LoginBean"%>
<jsp:useBean id="loginBean" scope="session"
class="LoginBean"/>
<html>
<head>
<title>Bibliography Database - Login
Option</title>
</head>
<body>
<h3 align="c....
The line <jsp:getProperty name="loginBean"
property="enteredcustomerid"/> and <jsp:getProperty
name="loginBean" property="enteredpassword"/> should be changed
since your Java code has changed. It should be
<jsp:getProperty name="loginBean"
property="EnteredCustomerId"/>
<jsp:getProperty name="loginBean"
property="EnteredPassword"/>
This is the only change needed for the JSP.
Now before running anything, take a looke at
%webroot%\WEB-INF\classes is there a file called LoginBean.class in
there? If so note the timestamp. Access your JSP page directory
http://localhost/login.jsp.
This should display the login form correctly. There's
something funky going on with my JRun instance and on the first try
I'll get a 500 error, but if I close the browser and access the
page again it will display correctly. Also you should see that the
classes directory has a new or updated LoginBean.class file.
Give this a whirl and tell me what happens. In your comments
your refer to loginBean.java, LoginBean.java, login.jsp, and
loginPage.jsp. Please note that the references should correspond to
your files and case-sensitivity is very important.
You've definitely got a lot of ground to cover in
understanding the relationship between servlets, JSP, classes, and
how to deploy to a J2EE web app server. You may want to checkout a
good introductory J2EE book like Beginning J2EE 1.4 by James
Weaver. ISBN 978-1-59059-341-7
-Tim