eval

There is still one last thing that we need before we move on to JOODBMS--eval.

Previously I was thinking that there would be numerous action classes, one for each method in the API, and that you would evaluate the action. I realize now that I had it backwards--there will be only a few action classes (for different content) and the persistent object evaluates the action.

Actually, we'll likely have it both ways. There will be an execute method on the action which then calls eval on a selected pobject.

Transactions then can carry an XML document which XmlBinder converts to a tree of actions which get executed. The intent here being to reduce the number of subclasses of transaction, for in JOODBMS transactions are persistent objects and that means the class loader must be able to load the class of every transaction ever executed.

Some actions will also need to carry content, like Bytes, Serializable and text.