Originally posted by Tim Lauster:
I did not have the current working directory in my classpath.
Originally posted by James McGee:
The appropriate fix is to set the classpath with an entry that points to your certify folder. For example, if you had your project stored in c:\Jbuilder5\myproject\, you'd want to put C:\Jbuilder5\myproject\classes\certify; into your classpath system environment variable.
I think you can also start the rmiregistry from the directory that your package starts in and it will work as well. In this case that would be the classes directory.
Originally posted by Doug Melzer:
Try specifying a protocol (i.e. file or http if you have a web server)-Djava.rmi.server.codebase="file:/C:/WINDOWS/jbproject/certify/classes"
Originally posted by Michael Ernest:
Remember that before the client gets a stub, rmiregistry's classloader loads _and resolves_ the stub class by using the codebase property. The interface(s) implemented by the stub class must be available via codebase or rmiregistry fails to bind.
Originally posted by Bosun Sogeke:
You might want to compile your java source file(s) using the -d option of javac.
In my code Data's find compares the argument with the values,
where values is a DataInfo array.
Therefore, I think, it should
match with Flight number and in my database there is no such