|
Re: Why is java.rmi.server.SkeletonMismatchException deprecated?: msg#00047java.sun.rmi
>From these frames of the (client-side portion of the) stack trace: > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:350) > at com.xtenit.xxx.run(xxx.java:381) it appears that there is client-side application code that is directly invoking methods of a java.rmi.server.RemoteRef (instead of invoking remote interface methods on a stub containing a RemoteRef, which is the usual thing to do)-- in particular, it is invoking one of the deprecated RemoteRef methods that are used for carrying out the JDK 1.1 RMI stub/skeleton protocol. That would explain why the skeleton is being used on the server side even with 1.4.2, and thus why it has an opportunity to throw SkeletonMismatchException. -- Peter =========================================================================== To unsubscribe, send email to listserv@xxxxxxxxxxxx and include in the body of the message "signoff RMI-USERS". For general help, send email to listserv@xxxxxxxxxxxx and include in the body of the message "help". For a list of frequently asked RMI questions please refer to: http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html To view past RMI-USERS postings, please see: http://archives.java.sun.com/archives/rmi-users.html
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Help: argument type mismatch, Steven M Payeur |
|---|---|
| Next by Date: | Re: Help: argument type mismatch, Peter Jones - JavaSoft East |
| Previous by Thread: | Re: Why is java.rmi.server.SkeletonMismatchException deprecated?, Joseph Shraibman |
| Next by Thread: | Re: Why is java.rmi.server.SkeletonMismatchException deprecated?, Bert Sierra |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |