#13 DbCommand serial version

[James Stiefel]

I have repeatedly seen complaints & exceptions relating
to DbCommand's serial version changing:

WARNING: EOF reached in System.in: console disabled
Dec 5, 2005 11:37:50 AM org.ozoneDB.core.InvokeServer
handleClientException
WARNING: handleClientException():
java.io.InvalidClassException:
org.ozoneDB.core.DbRemote.DbCommand; local class
incompatible: stream classdesc serialVersionUID =
-5445281218960850114, local class serialVersionUID =
-2925432770879897790
Dec 5, 2005 11:37:50 AM org.ozoneDB.core.InvokeServer
handleClientException
WARNING: handleClientException():
java.io.InvalidClassException:
org.ozoneDB.core.DbRemote.DbCommand; local class
incompatible: stream classdesc serialVersionUID =
-5445281218960850114, local class serialVersionUID =
-2925432770879897790

I'm not exactly clear on where the problem originates
from, whether it has to do with classes compiled using
different compiler versions or a client compiled
against 1.2 release (or some combination?).

I discovered a similar or related problem previously
and traced it to DbCommand not explicitly defining a
serialver. I corrected that by explicitly defining the
serial version to be the same as it was under 1.2 release.

However, I continue to see complaints when testing
compataiblity between 1.2 and 1.2.1 beta.