In the end, it's possible to make changes to the class which break serial
compatibility, see the "incompatibility exception", paste in the old
serialVersionUID value, into the new class, add a new variable, whose only
purpose is to see the "change" in compatibility and still do this.
public cl
Just thought I'd throw in my 2 cents:
Don't forget that if you do not call defaultReadObject() on the
ObjectInputStream during deserialisation, any additional fields added later
will break serial compatibility.
The Serialization builder pattern allows you to substitute and migrate classes
and
Can't tell from discussion so far but if serialVersionUID wasn't
hardwired, I'm thinking likelihood of compatibility becomes quite
limited?
On 4 February 2013 22:10, Dennis Reedy wrote:
> I'm actually not sure if Dawid has to actually do anything here. The entries
> have been written into the sp
I'm actually not sure if Dawid has to actually do anything here. The entries
have been written into the space and have as their annotation a URL that has
been provided by the entries defining classloader. In this case the entry is
annotated using Rio's artifact URL scheme.
If the change(s) are
On 4 February 2013 19:29, Greg Trasuk wrote:
>
> Out of curiousity, how frequently do people use JavaSpaces as a
> long-term persistence mechanism? Obviously, it's one of the
> possibilities envisioned by the JavaSpace spec, but most examples I've
> seen (and certainly the ones I've implemented)
Hi Greg, One of the major players providing space backed persistence is
Gigaspaces. The whole company is now modeled around concept of java spaces.
One of the big pushes for Gigaspaces is the concept of a space based
in-memory distributed data grid. Their architecture makes the space the
primary da
Out of curiousity, how frequently do people use JavaSpaces as a
long-term persistence mechanism? Obviously, it's one of the
possibilities envisioned by the JavaSpace spec, but most examples I've
seen (and certainly the ones I've implemented) have JavaSpaces as more
of short-term communications me
On 4 February 2013 17:32, Dawid Loubser wrote:
> Thanks Gerard,
>
> That does sound reasonable, but wouldn't I effectively lose the unique
> individual codebase annotations of each entry? I have various unrelated
> services that interact in often-complex ways. Consider the following:
>
> * In foo-
Thanks Gerard,
That does sound reasonable, but wouldn't I effectively lose the unique
individual codebase annotations of each entry? I have various unrelated
services that interact in often-complex ways. Consider the following:
* In foo-api, I have an entry called FooEvent
* In my space-based tim
One easy option may be to write a simple client using your old code to
serialize the entries in the space to XML on disk. Then launch your new
application and put entries into the space instance.
On Mon, Feb 4, 2013 at 3:34 AM, Dawid Loubser wrote:
> Thanks for the quick response, Dan!
>
> I wa
On 4 February 2013 11:34, Dawid Loubser wrote:
> Thanks for the quick response, Dan!
>
> I want to understand the classloading a bit better. Let me explain to
> you how I *think* it works. Also, for reference, I'm using the rio
> project, that has a special classloader that understands URLs in the
Thanks for the quick response, Dan!
I want to understand the classloading a bit better. Let me explain to
you how I *think* it works. Also, for reference, I'm using the rio
project, that has a special classloader that understands URLs in the
form "artifact:foo:bar:1.0" and which loads classes from
On 4 February 2013 11:10, Dawid Loubser wrote:
> Hi all,
>
> I have a bunch of entries in a JavaSpace (representing long-running
> process state, i.e. they exist for days or weeks), and these contain
> some objects that were generated from XML (using JAXB). That vocabulary
> has evolved (additions
Hi all,
I have a bunch of entries in a JavaSpace (representing long-running
process state, i.e. they exist for days or weeks), and these contain
some objects that were generated from XML (using JAXB). That vocabulary
has evolved (additions only) but now, of course, the computed
SerialVersionUIDs w
14 matches
Mail list logo
