FireStorm/DAO 2.0.5
FireStorm/DAO 2.0.5 is now available to download. There is now a single download which provides functionality for the Standard, Enterprise, and Architect editions depending on the license key being used.
The changelog taken from the README is as follows:
Changes between 2.0.4 and 2.0.5
- Automatic renaming of reserved words
- Database node in tree view now has context menu for importing schemas
- There is now a single distribution kit for all editions (Standard, Enterprise, Architect)
- Architect Edition source code now compiles against the release kit
- The JDBC option "use schema prefix" is now correctly applied to sequence names
- A prominent message is now displayed when the evaluation license restriction is reached
Changes between 2.0.3 and 2.0.4
- Generated ejb-jar.xml now uses CDATA encoding for EJBQL queries
- Fixed bug with CMP finders with multiple parameters
- Fixed bug that caused datasource name to always default to 'mydatasource'
- Fixed bug from 2.0.2 in generated equals() method in PK/DTO classes
- Fixed bug from 2.0.3 where vendor-specific EJB deployment descriptors were not generated
- Renamed DTO factory method in CMP EJB to createXxxx instead of getXxxx to avoid name clashes
- Architect Edition now ships with working example source
Changes between 2.0.2 and 2.0.3
- Improve message if no valid license found
- Generates correct EJB code for auto-increment support in JBoss
- Fixed bug in ejbCreate() where only pk fields were being set
- Added validation that primary key finders must exist before generating code
- Token replacement of @date@ and @time@ in java file headers now works
- PK property sheet improved
- FK property sheet improved
- Table Finder property sheet improved
- README format improved
- Added short-cut mnemonics to menu items in "Generate" menu
Changes between 2.0.1 and 2.0.2
- SQL script generator now generates the correct SQL syntax when using projects based on MySQL database schemas
- Support for java.sql.Clob Java type
- SQL Server IDENTITY support now working
- SQL Server schema name prefix bug fixed (now uses schema..table instead of schema.table)
- ANT tasks working again (obfuscation error in 2.0.1)
- New feature - customizable templates for file header in generated code
- Fix token-replacement problem with product.edition in README.HTML
- Fixed bug in generated equals() method in DTOs
- SQL Server datatype improved support (NVARCHAR, SMALLDATETIME, UNIQUEIDENTITY)
Changes between 2.0 and 2.0.1
- Generated code has re-usable methods for common operations (such as fetching results) making the code far closer to human-authored code
- Generated code also includes comments and only has import statements that are needed, again making the code appear to be human-authored.
- There is now an option to control whether the SQL statements should include the schema name or not.
- DAO implementation now has findBySqlSelect and findBySqlWhere for greater control over the SQL that is executed for finder methods.
- Bugs in Linux script (firestorm.sh) have been fixed.
- Fixed Linux font issues
- New and improved GUI look-and-feel
- Oracle CLOB columns are now correctly recognized when importing from JDBC
- Project file format has changed slightly so that code-generation options are stored as key-value pairs making it feasible to have a consistent XSD for all code generator plug-ins (including user-defined code generators with the Architect edition).
- It is now possible to specify the name of the generated JAR file in the project file