(Help) system classpath -Vs- the place where weblogic looks for classes

Question

The following is my app's hierarchy.
myapp
|
|__myjsp.jsp
|
|__WEB-INF
|
|__classes
|_ MyClass.class
I am not able to use MyClass within myjsp.jsp
i.e. a scriplet like that shown below gives an error stating that MyClass isnt found
<% MyClass obj; %>
I've tried setting the system classpath, but to no avail.
Is there a difference between the system classpath and the place where weblogic looks for classes?
(I am running my app by creating a myapp.war file and placing it in autodeploy folder)

Answer 1

Try moving your class to a named package and use the appropriate import statement in your JSP. Loading it from WEB-INF/classes/packagename should be fine so you might want to remove the other classpath mods you made to eliminate that uncertainty.
Here's a snippet from http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rweb_jsp_migration.html:
"As of JSP 2.0, referring to any classes from the unnamed or default package is not allowed. This can result in a translation error on some containers, specifically those that run in a JDK 1.4 or greater environment which will also break compatibility with some older JSP applications. However, as of JDK 1.4, importing classes from the unnamed package is not valid. See Java 2 Platform, Standard Edition Version 1.4.2 Compatibility with Previous Releases for details. Therefore, for forwards compatibility, applications must not rely on the unnamed package. This restriction also applies for all other cases where classes are referenced, such as when specifying the class name for a tag in a Tag Library Descriptor (TLD) file."
HTH,
Mike
Weblogic/J2EE Security Blog: http://monduke.com