object store, groovy

[albertd]

Hi,

I took a look at darkstar and it looks quite promising. Some wishes I'd like to mention:
1. I learned the object store is running on an internal derby database. For larger projects it should be able to externalize it to a seperate database server.
2. I would like to have more influence on re-creation of objects by simtask, i.e. a callback called after deserialization.
3. I had the idea to write GLO's in groovy. This would, however, require the groovy classloader to be used on deserialization. So it would be nice if I could tell SimTask which classloader to use when creating GLOs. Obvious pros: You can change the source at runtime and immediately see the results. Cons: none, because a java class file is generated.

Albert

[JaydeRyu]

I have a simmilar wonder and request. It would be nice to have a scripting language runnable in a GLO. It would be a awsome way to chage GLO behaviour live.

This place looks so dead at the moment.

[Jeff]

(1)  The 0.9 stack actually uses BerkleyDB.    But you now talk to it through the DataManager.  While the built in one is the standard DataManager you are free to write your own. 
The information on how to write custom managers will be coming with the GPL release.

(2) You can have all sorts of control through the existing Serilaization controls and mechanism.  Look at the docs on Serialization in the API.

(3) You could write a groovy loader as part of your app code.  Alternately the 0.9 stack allows for extension managers and something I've been
thinking of exploring myself is a  "Groovy Manager".