title: 'J2ME Pattern: ActiveRecord' author: Marcus Rohrmoser type: post date: 2008-10-10T22:05:11+00:00 url: /2008/10/j2me-pattern-activerecord/ yourls_shorturl:
Though J2ME forces you to be close with adding classes, type-safe & convenient persistence might be something you don't want to miss.
And as RecordStores are the primary application persistence stores, there's some boilerplate code you can refactor out into one single common base class.
Also – especially from a pattern standpoint – it's a must and increases the unterstandability and maintainability of your code.
So what's the design assumptions and decisions?
Check back later for sample code.
Or just don't code persistence manually but use the floggy J2ME persistence framework. Looks interesting, but I didn't try it out yet.