wood burning stoves 2.0*
The moose likes EJB Certification (SCBCD/OCPJBCD) and the fly likes Why should remote method arguments/return types always be Serializable Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Certification » EJB Certification (SCBCD/OCPJBCD)
Bookmark "Why should remote method arguments/return types always be Serializable" Watch "Why should remote method arguments/return types always be Serializable" New topic
Author

Why should remote method arguments/return types always be Serializable

jishnu dasgupta
Ranch Hand

Joined: Mar 11, 2011
Posts: 103

Hi all,

I have just started off with EJB and i cant make sense that whay should my argument/return types of method must be of Serializable type, for a remote Object.

Again, if it is Serializable, then the Class 'es must be present in the remote client, if i want to deserialize my remote Object/ stub. In that case what is the point of having a RPC?? Please help me out as I am really confusing myself!!!


If debugging is the process of removing bugs, then programming must be the process of putting them in. -- Edsger Dijkstra

Thiago Alves de Moraes
Greenhorn

Joined: Dec 09, 2010
Posts: 8
Remote method should have arguments and return types serializable because you are going through a remote call, that is, passing data through the network.


--
thiago moraes
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Why should remote method arguments/return types always be Serializable