| Title | Description |
| New servlet component |
Servlets can now be defined in the JCodeBox web tier |
| New text component |
Text components allow you to define text based files for inclusion in your web application
i.e. you can define HTML pages as text components. |
| New resource component |
Resource components allow you to select files/resources on your local system for inclusion
in your web application i.e. you can select a local image file to be used in your web app. |
| New web styles |
Web styles allow you to optionally apply a pre-defined style to your web application. The
style will govern how your web application operates at runtime. Further details on available
web styles can be found in the JCodeBox knowledge base. Web styles are optional and if you
prefer, you can switch off the web style and design your web application from scratch. |
| Editable web.xml |
The web.xml for your web application can now be edited in JCodeBox. |
| Dynamic application name |
The application name displayed on system generated JSP is no longer hardwired into the
JSPs. It is set in the initialization method of the front servlet (controller) and stored in
an application variable for retrieval by JSPs. |
| User definable colors |
The colors for generated web applications can now be changed via JCodeBox system options. |
| Paths for JSP and other components |
Paths can be set for JSP, text and resource components allowing you further flexibility
in defining your web application. |
| Code template editor |
A code template editor allows you to edit the JCodeBox templates from
within the JCodeBox environment. JCodeBox templates are written in XSL. |
| CLOB/BLOB support |
Support for the CLOB and BLOB datatypes has been added. Please note however that CMP usage
is dependant on application server support. |
| Autocode entity SQL |
The autocoder can insert SQL statements based on the selected entity directly into your
code. |
| Tomcat deployment enhancements |
Tomcat deployment has been enhanced to use the Tomcat Manager application. This means that
you can re-deploy applications without needing to re-start Tomcat or delete the previous deployment |
| Updated mySql JDBC driver |
An updated mySql JDBC driver has been provided. Please note this driver is provided as a
convenience and needs to be manually added to your JCodeBox installation if desired.
- Edit the JCodeBox classpath replace the existing mySql driver file with the new file
- Edit the mySql driver details in the main system view. Change the location to reflect the
location of the new driver file and change the driver class to the new driver class (i.e. from
org.gjt.mm.mysql.Driver to com.mysql.jdbc.Driver
|
| Updated postgresql JDBC driver |
An updated postgresql JDBC driver has been provided. Please note this driver is provided as a
convenience and needs to be manually added to your JCodeBox installation if desired. This driver
should only be used against postgresql 7 databases. If you are interrogating a postgresql 6
database, the postgresql driver shipped with the original version of JCodeBox should be used.
- Edit the JCodeBox classpath replace the existing postgresql driver file with the new file
- Edit the postgresql driver details in the main system view. Change the location to reflect
the location of the new driver file
|
| Minor bug fixes |
A number of minor bug fixes have been included i.e. Oracle to Java datatype mapping has been
enhanced to resolve the problem where some oracle datatypes were being mapped to the generic
object datatype |
| Documentation updates |
Parts of the JCodeBox documentation have been updated:
- User manual
- Knowledge base
- FAQ
Please update the doc sub-directory in your JCodeBox installation with the
doc sub-directory provided with the update if you would like to update your
local documentation set.
|
