i-net Crystal-Clear

Changes in Release 6.5.52

i-net Crystal-Clear runtime

New features

  • Following JDBC drivers bundled with i-net Crystal-Clear. These driver versions are unlimited with i-net Crystal-Clear, only.
    • i-net SPRINTA (MS SQL Server)
    • i-net SERO (Oracle)
    • i-net SYTO (Sybase)
    • i-net ENTWO2 (DB2)
    • i-net FOSITEX (CSV files).
  • New formula functions:
    • “properCase” - returns the original string where the first character of each word are upper case and the others lower case.
    • “bytesFromFile” - returns the content of a file addressed with a path or URL as binary data. (Can be used for loading pictures.)
    • “translate” - with this function the LanguageResource ResourceBundle can be used to translate strings inside of formulas.
    • “LBound” - returns the lower bound of an array.
    • “IsArray” - returns if the passed object is an array.
    • “Debug” - with this function it is possible to add a text to the log file in log level DEBUG.
    • “Escape” - URL encoding the passed string.
    • “Unescape” - URL decoding the passed string.
    • “ServerName” - returns the http server name i-net Crystal-Clear is running on. (e.g.”http://localhost”)
    • “IndexOf” - returns the position of the first occurrence of a string within another string.
    • “DefaultCurrencySymbol” - returns the default locale's currency symbol, i.e. “$”, “€”, etc.
    • ContentLocale - returns the locale of the server.
    • DataTimeZone - returns the time zone of the datatime.
    • PrintTimeZone - returns the time zone of the printtime.
  • New special fields:
    • Content Locale - displays the locale of the server.
    • Data Time Zone - displays the time zone of the datatime.
    • Print Time Zone - displays the time zone of the printtime.
  • Sort direction of sort fields and/or groups can be defined by a formula.
  • Hierarchical grouping with original sort order.
  • The cross-tab option vertical wrap now supported. It allows to change the wrapping behavior of the cross-tab, if it doesn't fit in the page width.
  • A general way to add Java libraries to i-net Crystal-Clear with crystalclear.properties file property “libDirectory”.
  • Report file extension can map to the file format. This means Report1.pdf in the browser URL is equals to Report1.rpt&init=pdf. This is valid for the following file extensions pdf, htm,, rtf, xls, svg, csv, txt, ps, ps2 and ps3.
  • New bitwise operators for numbers in formulas: “and” and “or” used for two numbers now act as bit-wise operators, that is: “5 and 2” → 0, “5 or 2” → 7.
  • XLS Export: Hyperlinks.
  • PDF, RTF, HTM and XLS export: sub-report on demand as hyperlinks now supported (init=… only, not Java viewer).
  • PDF Export: Symbol font (e.g.S) now supported. Characters encoded in Symbol (font-specific) encoding will be written with Adobe Type1 font Symbol. Many special characters and Greek characters encoded in Unicode, that don't belong to Latin character set, will be written with Type1 font Symbol too.
  • RTF export: Unicode characters can be displayed in charts now, because charts are written in emf - format instead of wmf.
  • Extended Interface for picture and database picture elements with various new options (e.g.: stretch to frame while keeping the aspect ratio).
  • Report property “Hide the page footer inside the report header”.
  • Page Footer: It is now supported to suppress the page footer dynamic on a formula, depending on the current row. But, it is not supported if “Print At Bottom of Page” is true for a section.
  • Java viewer: Arabic fonts with right to left direction supported.
  • Keep Together for areas supported (version 6.5.05).
  • TXT Export: “Page N of M” and TotalPageCount supported (version 6.5.16).

Fixed bugs

  • Column which used only by Sorts, Record Selection Formula or Join condition will be ignored by distinct.
  • JavaBean: The JavaBean was not displayed if the database field, on that it was designed, was not used in the report expecting the JavaBean.
  • Database Connection:
    • Oracle database: Overwriting package information with Datasource.setCatalog() or report URL property “catalog” will have effect now.
    • Bug with Joins since version 6.1: A join have one column linked to multiple columns to an other table.
    • A failover will now be done if a corrupt connection will be detected (the sqlstate “08S01” will be checked). The corrupt connection will be closed and the execute of the statement will be tried again.
    • SQL commands using PromptField values: String values will be quoted automatically now.
    • Because of a wrong or not set catalog name to database Connection object meta data requests to sybase (and other) driver didn't return expected information of stored procedures or tables.
    • Engine.setData() implicitly tried to create a Connection.
    • Stored procedure(SP) didn't used set parameter if report contained further tables before adding the SP. Because this problem was in report template file, old reports still won't work.
    • Stored procedures could not be used with Interbase databases when using the Interbase JDBC driver version 4.5.x.
    • Calling Datasource.setDatabase() with an own Database class did not work. If the report was executed the designed connection of the report was used.
    • Multi value prompts used in record selection formula with ”=” operator were transformed to wrong SQL. The ”=” operator did not changed to “IN” operator (fixed in version 6.5.02).
    • Multi value prompts used in record selection formula with “isnull()” function has not been evaluated before SQL statement was created. Therefore an SQL statement with invalid syntax was created (fixed in version 6.5.02).
    • SQL statement will not be executed without Where clause, if an OutOfMemoryError has occurred during execution with Where clause (supported in version 6.5.02).
    • If a Database class was set before report execution, it won't be attempt to create an instance of Database class defined in crystalclear.properties file. This solves a problem, if defined class couldn't instantiated but was set via API (fixed in version 6.5.08).
    • Blob images not displayed correctly for some JDBC drivers (fixed in 6.5.16).
    • A refresh of a stored procedure could be not successful if the stored procedure could not handle NULL values passed for the parameters. (fixed in 6.5.16)
    • A JDBC driver was not used if it had thrown an SQLException at DatabaseMetaData.getDatabaseProductVersion() and DatabaseMetaData.getProductName() (fixed in 6.5.17)
    • A refresh of a stored procedure did not refresh the value type of prompts used as parameter for the stored procedure (fixed in 6.5.19)
    • A refresh could not be done on a table/ stored procedure provided by an own com.inet.report.Database class implementation (when not using JDBC drivers) (fixed in 6.5.19).
    • A stored procedure of MySQL database could have returned scrambled data because of a bug of the MySQL JConnector (fixed in 6.5.22).
    • Using Engine.setSql() or the URL parameter sql could have failed if the sql statement contained a german “ß” (fixed in 6.5.25).
    • Using Engine.setSql() or the URL parameter sql did not work with an Oracle statement starting with WITH clause (fixed in 6.5.25).
    • Using Engine.setSql() with a call of a stored procedure did not work correctly. (fixed in 6.5.26)
  • HTML Text interpretation: Newlines and tabs are handled like spaces now. Before they were ignored.
  • If setData was used for a sub report and no DLL name was set, then the data was lost.
  • RTF export: The cross-tab border was not displayed.
  • RTF, HTML, XLS, CSV, Data export: A bug with “Manual Formatting” has been fixed.
  • The default PropertiesChecker named “PropertyChecker” was not found, if it was not specified in crystalclear.properties.
  • The ReportReader.exe writes the font names in Unicode. Now it is possible to execute reports that contains Chinese font names and that were designed with Crystal Reports 9 (or higher).
  • A bug with the servlet remote interface has been fixed. Now, it is possible (again) to send an engine with data from a client with the post command to the i-net Crystal-Clear servlet and receive the executed report as answer from the servlet on the same client.
  • A bug with the group on a date column with sort order “original” has been fixed.
  • Various layout problems:
    • Justified text had various rare bugs, such as when the element's width was very small.
    • Font problems of highlighting wrong text parts.
    • Various problems with layout of multiple HTML-interpreted elements after page breaks.
    • Sizing of lines: Lines used to have the height of the following line, now they have the correct height.
    • Line breaks in labels and fields used to be ignored in CSV export, now they are interpreted as spaces.
    • “Allow Field Clipping” had some rare clipping issues where text parts could be skipped.
    • Rare cases of wrong clipping or shifting right-aligned text.
    • Rare cases of showing blank lines when there were none.
    • Rare cases of suppressing blank lines when they should not have been.
  • A cross-tab page break bug since version 6.0 has been fixed.
  • Various unnecessary warnings were shown in the Visual Database Wizard when the connection was incorrect, these have been removed or fixed.
  • A bug that RDC.loadEngine(File, BufferedReader) caused an InternalError when the passed File object was null.
  • A bug that Element.setManualFormatFormula() did not set the property formula correctly so that the report could not be saved.
  • RTF-Export: Blobs (in wmf-format) are now displayed in the width and height of the image element.
  • The formula operator “or” had an identical priority to “and”: “true OR true AND false” used to return “false”, now it correctly returns “true”.
  • The formula functions and summary types “correlation” and “covariance” had rare cases of miscalculation on running total fields.
  • Adding a number to a date was not optimized correctly when it was done in record selection formulas.
  • Deleting a stored procedure using stored procedure parameters did not remove the reference to the prompt field.
  • com.inet.report.Field.indexOf() did not work properly.
  • Java Viewer: Printing problem with Java 5.0 has occurred if the report was designed in landscape orientation. The report was printed in portrait.
  • The min range property for prompt fields were not read for reports of Crystal Reports 9 or higher.
  • The summary info read from report of Crystal Reports 9 or higher could be corrupt.
  • If dynamic (suppressed) page footer sections are used, it could occur that the page footer section was overwritten by a detail or other section.
  • RTF text interpretation: Font specified in rtf text was not used.
  • Charts: Wrong types of “Area Charts” in reports that were designed with Crystal Reports 9 (or higher).
  • There was a rare endless loop in certain formulas using wrong Basic syntax.
  • Prompt values have not been requested after Drill-Down.
  • The function Engine.setData for sub-reports works now correctly.
  • The positional notation of number labels on the y-axis of the Chart.
  • PDF export: Dynamic images were cached unnecessarily. To reduce OutOfMemoryErrors this caching has been removed.
  • XLS export: Because of a bug with sub-reports, it could be that a field get lost in the created xls file (fixed in version 6.5.01).
  • Report data has going out of the page footer section (fixed in version 6.5.02).
  • The calculation of the page footer height has ignored the property “Underlay Following Section” for page footer sections (fixed in version 6.5.02).
  • Sub-reports on demand: If a database field was used in the property formula for “On demand Label” and/or “On demand Tab Label”, only, then this database field has not been added to the Select statement and therefore the content has not been displayed in the report at runtime (fixed in version 6.5.03).
  • An endless loop and OutOfMemoryError has occurred if “Keep Together” was enabled for 2 groups, “Repeat Group Header” was enabled for the first group and
    the height of a detail section was greater than page height (fixed in 6.5.04).
  • An empty “BySummary” has occurred (fixed in 6.5.04).
  • PDF export: OutOfMemory-Error has occurred in some cases if Chinese TrueTypeFonts was used for font embedding (fixed in 6.5.06).
  • An additional empty page was displayed if “Print At Bottom of Page” was enabled for the report header section and the page header area has contained more than 2 page header sections (fixed in 6.5.06).
  • CSV Export (data only): Exception has occurred if the exported csv file was used as datasource for a report because the column names has contained a ”.”. This ”.” will be replaced by an underline character “_” in version 6.5.06.
  • Java Viewer: An error dialog was displayed also if method exportView was called with throwException =true (fixed in 6.5.06).
  • The group number was not reset for sub-reports (fixed in 6.5.06).
  • Various problems with multi-value prompts (fixed in 6.5.07).
  • A problem with Minimum or Maximum being used on non-number arrays or multi-value prompts (fixed in 6.5.07).
  • Array concatenation: “a” + [“b”,”c”] + “d” now returns as [“a”,”b”,”c”,”d”] (fixed in 6.5.07).
  • User defined formulas (e.g. with Object[] as parameter) could not be executed. (fixed in 6.5.07).
  • A synchronized problem with the hard disk cache has occurred, if a lot of threads were used (fixed in 6.5.07).
  • The stored procedure parameters have not been refreshed correctly (fixed in 6.5.07).
  • User defined formulas with NULL as parameter values could not be executed. (fixed in 6.5.08).
  • Java Viewer: Bug with JDK 1.1.x compatible Java VM (e.g. Microsoft JVM) has occurred (fixed in 6.5.09).
  • MultiColumn Report: Vertical line not appearing in the second column if they started in the first column (fixed in 6.5.09).
  • Last page footer section was not displayed if another section of the page footer area has been grown.
    “Can Grow” for page footer sections will be ignored (since version 6.5.09).
  • ClassCastException during formula optimization if the field was unknown (fixed in 6.5.09).
  • “Broken Subreport Link” exception has occurred if a formula was build on a sub-report formula that was used for this sub-report link, only (fixed in 6.5.09).
  • ClassCastException occurring under some circumstances when printing. (fixed in 6.5.10).
  • HTML Text Interpretation: Headings H1 - H6 not bold (fixed in 6.5.10).
  • “New Page After” in sub-report and in main report has produced wrong results (fixed in 6.5.11).
  • Problem with Engine.setConnection has occurred if the catalog of a database object (e.g. Oracle stored proc in package) has been changed (fixed in 6.5.12).
  • Problem with OrderBy formula has been fixed in 6.5.12.
  • Wrong height of section was used in sub-reports (fixed in 6.5.12).
  • Bugs have occurred if a cross-tab was used in a sub-report (fixed in 6.5.14).
  • No exception was thrown if an image could not be loaded successfully (fixed in 6.5.14).
  • Report files designed with version 5.x was not opened and executed correctly in version 6.5.x (fixed in 6.5.14).
  • Bug in converting the record selection formula to a SELECT statement when using boolean constants “true” and “false” in combination with prompt fields (fixed in 6.5.15).
  • Bug has occurred if the start section of a line was suppressed (fixed in 6.5.15).
  • Field with Barcode font was not displayed correctly in the Java viewer, if Java viewer was running in JDK 1.1.x and value of the property “useNativeFonts” was false (fixed in 6.5.15).
  • Blob images not displayed correctly for some JDBC drivers (fixed in 6.5.16).
  • The property formula for text interpretation was not evaluated correctly so that the content of the field could be misinterpreted (fixed in 6.5.16).
  • A sub-report was printed with wrong page orientation (fixed in 6.5.16).
  • Java Viewer API: exportView(toHTML_SINGLE_PAGE , …) has created one file per report page instead of one file for the complete report (fixed in 6.5.16).
  • PDF export: TrueType-Fonts with the word “Regular” at the end of the name was not embedded successfully because Windows has displayed the font name without the word “Regular” (fixed in 6.5.16).
  • Crosstab: The feature “Suppress Empty Rows” has not worked under some conditions (fixed in 6.5.16).
  • Endless loop in cross-tab has occurred (fixed in 6.5.16).
  • Java Viewer: Problem with hanging Java Viewer if method printView(PrintJob) was used and the report contains right aligned text (fixed in 6.5.18).
  • XLS export: The property “reverse sign for display” was not regarded (fixed in 6.5.19).
  • CSV export: Bug has occurred if strings like: “Hello” (with quotes) was used in the report exported in a csv file (fixed in 6.5.20).
  • PDF export: Bug with totalpagecount in subreports has been fixed. It has produced corrupt pdf files (fixed in 6.5.20).
  • Database / Harddisk cache: Deadlocks fixed (fixed in 6.5.21).
  • ReportReader.exe: All Formula Fields Became Numeric Type (fixed in 6.5.21).
  • Keep Together for areas in subreports has not worked if area was greater than one page (fixed in 6.5.21).
  • HTM export: Semicolon was missing after ”&nbsp” (fixed in 6.5.22).
  • Formula functions: NullPointerExceptions have occurred if null was passed as parameter value (fixed in 6.5.22).
  • Java viewer: Landscape Printing with Java SE 6 failed. First page was printed in portrait orientation (fixed in 6.5.22).
  • Java viewer: The alignment of numeric columns with right alignment was incorrect (fixed in 6.5.22).
  • PDF export: The thick of lines was different if TTF font embedding was used or not (fixed in 6.5.23).
  • Listener.stop() did not stop all threads (fixed in 6.5.23).
  • TXT export: Font name and font size can be specified in crystalclear.properties (supported in 6.5.23).
  • PostgreSQL: Problems with the case sensitivity of alias names occurred (fixed in 6.5.23).
  • XLS export: Numbers was not rounded according to settings in i-net DesignerXML (fixed in 6.5.24).
  • XLS export: Default null format in custom number format was not set (fixed in 6.5.24).
  • XLS export: Sub report on demand was handled like a normal sub report (fixed in 6.5.25).
  • PDF export: Same pictures are duplicated in exported pdf file (fixed in 6.5.25).
  • Encoded URL properties in a servlet environment were not decoded properly. E.g. the encoded plus sign ”+” (encoded: ”%2B”) was decoded to space character ” ”. (fixed in 6.5.26)
  • An OutOfMemoryError occurring because Delfater instances for compression were not closed properly has been fixed (fixed in 6.5.26).
  • SSL has not worked with ISAPI (fixed in 6.5.27).
  • Due to a bug in version 6.5 rendering of WMF encoded images produced poor quality outputs (fixed in 6.5.27).
  • If i-net Crystal-Clear cluster and database cache was used, database cache was not reconnected after a database shutdown (fixed in 6.5.27).
  • Formula function 'min' produced error results if there are some records with NULL (fixed in 6.5.28).
  • Right aligned text was truncated on the right side of the field (fixed in 6.5.29).
  • Line charts: Legend contains wrong values (fixed in 6.5.29).
  • Cross-Tab in the page footer of a sub report now displayed (fixed in 6.5.30).
    (Bug can occur in versions 7.0 - 7.3 also).
  • Multiple dead locks in the cache (memory, hard disk, database) has been fixed by restructuring of the synchronized methods in the cache (fixed in 6.5.31).
    (Bug can occur in versions 7.0 - 7.3 also).
  • JavaBeans: Bug occurred if the width and height of a Java Bean was 0 (fixed in 6.5.32).
  • Report viewer freezing while checkProperties method is running for a very long time (fixed in 6.5.33).
    (Bug can occur in versions 7.0 - 7.5 also).
  • Issue with bar charts display multiple group entries (fixed in 6.5.34).
  • RTF text interpretation did not work if an ANSI codepage should be used but no codepage was specified. (fixed in 6.5.35).
    (Bug can occur in versions 7.0 - 7.5 also).
  • Function: DistinctCount returned 1 instead of 0 if the summarized field contained multiple Null values. Also, the performance of the distinct count function was improved (fixed in 6.5.37).
    (Bug can occur in versions 7.0 - 7.6 also).
  • Crosstab calculates its maximum height on the first page of its appearance and use this value for every following page (fixed in 6.5.38).
    (Bug can occur in versions 7.0 - 7.7 also).
  • Formula behavior was greatly optimized for reports with many formulas referencing each other. (fixed in 6.5.39).
    (Bug can occur in versions 7.0 - 7.7 also).
  • Text export: It could occur that some labels are missing in mailing label or multi column reports if one or more section suppressed (fixed in 6.5.40).
    (Bug can occur in versions 7.0 - 7.8 also).
  • Exceptions with cascaded if-then-else-statements in Basic formulas has occurred (fixed in 6.5.41).
    (Bug can occur in versions 7.0 - 7.9.01 also).
  • The last elseif block in basic syntax formulas was ignored if it was not followed by an else block (fixed in version 6.5.42).
    (Bug can occur in versions 7.0 - 7.9.02 also).
  • OutOfMemoryError occurred if “Suppress report if no rows” was enabled for the report and “Suppress Blank Section” was enabled for the section
    containing a sub-report (fixed in version 6.5.43).
    (Bug can occur in versions 7.x also).
  • RTF Export: “Page Setup” dialog in MS Word is disabled for rtf export. Empty paragraph added to the end of the rtf file so that it is possible to open the “Page Setup” dialog (fixed in version 6.5.44).
    (Bug can occur in versions 7.x also). 
  • Endless Loop occurred if section properties “Print At Bottom of Page” and “Suppress Blank Section” was used in combination with sections spanning multiple pages (fixed in version 6.5.44).
    (Bug can occur in versions 7.x also).
  • A problem with variable declaration causing a “VariableAlreadyDefined” error has occurred (fixed in version 6.5.45).
    (Bug can occur in versions 7.x also).
  • It has occurred that database connections that was set using API were not closed after parameter fields has been requested from the Java viewer (fixed in version 6.5.46).
    (Bug can occur in versions 7.x also).
  • Database connections in sub-reports that has been set using API were not closed after parameter fields were requested (fixed in version 6.5.47).
    (Bug can occur in versions 7.x also).
  • Sometimes Polish language was displayed wrong if text interpretation “Rich Text” was used (fixed in version 6.5.48).
    (Bug can occur in versions 7.x also).
  • Sometimes a section disappeared if the Page Footer section was suppressed depending on a formula (fixed in version 6.5.49).
    (Bug can occur in versions 7.x and 8.x also).
  • NullPointerException occurred while using SQL Expression editor (fixed in version 6.5.50).
    (Bug can occur in versions 7.x and 8.x also).
  • OutOfMemoryError occurred if embedded fonts was used and separate .ttf file was used for bold font, e.g. timesbd.ttf (fixed in version 6.5.51).
    (Bug can occur in versions 7.x and 8.x also).

Behavior Change

  • Database Connection:
    •  To reduce memory usage of using stored procedures and sql commands, columns not used in report design will not be read.

API changes

  • class TableSource, additional methods:
    • refresh() - refreshes the information about columns and stored procedure parameter
    • setInputParameter(String[] , int[], Object[]) - defines input parameter for stored procedure and sets data for refresh and execute
    • setInputParameter_TypesOfSQLType(String[] , int[]) - defines input parameter for stored procedure, parameter type is of sql type
    • setInputParameter_TypesOfSQLType(String[] , int[], Object[]) - defines input parameter for stored procedure and sets data for refresh and execute. The set parameter type is of sql type.
  • class JavaBean, additional methods:
    • getBeanPropertyFormula(String)
    • getBeanPropertyValue(String)
  • class RDC, additional method:
    • getClassLoader() - this ClassLoader contains all libraries set with “libDirectory” and “driverLibrary” property
  • class Fields, additional method:
    • addSortField (Field field, FormulaField formula) - adds a new SortField with a formula for sort direction
  • class SortField, additional method:
    • setSortDirectionFormula(FormulaField formula) -sets a sort direction formula for current SortField
    • getSortDirectionFormula() - gets sort direction formula
    • removeSortDirectionFormula() - removes sort direction formula
  • class Group, additional method:
    • setGroupDirectionFormula(FormulaField formula) - sets a sort direction formula for current group
    • getGroupDirectionFormula() - gets sort direction formula
    • removeGroupDirectionFormula() - removes sort direction formula
  • class ReportProperties, additional method:
    • setHidePageFooterInsideReportHeader(boolean)
    • getHidePageFooterInsideReportHeader()
  • class PromptField, additional method:
    • getTableSources() - returns the TableSource objects of views and/or stored procedures if the prompt field is used as parameter for one or more database objects

i-net DesignerXML

New features

  • The special fields are now displayed in two groups: “Report” and “Print”.
  • Cache of i-net Crystal-Clear won't be started. This saves system resources.
  • Reports can now be executed based on previously created core files.
  • JBuilder plug-in: File Chooser Dialog for designing of a new report implemented.

Fixed bugs

  • A bug that the properties of a JavaBean could be lost when edited them the first time and then changed something different in the report.
  • A bug in the group dialog which changed the sort order to “ascending” when using hierarchical grouping with “descending” or “original” sort order.
  • A bug that only one sort field could be deleted in the sort records dialog.
  • A bug that the properties dialogs could not be used when using an own DesignerDataModel but not implementing the “editPropertiesDialog” method.
  • A bug that the font size was reduced by changing the unit in which the size is shown.
  • The various bugs in “Summary Field Properties”.
  • The driver libraries are now available in embedded modus too.
  • A bug that the reference of fields were not shown properly.
  • JBuilder plug-in:
    • Creating a new report with the same name as an existing report results into two file nodes in current project, but the same report file for both nodes.
    • A report node designed with full absolute path caused FileNotFoundException.
  • Eclipse plug-in: A bug with empty “Database Wizard” has been fixed.
  • A bug with empty DatabaseWizard executed in Eclipse plug-in.
  • JBuilder & Eclipse plug-in: Reports created with Crystal Reports 9 (or higher) could not be opened successfully.
  • Empty text parts in a text field has been removed, e.g. white spaces between embedded fields (fixed in 6.5.04).
  • Default value for the cross-tab property 'Vertical Wrap' has not been saved (fixed in 6.5.07).
  • i-net DesignerXML could crash with an OutOfMemoryError if run with an account of group “Users” and not “Power Users” or “Administrators” (fixed in 6.5.16).
  • Font size in the toolbar could not be entered as floating point number (fixed in 6.5.18).
  • The property formula for the decimal separator symbol could not be set (fixed in 6.5.19).
  • Elements could have been copied when moving them with pressed Ctrl key (fixed in 6.5.19).
  • No system libraries could have been added to i-net DesignerXML (fixed in 6.5.24).
  • Some keywords, like “WITH”, not allowed for commands (fixed in 6.5.36).
    (Bug can occur in versions 7.0 - 7.6 also).
  • StackOverFlowError occurred during start of i-net DesignerXML with Java 6 on Windows 7 (fixed in version 6.5.52).
    (Bug can occur in versions 7.0 - 7.6 also).

API changes

  • class EmbeddedUtils, additional methods:
    • addFileToLastOpened(File) - adds a file to the menu last opened file so that a file can be re-opened easily
    • addToClasspath(String) - adds a jar file specified by an URL or a path to the classpath of i-net DesignerXML
    • setDefaultPageLayout(Engine) - sets the default page layout loaded from the i-net DesignerXML registry to the given Engine object.
  • interface DesignerDataModel, additional methods:
    • isOpenDriverLibrariesAllowed() and setOpenDriverLibrariesAllowed() - the driver libraries dialog can be enabled/disabled with these methods

i-net SchedulerXML

Fixed bugs

  • The execution date of a task was sometimes wrong (one week later) if a weekly interval was used.
  • An infinite loop occurring when using PrintAction while running i-net Crystal-Clear with a local system account (e.g. as NT service).
  • A bug that HTML export did not work properly for EmailAction and FileAction.
  • The subject and the text body of the email sent by the EmailAction will now be encoded with UTF-8.
  • A report definition for a task could get unreachable because of quotes around the path to a report template.
  • A NullPointerException occurring when pressing “show log file” in the web configuration tool.
  • When pressing “show log file” and using a scheduler log file then the log messages written after this step overwrote the messages created before.
  • The DynamicProperties class set for a report using the API could not be restored from the xml file and so was lost.
  • i-net SchedulerXML can now work together with ClusterCache.
  • An extremely rare case of an endless loop. Occurred only with weekly execution.
  • A case of an unhandled ArrayIndexOutOfBoundsException that could occur with monthly execution.
  • Delete button for reports will work now also if special characters was set for report configuration name.
  • A NullPointerException occurred for an EmailAction if generated reports should be added to a zip archive but no reports could be executed successfully. (Fixed in 6.5.17)
  • Zip archives attached to an email sent by the EmailAction could be corrupt. (Fixed in 6.5.17)
  • Files attached to an email sent by the EmailAction could contain relative path information for some email clients. (Fixed in 6.5.18)

i-net Crystal-Clear Setup

New features

  • The components are now arranged in a component tree.
  • The included JDBC drivers and JavaBeans can be selected in the component tree.

Fixed bugs

  • Chinese characters were incorrectly displayed in the uninstaller.
  • Shortcuts were created in a wrong directory if the i-net DesignerXML was installed on a Chinese server.
  • Check for available memory has been failed on Linux sometimes (fixed in 6.5.14).
  • Bug with PHP5 on Linux/Unix occurred (fixed in 6.5.24).
Documentation Sitemap

i-net software strives to provide accurate product documentation. Please give us your feedback using the form below.
NOTE: This form is for documentation feedback only. For technical assistance, please send an email to crystalclear@inetsoftware.de.

 

© Copyright 1996 - 2010, i-net software; All Rights Reserved.