Re: I'm new to Prevayler: Best practices for updating your architecture?

"Justin T. Sampson" <[email protected]>
Newsgroups gmane.comp.java.prevayler
Message-ID <CAAshuuFMuEn+vSm+bsFVomTwnMGMetW5v0n1jsCBWpXMxukJfg@mail.gmail.com>
Yeah, I've done data upgrades at snapshot deserialization time, both when
using Java serialization and when using XStream.


On Wed, Sep 14, 2011 at 6:44 AM, Karl Wettin <[email protected]> wrote:

> For minor changes I've had a lot of success by implementing Externalizable,
> setting a local version id and then implement refactoring at deserialization
> time that knows how to read the historic versions. You are however somewhat
> limited to what you can do with this. It helps being a fan of strategy
> pattern and aggregation rather than subclassing everywhere.
>
> For major refactoring I usually export the root as XML in the old revision
> and import it to the new revision.
>
> 14 sep 2011 kl. 15.34 skrev Klaus Wuestefeld:
>
> > http://prevayler.org/old_wiki/ThereCanOnlyBeOne.html
> >
> >
> > On Wed, Sep 14, 2011 at 10:28 AM, Naveen Chawla <[email protected]>
> wrote:
> >> What are your best recommended steps, when using Prevayler, for
> >> updating one's object architecture i.e.
> adding/replacing/removing/modifying
> >> fields, methods, inner/nested classes etc.?
> >>
> ------------------------------------------------------------------------------
> >> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
> >> Learn about the latest advances in developing for the
> >> BlackBerry&reg; mobile platform with sessions, labs & more.
> >> See new tools and technologies. Register for BlackBerry&reg; DevCon
> today!
> >> http://p.sf.net/sfu/rim-devcon-copy1
> >> _______________________________________________
> >> To unsubscribe go to the end of this page:
> >> http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
> >> _______________________________________________
> >> "Databases in Memoriam" -- http://www.prevayler.org
> >>
> >>
> >
> >
> ------------------------------------------------------------------------------
> > BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
> > Learn about the latest advances in developing for the
> > BlackBerry&reg; mobile platform with sessions, labs & more.
> > See new tools and technologies. Register for BlackBerry&reg; DevCon
> today!
> > http://p.sf.net/sfu/rim-devcon-copy1
> > _______________________________________________
> > To unsubscribe go to the end of this page:
> http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
> > _______________________________________________
> > "Databases in Memoriam" -- http://www.prevayler.org
>
>
>
> ------------------------------------------------------------------------------
> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
> Learn about the latest advances in developing for the
> BlackBerry&reg; mobile platform with sessions, labs & more.
> See new tools and technologies. Register for BlackBerry&reg; DevCon today!
> http://p.sf.net/sfu/rim-devcon-copy1
> _______________________________________________
> To unsubscribe go to the end of this page:
> http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
> _______________________________________________
> "Databases in Memoriam" -- http://www.prevayler.org
>

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry&reg; mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry&reg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1

_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.