Differences between revisions 1 and 2
Revision 1 as of 2005-03-25 19:28:50
Size: 1401
Comment:
Revision 2 as of 2009-09-20 23:24:20
Size: 1401
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

Beehive has at least one feature that depends whether the system is running in development or production mode. In general, developers run their systems with assertions enabled and production leaves assertions off, so Beehive makes a similar assumption. If you would like to override that assumption, like to leave assertions off but still be in 'dev mode', you may use a system property called beehive.productionmode.

Note: until http://issues.apache.org/jira/browse/BEEHIVE-462 is resolved, you should substitute beehive.produtionmode in the commands below.

export JAVA_OPTS=-ea Using this setting for Tomcat, then Beehive would be running in development mode. If you have <netui:exceptions showDevModeStackTrace="true"/> in one of your pages and an exception occurs, then you will see the stack trace.

export JAVA_OPTS= In Tomcat, this leaves assertions disabled and results in Beehive assuming production mode. If you have <netui:exceptions showDevModeStackTrace="true"/> in a page and an exception occurs, you won't see the stack trace.

export JAVA_OPTS="-ea -Dbeehive.productionmode=true" This is a case where the assumption made by Beehive is overriden: assertions are enabled, but Beehive will run in production mode. If you have <netui:exceptions showDevModeStackTrace="true"/> in a page and an exception occurs, you won't see the stack trace.

DevMode (last edited 2009-09-20 23:24:20 by localhost)