Closed Bug 282617 Opened 20 years ago Closed 19 years ago

Problems with serialization of Undefined

Categories

(Rhino Graveyard :: Core, defect)

head
x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mcormier, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

This might be related to the changes for bug #280047.

My use case is two applications, one being a "scripting host", the other sending
JavaScript to the first one (over RMI) to evaluate.  The relevant part of the
interface is trivial and looks like:

  public interface RemoteScriptingHost extends Remote {
    public Object eval(String expr) throws RemoteException;
  }

My problem is when RMI unmarshals the return value and it's undefined, I get an
exception like:

java.rmi.UnmarshalException: error unmarshalling return; nested exception is: 
	java.io.InvalidClassException: org.mozilla.javascript.Undefined; local class
incompatible: stream classdesc serialVersionUID = 9195680630202616767, local
class serialVersionUID = 940272108611353017

Both applications are launched from the same code base, so I know the versions
of Undefined match exactly.  Maybe the class needs an explicit serialVersionUID?

Reproducible: Always

Steps to Reproduce:
Version: other → head
Do you use identical JVMs (vendor and version) on both sides?
Yes, we're talking two instances of the same VM (Sun HotSpot Client 1.4.2_06)
running on the same PC.
Reassigning to please_see_bug_288433@eml.cc pending resolution of bug 288433
Assignee: igor.bukanov → please_see_bug_288433
Assignee: please_see_bug_288433 → nobody
This was fixed in CVS HEAD, serial version ID 9195680630202616767 was added manually to the class. It'll show up in the next release
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.