- FireStorm is now compatible with Windows Vista
- An extra "Navigation" field has been added to the foreign key editor in the
user interface to allow users to control the direction of generated relationships when
generating EJB 3.0 / JPA source code. Valid values are "Unidirectional, Parent -> Child",
"Unidirectional, Child -> Parent", and "Bidirectional".
- The JDBC Driver and Data Source configuration have been re-implemented to improve usability.
- When defining Table Finders or Custom SQL DAOs, it is now possible to escape colon symbols
with the backslash '\' character to stop FireStorm from interpreting them as parameter names.
- Improvements have been made to the way in which FireStorm loads custom code generation providers
that have been developed using the Architect Edition of the product. It is no longer
necessary to specify the provider class names in the configuration file as FireStorm now
scans all jar files in the jars directory at startup and automatically attempts to load
any classes that implement the Provider interface.
- Java Data Objects (JDO) is no longer supported.
- FireStorm no longer offers the option of generating SQL scripts from the project file. Although
this was a potentially useful feature FireStorm is not intended to be a database design tool and
this feature was causing some instabilty in the core functionality due to the need to maintain
lists of supported sql types per platform (see notes related to bug 4876 below).
- The user interface no longer works with JDK 1.4. JDK 1.5 or later is now required.
- [4629] Firestorm did not correctly import table definitions from SQL/DDL scripts if
the PRIMARY KEY clause was specified directly in the column definition. Also the IDENTITY keyword
was not supported. This issue has now been resolved.
- [4690] It is now possible to specify the location of the Oracle JDBC driver jar file so that
the generated Ant build.xml file contains the correct classpath. Also, the generating import
statement for Oracle support has been changed from oracle.jdbc.driver.OracleTypes to
oracle.jdbc.OracleTypes to reflect the move from classes12.zip to ojdbc14.jar
- [4691] FireStorm was failing to correctly import DB2 databases due to "unsupported data type"
errors.
This issue has now been resolved.
- [4792] When generating Hibernate code, relationships now default to directional (not bi-directional)
many-to-one relationships from the child table to the parent table.
- [4795] When importing from JDBC, the jdbc catalog name was not being saved in the project
file, requiring the user to re-select the catalog name each time the project was synchronized
with JDBC. Also, this caused the user interface to prompt the user to save the file even if
no changes had been made. This issue has now been resolved.
- [4796] FireStorm was failing to correctly import tables that had multiple foreign keys that
referred to the same parent table (e.g. customer with shipping_address_id and
billing_address_id both referring to the same address table). Prior to this bug
being fixed, FireStorm would import a single foreign key rather than importing a
separate foreign key for each relationship. This issue has now been resolved.
- [4876] FireStorm was displaying validation errors such as "SQL Data type 'XXX' is
not supported by target database 'YYY' after importing a database schema. The cause
of this was that the list of supported data types in FireStorm was not complete. However,
rather than attempt to keep a comprehensive list of database platform data types in
the FireStorm code base the validation check has been removed. The data types have been
imported from the database so we can assume they are correct. Also, the SQL data type
names have no impact on generated Java code anyway so they are really just there for
informational purposes.
- [4880] Oracle 9i CLOB/BLOB types are no longer restricted to 8192 bytes when generating
JDBC DAO code.
- [4892] The foreign key swing table in the Table editor now shows the correct column list for
each key rather than 'TBD'.
- [4933] When importing form a SQL/DDL script, foreign key declarations that provided a constraint
name where not imported. For example "ALTER TABLE customer ADD FOREIGN KEY customer_billing_address
(billing_address) REFERENCES address (id)" was failing because the DDL parser did not expect the
constraint name 'customer_billing_address' but expected the column list. This issue has now been resolved.
- [4947] The JDBC DAO code generator was generating incorrect update() methods for Oracle when
CLOB/BLOB types are used and the 'Generate Dynamic UPDATE' option was not selected. The error
was due to a mismatch between the SQL and the number of bind parameters. This issue has now been resolved.
- [5102] Resolved "Failed to clone project" error.
- [5104] Fixed error with support for reading Oracle LONG RAW data type in JDBC DAO code. The AbstractDAO
base class, which is generated based on a template, has been updated to specifically check for this
data type and then call the JDBC getBytes method rather than getBlob.
- [5117] When generating a J2EE web application and targetting JBoss, the web.xml correctly only
contained a JNDI resource-ref it the JNDI option was selected during code generation (as oppoosed
to hard-coded JDBC details). However, the generated JBoss jboss-web.xml always contained the JNDI
name even if the JNDI option was not selected. This resulted in a deployment error if JNDI was
not selected. This issue has now been resolved.
- [5138] A bug introduced in an earlier 3.2 beta caused Custom SQL JDBC DAOs to be
generated with references to incorrect class names. This issue has now been resolved.
- [5445] The generated DAO Factory no longer uses a static instance variable for caching DAO
the instance and the create() method now always returns a new DAO instance. This functionality
was changed to resolve a thread-safety issue reported by a customer.
- [5446] When generating JDBC DAO code that uses dynamic updates,
the generated code now resets the modified flag when populating a DTO from the database.
- [5503] When generating JDBC DAO code that uses dynamic inserts,
the generated code now correctly handles Oracle BLOB/CLOB data types.
- [5542] The dialogs for configuring JDBC drivers and data sources were quite buggy. These
dialogs have been re-implemented using a simpler design.
- [5588] When generating code for Custom SQL JDBC DAOs, the findByDynamicWhere method was
not implemented correctly. This issue has now been resolved.
- [5607] FireStorm was failing to generating the correct import statements when
generating JDBC DAOs if a DAO had finders with parameters of type java.math.BigDecimal
and where the DAO did not have any columns defined with that type. This issue has
now been resolved.
- [5652] When reverse engineering Oracle SQL scripts, foreign keys defined within the
create table (...) syntax were not detected correctly. This issue has now been resolved.
- [6627] Incorrect code was generated for EJB 2.1 entity beans. This issue has now been resolved.
- [6403] Incorrect catalog/schema prefix generated in JDBC DAO getTableName when generating
code for Sybase. This issue has now been resolved.
- [6459] JDBC Table DAO code now includes import for java.sql.Types, which has recently beeen
removed and caused compilation errors.
|
