Tilmann comments

Results 80 comments of


                                            Tilmann

Implement bytecode enhancement for zooActivateRead()/zooActivateWrite() and the rest

Sorry for the late reply, I'm quite with other stuff at the moment. Your classfile transformer looks very useful. I suppose it could also be used to insert the super-class...

Implement bytecode enhancement for zooActivateRead()/zooActivateWrite() and the rest

Thanks for the explanation, that sounds very cool (even though I never used SAP hybris or SAP in general). I also didn't know of ebean, their session-less approach sound really...

java.lang.RuntimeException: Class has not been fully evolved

The 0.5.1 does not contain any changes to the database format, you should be able to simply install 0.5.1 over 0.5.0 and continue working (unless you somehow rely on ZooDB...

java.lang.RuntimeException: Class has not been fully evolved

Export and reimport is the simplest if your environment allows that (you are DB-Admin, database not too large, ...). Otherwise you can use the ZooDB's schema evolution API. It work...

java.lang.RuntimeException: Class has not been fully evolved

Thanks. It appears the problem happened when it tried to read an array of persistent objects, and I guess on of the objects in the array caused the problem. Ideally...

java.lang.RuntimeException: Class has not been fully evolved

@slavap Okay, thanks. That may explain it, I will try to reproduce it.

java.lang.RuntimeException: Class has not been fully evolved

Related to #71

Implement tool that can monitors activateWrite

This could be done using a proxy, see issue #61

Introduce mutual exclusion for JavaObject vs GenericObject

Invalidate and internally delete the GObject when calling Handle.getJavaObject() and invalidate JavaObject (delete???) when calling doing something that requires the GObject to be created (what?). This should make things cleaner...

Clean up GenericObject & GOProxy usage

See updated TODO (emphasizes the same point) and Test_039