Ok, thats the way I would have done it as well :) Looking forward to your code :)
Btw. with all those new entity stores: Would it be sensible to have a default implementation for those blob - entitystores with basic handling for properties/assocs, perhaps having a sax like callback interface for each prop/assoc in the abstract store? (Besides AbstractEntityStoreMixin) Michael Rickard Öberg schrieb: > Michael Hunger wrote: >> Oh, thats unfortunate :) How do you store the entities? Do you use the tree >> structure of the preferences to map the >> entities and their assocs 1:1 on that? > > Each entity gets a Preferences node with the identity as pathname. > Properties are trivial, and assocs are stored with QId.toString(). > ManyAssocs are stored as strings with one QId.toString() per line (i.e. > multiline values). Trivial and fairly readable. Service configs aren't > gonna have much in terms of Associations anyway I think, mostly Properties. > >> Yeah its really cool :) >> Perhaps Niclas can use that to store gui state of the swing application as >> well. > > Yeah, as it is it can store anything. Any non-primitive value will > simply be serialized into a bytearray so there's no limit on what > properties can be used. It's just not very easy to edit bytearrays using > the Property Editor (or RegEdit in Windows). > > /Rickard > > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev -- Michael Hunger Independent Consultant Web: http://www.jexp.de Email: [EMAIL PROTECTED] Enthusiastic Evangelist for Better Software Development Don't stop where you are: http://creating.passionate-developers.org We support Software Engineering Radio (www.se-radio.net) _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
