No, it looks more like a problem with your JSPs.  Bean property names
begin with lowercase letters (unless you expend considerable effort to
make it otherwise).  It is potentially confusing that the initial
lowercase letter by convention appears uppercase in getter and setter
names; for example, getEmpName() and setEmpName(String) would be the
getter and setter for property "empName".

If Jasper couldn't find the bean class then it would have said so; if it
goes so far as to check the presence of a particular property then it
has already introspected the bean class.

NO.  The correct place for classes specific to your web-application is
inside a jar in the webapp's WEB-INF/lib/ directory.  If you prefer, you
can also put it under WEB-INF/classes/ in a directory hierarchy
mirroring the package structure.

If multiple web applications in the same Tomcat instance need to share
classes then those classes should go into Tomcat's
$CATALINA_HOME/shared/lib/ or $CATALINA_HOME/shared/classes/ directory.

Under no circumstances should you put user classes anywhere under
$CATALINA_HOME/common/.

See http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html

Moreover, make sure the classes are in exactly one place within any
given Tomcat instance's sphere.  I promise you that following this rule
will save you hours of grief and frustration.

Put it in the classpath.  You have actually done this already, it seems,
even though you haven't gotten it into the correct part of the classpath.