Release NotesDezember 13, 2006
About ULC 6.1.2
Release 6.1.2 is a maintenance release for ULC release 6.1. It includes the following changes:
To migrate from ULC 6.1 to ULC 6.1.2, please see the migration notes.
ULC 6.1.2 requires the Java Runtime Environment (JRE) 1.3.1 or later on the server, and Java Runtime Environment (JRE) 1.4.2 or later on the client.
The ULC client has been tested on Windows 2000/XP with the following deployment options:
- Applet: Running the ULC client as an applet has been tested with the following browsers:
- Firefox 1.0.3
- Microsoft Internet Explorer 5
- Microsoft Internet Explorer 6
- Java Web Start: Running the ULC client using Java Web Start has been tested with Java Web Start 1.4.2_05 and Java Web Start 1.5.0_04.
The ULC server has been tested on Windows 2000/XP, Red Hat Linux 9.0, and Sun Solaris 8 with the following deployment options:
- Servlet container: The Servlet integration has been tested on
- EJB container: The EJB integration has been tested on
This build is based on ULC 6.1.1 Please see the ULC 6.1.1 release notes for additional information.
Modules, Parts and Release Structure
The ULC release includes all components required to successfully develop and deploy ULC applications. The ULC modules, parts, packages, and the structure of the current release are described in the following sections.
The ULC release is split into modules. Each module belongs to exactly one of five categories:
The ULC core.
Always needed, for development and deployment.
Server-side integrations into containers, e.g. Servlet, EJB.
Only needed for server deployment.
Client-side integrations into environments, e.g. Applet, JNLP.
Only needed for client deployment.
Samples demonstrating the usage of ULC, e.g. Hello, ULCSet, OnlineShop.
Not needed during development or deployment.
The category and module names are reflected in the directory structure of the release, e.g. environment/applet for the applet module that belongs to the environment category.
A module directory contains subdirectories with the following contents:
Jar files that contain the module classes.
For sample module the required libraries.
Only for sample modules: the required resources, e.g. images, property files
Either complete source code or source stubs.
The source stubs are used to enable code completions in IDEs.
Only for sample modules: ready to deploy web application, i.e. war files
Each of these modules can contain up to four parts:
Contains classes to be deployed on the client side.
Runs inside the sandbox.
Contains classes to be deployed on the client side.
Does not run inside the sandbox. The additional permissions required depend on the module.
Contains classes to be deployed on the server side.
Contains all classes needed during development, i.e. the client, trusted, and server parts plus some additional development classes.
The part names are reflected in the filename of the jar files in the lib and src directory of the corresponding module, e.g. ulc-applet-client.jar and ulc-applet-client-src.jar for the classes and source stubs of the applet module that have to be deployed on the client side.
|ulc-6.1.2||ULC 6.1.2 home directory|
|base||ULC base framework|
|J2EE server integration including EJB container integration and Servlet container integration.|
|Client environment integration for applet deployment, JNLP deployment, and standalone deployment.|
|license||the jar file with the deployment license key|
|previous_releasenotes||Previous release notes|
|Sample applications with ready to run Tomcat Servlet container|
|build.txt||Contains the build number|
|LicenseAgreement.pdf||The license Agreement|
|UBA-964||Input is not blocked anymore when reloading an applet|
|UBA-6803||Calling the method waitForIdle() in UISession from different threads may lead to lock-up|
|UBA-6909||ULCComponent.scrollToVisible() does not work for ULCTextFields|
|UBA-6936||Exception due to null event listener that becomes a target of method invocation by reflection|
|UBA-6939||Setting a very large text on a ULCTextField results in a UTFDataFormatException|
|UBA-6986||JTableTree.scrollCellToVisible() does not work|
|UBA-6991||Examples in com.ulcjava.base.application.datatype.ULCNumberDataType are not current|
|UBA-6994||Application, Extension and Internal API tags are not rendered into the HTML API doc|
|UBA-6995||Include link again to previous release notes in releasenotes.html|
|UBA-7002||FilteringEventQueue.ensureIsUninstalled() sometimes causes an empty stack exception|
|UBA-7043||FocusListener does not work in ULCTableTree|
|UBA-7077||javax.swing.TableModel.getColumnCount() returns number of rows|
|UBA-7090||HttpSessionListener throws NullPointerException in case ULC application has not yet been started|
|UBA-7097||Default value of DefaultCloseOperation for ULCFrame on the client and server is different||The default close operation for ULCFrame and ULCDialog has been changed to HideOnClose. See migration notes.|
|UBA-7115||MouseMotionListener does not work in JTableTree|
|UBA-7120||ULC is not able to serialize String arrays that contain null elements|
|UBA-6944||Default coders should support java.sql.Date, java.sql.Time, java.sql.Timestamp|
|UBA-7003||Online shop sample: changes in shopping cart table do not update total|
|UBA-7072||ULC should support TimeZone objects out of the box|
- ULCFrame and ULCDialog: Due to the fix for UBA-7097
the server-side ULCFrame and ULCDialog classes now uses the same default close operation like the
client-side JFrame and JDialog classes.
The default close operation for ULCFrame and ULCDialog has been changed to HideOnClose.
- In a signed applet default cut/copy/paste using [ctrl]+x / [ctrl]+c / [ctrl]+v is broken. This is a Java Plugin bug not a ULC problem (see Java Bug Database). This problem only affects Java Plugin 1.4.2.
- After completion of a drag-and-drop operation, the mouse cursor is not set back to the default cursor. This problem only occurs on Linux. (UBA-686)
- Inappropriate mouse cursor feedback during drag-and-drop is observed if the drop target component rejects the drag operation. This occurs only in pre JRE 1.4.2. (UBA-756)
- Applet deployment does not work for Opera. (UBA-767)