aspose file tools*
The moose likes Distributed Java and the fly likes RMI codebase complications Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Distributed Java
Bookmark "RMI codebase complications" Watch "RMI codebase complications" New topic
Author

RMI codebase complications

Shawn Capron
Greenhorn

Joined: Mar 18, 2014
Posts: 9
I moved this thread from general because I put it in the wrong section.

I am trying to modify the execution string for my RMI service the command works as expected in this format:



but it fails like this:



The exception I get is:



I have read that just specifying a directory for a codebase works with the syntax I have, is there something that I am missing?
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18908
    
    8

My first guess would be that you spelled the class name wrong; try "java.lang.ClassNotFoundException: my.service.Class" instead of "java.lang.ClassNotFoundException: my.service.CLass". (Case-sensitivity)
Shawn Capron
Greenhorn

Joined: Mar 18, 2014
Posts: 9
I apologize that is a typo in my post not my code, I am not allowed to release the actual class name. I will edit my post.
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18908
    
    8

Okay, let's try another guess. What does the asterisk mean here?

-cp "$MAIN_DIR/lib/*"
Shawn Capron
Greenhorn

Joined: Mar 18, 2014
Posts: 9
That is a specification for the java classpath to include all jars in that folder on the class path. I am fairly certain that has nothing to do with the codebase issue. It is the same format both in the command that works, and the one that doesn't work.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: RMI codebase complications