Configure Tomcat for JavaBeans & classes

Developing a web application on Tomcat 4.0 with JSPs in a M-V-C structure, I am using several JavaBeans to encapsulate various data objects, but currently on a very steep learning curve.

The JavaBean (a Java class file) is not currently being recognised by Tomcat.  I have tried to put the files concerned in the <<install>>/common/classes directory and in the application <<appl>>/WEB-INF/classes directory - both with no success.  I have added the correct <Context> object to the <<install>>/conf/server.xml file that points to my application directory.  There seems to be a lot of information about adding servlets to the local <<appl>>/WEB-INF/web.xml file, but does not seem to be an equivalent XML definition for a Java class/bean.

Surely there must be a simple way for Tomcat to recognise Java class files???

Looking forward to any help on this.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are the class files in a package?

if they are make sure you are putting them in your <<app>>/WEB-INF/classes/package/path/classfile.class


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
robertcarrAuthor Commented:
Thanks for the suggestion.  I wasn't using a package (the project isn't really that big - yet).  However, got me thinking...

If I imported the .class file :
<%@ page language='java' import=<<JavaBean>> %>
before declaring useBean, it seems to work.

So what I will probably do with the multitude of beans yet to write, is put them all in a package then import it to the JSPs as required.

It's probably a fudge, but it seems to work.  I still can't understand why changing the classpath had no effect. Looking forward to seeing a book that explains the details of Tomcat in simple terms!

robertcarrAuthor Commented:
Not quite the answer needed, but was a catalyst to finding a solution.
JavaScript Best Practices

Save hours in development time and avoid common mistakes by learning the best practices to use for JavaScript.

changing the classpath is not going to make your JSP/Application see the classes just allow Tomcat's Application Server a path to look for any Java classes that you maybe importing.

A C?

robertcarrAuthor Commented:
Thanks cheekycj - I'm slowly getting there.  Painful but I think I can see the light.  
Anyway next problem is now JDBC.  I think there might be a 100 pointer waiting in the wings, if it hasn't already been asked...
robertcarrAuthor Commented:
Sorry about the C cheekcj.  Only new to the EE, I hadn't quite realised how the grading should work.  Should have been an 'A'.

Sorry for blemishing your previously faultless record.  No idea how to change the grade either.
don't worry Robert, can happen to all of us read also

upgraded to A

JGould-EE Moderator
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.