Another option would be to use Annotations; annotateClass(..) overrides in our ClassLoaderObjectOutputStream(todo) to pass the extra class information which ClassLoaderObjectInputStream can use to dynamically load new classes .... Have not given much thought on the way we can achieve the same & the repercussions it might have
, but I guess this would be a much cleaner way . comments???? V i n a y --- vinaysahil chandran <[EMAIL PROTECTED]> wrote: > Hi, > The client stubs should be capable > of being passed around as an argument(s).. > a simple program to give the stub > one got from the server back to it is attached > herewith, > One would hope that it would resolve on the server , > to the impl registered with it.... > What would be right way to acheive the same .? > > One way I found was working with making all > proxies as (AltrmiProxy ) being serializable. > (java.rmi.server.RemoteObject is serializable for > this cause) > Maybe DefaultMethodHandler during its > correctArgs(..) > call will replace the stub with remote impl > registered > > with server. > makes sense . > > V i n a y > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Sports - Coverage of the 2002 Olympic Games > http://sports.yahoo.com > ATTACHMENT part 2 application/x-zip-compressed name=more_tests_with_altrmi.zip > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> __________________________________________________ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
