You can now store multiple DataSource JNDI names in JCodeBox. They can be entered via the
Application tab on the JCodeBox Options dialog. The DataSource JNDI name you enter for an Application
must be selected from this list (i.e. needs to have been entered previously).
While you are defining an application, if you change the DataSource JNDI name for the application,
you will be prompted to update the DataSource JNDI name for existing entity beans. If you choose yes,
you will be presented with a list of existing entity beans that have that DataSource JNDI name and be
able to select which ones should be updated.
EJB types
When defining EJB's, you can now enter a parent/base class and add implemented interfaces (where
applicable) for the following:
Bean class
Primary key class (entity only)
Home interface
Remote interface
Local home interface (J2EE 1.3 only)
Local interface (J2EE 1.3 only)
Entity bean field name capitalization
When you define an entity EJB based on a RDB/Manual entity, JCodeBox applies the following rules
to create field names for the EJB:
Convert the RDB/Manual entity field name to lower case
Remove underscores from the RDB/Manual entity field
Capitalize the first letter after each removed underscore
i.e. if a RDB/Manual entity field name was ACCOUNT_NUMBER, the entity EJB field name would be
accountNumber and the accessor methods would be getAccountNumber() and setAccountNumber().
This update allows you to switch this behaviour off i.e. to use the RDB/Manual entity field name
without any modifications.
Data Access Object code change
The template that produces Data Access Objects (DAO) has been modified so that the
java.sql.Connection object the DAO uses can be provided from an external source i.e. the
DAO doesn't have to create the java.sql.Connection object it uses.
JCodeBox GUI changes
The method definition dialog has been re-organized and the view helper dialog is now re-sizable.
Copyright Michael Campbell Associates Ltd. 1999-2003.
All Rights Reserved
