Howzit Chris and Sachin,
I think I found out why it worked. Let me explain, when I was trying to get the rmi server up, I was starting the rmiregistry external to the server in the command line. This was giving me the not bound exception. I then put the exec line in my server itself, which at the time was a dummy server, in the default package (ie no packed). So what it did is start the rmiregistry in the root directory of the application, so that from the root, it could then find com.whatever_stub.
When I structured my dummy application properly and put the server class in a package, suddenly the error NotBoundException returned. so in essence you're right. It is due to a classpath problem, which can be solved in two ways as I have found out recently.
1) in the command prompt, set the classpath to reference the root directory of your application, or start the rmiregistry from the root of your application.
2) there is a solution using the codebase. you have to set the codebase to be exactly that, the base/root of your application, which I think is similar to setting your classpath to the root.
Either way, I think I have now solved the problem on my side for good. I have an environment variable for my application, that points to the root of my app, and I start the rmiregistry from my server, but instead of running the rmiregistry, I run a batch file that starts the rmiregistry using the environment variable.
Hope this helps.
cheers
Darryl