Community
Participate
Working Groups
Rhino and Derby is built into Java 6.0. However, for backward compatible there is a need to keep Rhino and Derby as part of the deployment. Questions: a. Can Derby be made optional? Is there any reason that Derby needs to be part of the main deployment? b. Can Rhino be de-coupled from the code, allowing optional deployment mechanism? Ideally, Rhino would not only be optional, but BIRT allow other scripting languages to be used. I thought part of the goal of Apache’s Bean Scripting Framework (BSF) was to accomplish this goal. Use a generic interface, and then allow the selection of the Rhino implementation.
1. Consider separation of the language used in expression builder and scripting: 1) support other scripting languages, in addition to Java and JavaScript. 2) support structure expression (in addition to java scripting expression) in dataset and data binding to enh performance of data set/result set calculation. Only after we made both change above, can we make Rhino dependency optional. 2. Derby is for the model car demo database and sample reports, the goal is to use sample reports to show BIRT features. It is in the runtime package as well since we want to let user use it to verify BIRT engine is deployed correctly. For those want minimal foot print, it is safe to remove the deby plugin and zip up the war file again. 3. When BIRT supports JRE 6.0, I suggest we provide a BIRT runtimr package for JRE 6.0 that removes deby and Rhino. schedule to 2.3 for this enhancement. Add plan key word for #3 above.
Wei, is M5 the milestone to use Java 6.0's Rhino and Derby? What is the plan if the app server still requires Java 5?
SUN embedded the rhino as the default script engine in JDK1.6. The package name are changed to sun.org.mozilla.* and exported the javax.script API. As BIRT uses the rhino directly, so it is hard for BIRT to use the script engine in JDK1.6 directly. To do so, BIRT should first support a general script lanager, the script language should b evalauted by a general script engine, either the javax.script or apache's script engine. For the Derby, the user can safely remove the Derby plugin from the BIRT build as it is only used by the sample report. defer the first problem to future.
Shall we consider in next release following enhancement? 1. Consider separation of the language used in expression builder and scripting: 1) support other scripting languages, in addition to Java and JavaScript. 2) support structure expression (in addition to java scripting expression) in dataset and data binding to enh performance of data set/result set calculation.
