FireStorm/DAO 2.2 RC1 - Updated Build
A new build (build 115) has just been posted to the web site. This fixes a problem with the new "Generate Dynamic Update Method" feature (Enterprise Edition only).
« June 2004 | Main | August 2004 »
A new build (build 115) has just been posted to the web site. This fixes a problem with the new "Generate Dynamic Update Method" feature (Enterprise Edition only).
CodeFutures is pleased to announce the availability of FireStorm/DAO Release
Candidate 1.
FireStorm/DAO 2.2 RC1 provides Struts-based JSP client generation, DAO
generation from partial DB schemas, enhanced automated build system support,
optimized JDBC code generation, dynamic update methods, and extended SOA
support.
You can find full details of the new features here:
http://www.codefutures.com/library/CodeFuturesFireStormDAOrelease22.PDF
FireStorm/DAO 2.2 RC1 is available for immediate download and free
evaluation from:
http://www.codefutures.com/products/firestorm/download/
Current FireStorm/DAO Enterprise Edition customers may use their existing
license for unrestricted access to all of the new features and
functionality.
The Struts and generation from partial DB schema functionality is restricted
by the evaluation license key.
Regards
Andy Grove
Chief Technology Officer
Code Futures, Ltd.
A new build of FireStorm/DAO 2.2 BETA is now available to download from:
http://www.codefutures.com/products/firestorm/download/
This latest build now included the ability to import a partial schema i.e. during the import process you choose which tables and views you want to import. Please note that this feature is not available in the evaluation version and is an Enterprise Edition feature.
FireStorm/DAO 2.3 will add full support for stored procedures but it is possible to call stored procedures using the current Custom DAO support. There are some restrictions using this approach (most notably the lack of support for INOUT or OUT parameters and support for REFCURSOR types).
If you want to call stored procedures that return no results you can use this syntax within the Custom DAO definition:
BEGIN ADD_JOB_HISTORY(:empId, :startDate, :endDate, :jobId, :deptId); END;
Small update from build 84 ..
The generated JDBC DAO implementation code now only prefixes variable names with underscores in methods where name clashes are possible. This makes the code look a lot cleaner.
The new concise finder methods now handle java.sql.Date, java.sql.Time, and java.sql.Timestamp more elegantly.
Latest BETA build has just been uploaded. This release contains a number of minor bug fixes and enhancements.
One of the largest changes is that the generated JDBC code in the DAO implementation classes is much more concise within the finder methods. The code is now closer to human-authored code (which should always be the goal of any good code generator).
Other changes include:
FireStorm/DAO is supported on Mac OS X (as well as Windows and Linux) and one of our customers has just reported a useful tip - the copy and paste functionality when running on Mac is mapped to the ctrl-c keyboard shortcut rather than the apple-c shortcut.
A couple of tips for users who want to keep their generated code under source control.
1. Preserving CVS files
When FireStorm/DAO 2.1 deletes an output directory before generating code it does not delete CVS directories (as long as the appropriate option is selected in the GUI). However, this release did delete .cvsignore files, making it very difficult to exclude any of the generated code from CVS. FireStorm/DAO 2.2 fixes this issue and does not delete .cvsignore files
2. Timestamps in headers cause conflicts
If you generate DAO code on multiple machines you are likely to get conflicts when commiting to CVS due to the timestamps in the javadoc file header not matching. It is a good idea to customise the file header so that it doesn't write the date or time.