AW: Persistent stored in Context

I guess that iterating over all fields and storing a Map is not what you wanted to hear?!

;-)

I don't see why this shouldn't be possible... is there any danger that resources like connections aren't released or something like that (->all?)?

Would it be possible to have a Map object where you put your persistent, and you store the map in the context...?!?

Anyway, I reviewed my code (thanks Gene... ;-) and I think I might need this, too... now I only store an ID and retrieve the persistent every time I need it.

Aleks

-----Ursprüngliche Nachricht-----
Von: Gene McCullough [mailto:[email protected]]
Gesendet: Montag, 20. September 2004 16:13
An: Keel Users
Betreff: [Keel User] Persistent stored in Context


I've got several models that lookup the same persistent.  So, I was
wondering if maybe I should just stash the persistent in the context. 
However, on accomplishing this, I find out that Persistent is not
Serializable, and i get an exception (java.lang.IllegalStateException to
be precise).

I'd appreciate any comments from anyone on wether this is good, bad, or
indifferent (the storing of persistent in the context), to know if I
should proceed with making this work, or just keep passing the key along
in parameters.  I'm usually for the "if it ain't broke, don't fix it"
method of maintenance, but i'm still early in development and would like
to iron it out now if worth it.

TIA
gene

_______________________________________________
User mailing list
[email protected]
http://lists.keelframework.org/listinfo.cgi/user-keelframework.org