I got this one resolved. The issue was I had a non-initialized Java Class
member variable in my bean.
-Original Message-
From: MacCormac Rinehart [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 08, 2001 2:00 PM
To: '[EMAIL PROTECTED]'
Subject: RE: cannot create bean of class...
The code
Hi,
I'm trying again to get some feedback on this issue of instantiating a bean
with Tomcat 3.2.1. I have deployed my riddles package in the WEB-INF/classes
directory for this program. There is an empty constructor in the bean. I
have already ruled out a ClassNotFound exception. At this point
to be to be seen by
Tomcat.
-Original Message-
From: MacCormac Rinehart [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 08, 2001 8:07 AM
To: Tomcat-users (E-mail)
Subject: cannot create bean of class...
Hi,
I'm trying again to get some feedback on this issue of instantiating a bean
with Tomcat
I think the most annoying thing of all is poking fun as someone on a public
forum when all they want is a little guidance. Everyone here has the
beautify key on their keyboard called delete, don't get annoyed at someone
who needs help. Just offer what you can or delete. And in case you haven't
The
answer to your question depends on where you create the connection. If you put
it in the init method, then there is only one because init only gets run the
first time the Servlet is activated. If you put your connection in the
doGet or doPost method, then you will have one connection
);
}
--
Forgive my ignorance, but why are you calling jsp:usebean AND writing the
code to instantiate? Don't you just need one or the other?
-Original Message-
From: MacCormac Rinehart [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 08, 2001 11:31 AM
To: '[EMAIL PROTECTED
I know someone posted a message with a problem similar to this about a month
ago, but was unable to find the solution. I have deployed my riddles
package in the WEB-INF/classes directory for this program. There is an
empty constructor in the bean. I have already ruled out a ClassNotFound
Hi,
This is a guess, I suggest reviewing the garbage collection rules for the
JVM. I know that you're on the right track by assigning null to the object,
but this does not guarantee that the object will be garbage collected, and
there is no way to guarantee garbage collection will run according
