/// under construction ///

For ubuntu users expereiencing this erro, download the following file and unzip and place in the jaxer/components folder of your jaxer install.

libjxMySQL50.zip

On some system configurations, an error may be logged during startup when Jaxer tries to determine the location of the home folder. This may be caused by an invalid or erroneous setting for the HOME environment variable. Make sure that the HOME environment variable references a location that is both a valid folder and is accessible to the user running jaxer. This error can be ignored however further attempts to use the Jaxer.System.homeFolder property will result in the same exception appearing in the logs and the Jaxer.System.homeFolder value will be null.

Jaxer provides a mechanism to identify an application by it's URL structure, this is controlled by the 'configRoutes.js' configuration script.

The Jaxer global routing object (Jaxer.Config.routes) holds an array of javascript functions that return either a NULL, if the url doesn't match the rule, or, a 2 value array, if the url matches the rule, the first value is the identifier for the application and the second value is the identifier for the page. These identifiers are used to manage script access to the Jaxer application and page containers.

The example above would create two applications predicated on the folder structure, the first,the ToyStore application, would be active for any pages server from the myApps/toys folder, the second from the myApps/books folder. These would have an application identifer (Jaxer.application.key) of 'ToyStore' and 'Bookstore' respectively, with each page being identified by it's full URL.

In the event that a URL doesn't match any of the provided rules, the default Jaxer rules would apply which provides an application name based on the fullpath to the folder, and a page context based on the full path to the document being served.

Jaxer currently will not load images server side, this means canvas actions such as drawIimage will throw an exception. This is being tracked in ASAP ticket jxr-172

This has been addressed in Jaxer 0.9.6 and later.

To work around the issue.

use

db.execute("insert into user_roles (user_role_id,access_role_id) values(?,?)"
, db.defaultConnections[Jaxer.DB.DEVELOPER].lastInsertId,3);

Jaxer has configuration settings that allow logging levels be adjusted. Here are some of the settings that you can turn on/off when trouble shooting a problem (Assuming windows platform here).

mod_jaxer (applicable only if apache is configured talking to Jaxer):
This is the module that apache uses talking to Jaxer. The loggings generated by this module are in your apache log (“Aptana Jaxer\logs\apache_error.log” if using the shipped apache server).
To generate extensive loggings, go to your httpd.conf (“Aptana Jaxer\Apache22\conf\httpd.conf” if using the shipped apache server.), change the LogLevel to debug, and restart apache.
LogLevel debug

JaxerManager:
JaxerManager manages the individual Jaxers. It is the bridge between the webserver connector (eg mod_jaxer) and jaxer. JaxerManager writes logs in the same file as Jaxer does. The log file is jaxer.log under “Aptana Jaxer\logs” if you are using the standalone Jaxer install.
You can turn on trace either from the JaxerManager command line (--trace=on) when you start JaxerManager or issue a (set trace on) command through its command port. You can use the utility program tellJaxerManager to do it.
From command line:
JaxerManager –trace=on
After JaxerManager has started:
tellJaxerManager “set trace on”
To turn off the trace,
From command line:
JaxerManager –trace=off
After JaxerManager has started:
tellJaxerManager “set trace off”

Jaxer:
Jaxer is the main process that does the work. It has a few settings that control various logging levels. All Jaxer logs go to the same log file as JaxerManager.

Turn on protocol dumping:
When it is turned on, Jaxer logs all network traffic between it and the webserver connector. The setting is in defaults\pref\Jaxer_prefs.js under the jaxer folder (Aptana Jaxer\jaxer\defaults\pref\Jaxer_prefs.js if using the shipped apache server.).
pref("Jaxer.dev.DumpProtocol", true);
The change requires restarting jaxer. To turn it off,
pref("Jaxer.dev.DumpProtocol", false);

Other Jaxer settings:
In the same Jaxer_prefs.js file, the following settings can be turned on (true) or off (false). Note that these settings control individual levels. Thus to get the maximum loggings, you should setting all of them to true.
pref("Jaxer.CoreTrace.EnableWarning", true);
pref("Jaxer.CoreTrace.EnableInfo", true);
pref("Jaxer.CoreTrace.EnableDebug", true);
pref("Jaxer.CoreTrace.EnableTrace", true);
The configLog.js (under “Aptana Jaxer\local_jaxer\conf” if you are using the standalone Jaxer install) contains additional settings mainly controlling the loggings for server-side javascript execution. You can edit the function() body to adjust the logging levels. Your settings here override the settings in jaxer\framework\configLog.js.