# Sample configuration for interfacing to a JSR223 script engine in Java 1.6
# This example uses "ruby", "javascript", and "php" (in one page).
#
# External jar requirements (e.g. must be on class path):
# javascript: - built in
# ruby
#  jruby.jar asm-2.2.3.jar asm-commons-2.2.3.jar (from http://jruby.codehaus.org/)
   jruby-engine.jar (in jsr223-engines.tar.gz from https://scripting.dev.java.net/)
# PHP
#  quercus.jar quercus/resin-util.jar quercus/script-10.jar
#  (from quercus-3_1-snap.war - see http://www.caucho.com/resin-3.0/quercus/)
#  jms.jar mail.jar servlet-api.jar
#  (from http://developers.sun.com/downloads/)
# This was true as of March, 2008.
# The choices of "ruby" and "php" are arbitrary, "javascript" 'cause its built-in.

handler=main
log=5
port=9999

main.class=sunlabs.brazil.server.ChainHandler
main.handlers=sunlabs.brazil.handler.CookieSessionHandler \
		sunlabs.brazil.template.TemplateHandler \
		php \
		sunlabs.brazil.sunlabs.ScriptServerTemplate

# Make sure all of the following script engines can be instantiated.
# This is optional, but makes debugging easier.

main.ensure=javascript ruby php

# each session gets it's own interpreter(s): use cookies for sessions id's
main.cookie=interp

# This configures the Script Handler to run all pages ending in "php"
# through the PHP script engine.  The mime type (which must be application/...)
# associates the file suffix with the script engine (which are both php in this case).

php.class=sunlabs.brazil.sunlabs.ScriptHandler
php.mime.php=application/php

# These are the template processing classes
main.templates=set bsl interp
main.debug=true

set.class=sunlabs.brazil.template.SetTemplate
bsl.class=sunlabs.brazil.template.BSLTemplate
interp.class=sunlabs.brazil.sunlabs.ScriptServerTemplate