ClassNotFoundException with Java Plugin

Hello,
My applet throws a ClassNotFoundException:webprocessor.WebEPApplet.class not found when I use the Java plugin. But if I uninstall the plugin the applet works fine. This is the html I use for when the plugin isn't installed:
<APPLET CODE = "webprocessor/WebEPApplet.class" WIDTH = 510 HEIGHT = 450 >
<PARAM NAME="cabinets" value="wpTest.cab,wp.cab">
<PARAM NAME = "userID" VALUE ="<%=request("userID")%>">
</APPLET>
And this is the source when it is:
<!--"CONVERTED_APPLET"-->
<!-- CONVERTER VERSION 1.0 -->
<OBJECT classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
WIDTH = 510 HEIGHT = 450 codebase="http://java.sun.com/products/plugin/1.2/jinstall-12-win32.cab#Version=1,2,0,0">
<PARAM NAME = CODE VALUE = "webprocessor/WebEPApplet.class" >
<PARAM NAME="type" VALUE="application/x-java-applet;version=1.2">
<PARAM NAME = "cabinets" VALUE ="wpTest.cab,wp.cab">
<PARAM NAME = "codebase" VALUE ="/">
<PARAM NAME = "java_codebase" VALUE ="/">
</OBJECT>
I have tried to leave the CODE value as "webprocessor/WebEPApplet" but it still gives the same error.
Is there a different syntax that I need to use to load my own classes within my own package?
Thanks,
Joe

im a bit lost here as to why it works without and not with the plugin, but maybe try to use the codebase attribute for the directory and the code for the class name.
like this:
<applet codebase="/webapps" code="my class" width="100" height ="100" >
<params here>
<and here>
</applet>

Is this with a 1.3 plugin? I've seen some reports of problems with the 1.3.1_02 plugin, and maybe other 1.3. Sun mentions that the new plugins won't accept class files with format violations created by some of the older compliers, but the exception dumps I've seen don't seem to exactly the exceptions associated with that mismatch, so I'm not sure that is the cause. However, applet for which I've seen the problem (that is, works on IE5.5, but not with 1.3.1_02 plugin) were likely compiled under 1.1.8 or earlier, so they could be the source of the problem.
As I recall, the incompatibility is mentioned in the J2SDK 1.3.1_02 release notes.