Community
Participate
Working Groups
Build Identifier: 2.6.0 If using a data set containing a numeric column name in a joint data set then the joint data set interprets the numeric column name as column index. This results in an exception if no such column index exist in data set. Reproducible: Always Steps to Reproduce: 1. Create a data set with a computed column named "123" 2. Create a joint data set, joining former data set to itself (join column and type are insignificant) 3. Preview results of joint data set Expected result: everythings works fine Actual result: Exception is thrown cause numeric column name is used as column index.
Created attachment 175386 [details] Stacktrace of exception on Preview Results
Created attachment 175387 [details] sample report Attached a sample report with the erroneous joint data set.
This is Rhino's behavior to handle "123" as 123,so currently we have no idea to check whether it means index or name.
*** Bug 375302 has been marked as a duplicate of this bug. ***
This is a rhino, BIRT can do nothing to it. Mark as won't fix.
The Report Engine works fine generating the report. Why should the report generation work and - at the same time - the Data Set Preview Results not work, when a column has a "number" (like the string "7") as name? Data Set Preview Results: I see no reason, why a Java program, which calls a Java-Script (and probably only with one method call as JavaScript: dataSetRow["<column name>"]), which then calls a Java-method again, cannot be written in pur Java instead. (see stacktrace in Bug 375302) IMHO it is unlikely, that the Rhino-/JavaScript-implementation will be changed because of a BIRT problem. It seems to me more likely, that BIRT is not compliant to the LiveConnect- or parsing-specification of JavaScript: Java Method Overloading and LiveConnect 3: http://www-archive.mozilla.org/js/liveconnect/lc3_method_overloading.html http://jdk6.java.net/plugin2/liveconnect/#OVERLOADED_METHODS Please reopen this issue.
Hey, BIRT is using Rhino as its javascript engine. BIRT itself will not do javascript evaluation job. Although the BIRT is java based, that not necessary means the script language used throughout the BIRT should be java. We use javascript because it is easy and popular. However, it is strange that report engine works fine while data set preview broken. Can you confirm that the report engine returns the correct value? Maybe that is because in your table you defined more data bindings than the number of column in data set, so that the index in your expression happen to locate some other columns? Thanks. Lin
Please use attached RPT-Design in Bug 375302: NumberAsColumnName.rptdesign (Attachment 213169 [details]) - Data Set Preview Results causes an ArrayIndexOutOfBoundsException. - The report preview with the same computed column works fine. BTW: The problem also exists on output columns with a "number" as name (like the string "43"). The "index" is always reduced by 1, leading to the exception message "42".
