This week's giveaway is in the EJB and other Java EE Technologies forum.
We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line!
See this thread for details.
The moose likes Distributed Java and the fly likes Unicast Remote Object Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Distributed Java
Bookmark "Unicast Remote Object" Watch "Unicast Remote Object" New topic
Author

Unicast Remote Object

Manas Shukla
Greenhorn

Joined: Mar 04, 2010
Posts: 1
hi all
i am new to java
therefore my question may not be apt for this forum
But why does implementation class has to extend UnicastRemoteObject ???
Andrey Kozhanov
Ranch Hand

Joined: Mar 12, 2010
Posts: 79
Actually, implementation class does not necessary has to extend UnicastRemoteObject. RMI goal is to make objects remotely accessible. There are two ways of doing this:

1. Extend UnicastRemoteObject

2. Call static method UnicastRemoteObject.exportObject with your implementation class as a parameter.

As far as i know, using UnicastRemoteObject either way is required by RMI server.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Unicast Remote Object