server field will never be assigned the Server object (because
the Server constructor never returns, because the calling thread
ends up in the loop checking for updates in apps.properties).
which can contain one singel directoy in which to look for skins.
The skin resolution looks like this now:
1) res.skinpath (directory)
2) nodemanagers (internal HopObjects marked as skinmanagers)
3) application directory
href() and renderSkin() functions, without all the other functions in
Helma objectmodel Nodes that don't apply to Java objects. This
was a problem because it "covered" methods in the Java objects
with the same name, e.g. list(), delete() etc.
app name is "base", not when it scripts Helma self. This means
that it is now possible to have more than one applications scripting
the Helma server itself (e.g. a simple overview app in / and a
sophisticated admin app in /admin).
° Removed self boolean parameter from start() and register(), since this is
now determined just once and doesn't have to be carried around. Also,
callers of these methods from outside didn't really know about this parameter.
quotes when building a query. Previously, also
number values were quoted in SQL queries since neither Oracle nor
MySQL seemed to care, but Sybase doesn't like quoted number vaules.
Also, some bits and pieces for version 1.2 type.properties reading.
(see http://helma.org/rfc/mapping12new/ )
a string type and values therefore need to be quoted. Previously, also
number values were quoted in SQL queries since neither Oracle nor
MySQL seemed to care, but Sybase doesn't like quoted number vaules.
properties can't be modified from script code.
Deleted stuff that was permanently commented out:
* setNode() method
* readonly check for created and lastmodified props
function ending with "_action" may be invoked via HTTP. It
isn't necessary anymore to define the action in a .hac file.
As a consequence, it's not possible anymore to invoke
templates (.hsp files) via HTTP. Thus, the exposeTemplates
option has become obsolete.
Implemented onRequest() function which is called on the
object handling the HTTP request before the actual action
is invoked.
