child node, but *never* deletes it from the database. remove()
actually deletes the node from the database and also releases it
from its parent.
This affects HopObject.remove() and HopObject.remove(HopObject),
which use these methods. From now on, the only way to delete a
HopObject from db is to use the remove() function without arguments.
HopObject.remove(HopObject) should be used to
- remove a child object from an embedded db collection without
deleting it
- removing a hopobject from a relational db collection with
cachemode = aggressive if the collection does not belong to the
child object's parent.
- Do not return on-demand nodes (groupby, accessname) in getProperty().
- Avoid creating loops in parent chain when creating cyclic references
on transient objects before committing them to db
- Removed unused links vector and code
- Rename Enumerations because enum is a reserved word in Java 1.5
don't start it) and run the application and through that class. config arguments
are exactly the same as in the main Server class.
commandline arguments after the [appname.functionname] part are now
passed to the function call as arguments.
scripting exceptions from the application are caught and printed correctly.
by merging it with invokeXmlRpc() - the only difference is in the XML-RPC access check,
so we shouldn't have to duplicate all code.)
* Make execution of global onStart() function synchronous in Application.start()
* Fix bug where user.onLogout() is called on a released RequestEvaluator
always unwrap it before processing/returning.
* If a script function returns null or undefined, return null even when
invoke() was called in XML-RPC mode.
a complex reference or create-one-demand relation! This was introduced because
we assumed that the calling code would know what it was doing, i.e. only call this for
objects contained in its subnode index, but as it seems to turn out it didn't, and this isn't
really necessary after all.
in Node.getProperty(). This was there in the old version of Node.getProperty() but was
kicked out in the recent rewrite, which caused NodeManager.getNode() to be called when it
shouldn't.
