Release NotesOctober, 2010
About Canoo RIA Suite Update 1b
Please see the Canoo RIA Suite Update 1 release notes for previous release notes.
To migrate from Canoo RIA Suite Update 1 to Canoo RIA Suite Update 1b, please see the migration notes.
Canoo RIA Suite requires the Java Runtime Environment (JRE) 1.5 or later on the server and on the client.
To deploy a Canoo RIA Suite application in a JEE server, the server needs to support either at least the Servlet 2.4 specification or at least the EJB 2.1 specification.
Packages, Modules, Parts and Release Structure
UltraLightClient is part of the Canoo RIA Suite. It consist of the ULC Core that includes all components required to successfully develop and deploy UltraLightClient applications. Additionally there are several extension packages that provide extended functionalities. The UltraLightClient modules, parts, packages, and the structure of the current release are described in the following sections.
Package ULC CoreULC Core contains everything that was in previous version of ULC enhanced with the new features: extended visual Effects, Charts, Animations and export to Google App engine.
The UltraLightClient release is split into modules. Each module belongs to exactly one of five categories:
All UltraLightClient classes.
For convenience, contains all other modules (except samples).
The UltraLightClient 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.
Utilities and extensions, e.g. application framework, test framework, QTP integration.
Only needed on demand.
Samples demonstrating the usage of UltraLightClient, 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 environement category.
A module directory contains subdirectories with the following contents:
Jar files that contain the module classes.
For sample and add-on modules 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.
Package ULC Table PlusULC Table Plus integrates the JIDE grids library that provides a table with various extended features.
Package ULC Web-IntegrationULC Web-Integration integrates the JxBrowser library. With this package you can integrate any web page directly into your ULC Application.
Package ULC Enterprise Portal-IntegrationWith this package you can integrate an ULC Application into your enterprise web applications or your enterprise portal server.
Package ULC Office-IntegrationThis package bundles Apache POI and iText to produce PDF and MS Office documents integrated into your ULC Application.
|<ULC_HOME>||UltraLightClient home directory|
|Add-ons to the UltraLightClient base framework|
|base||UltraLightClient base framework|
|all||For convenience, all UltraLightClient classes|
|Server integrations including EJB container integration and Servlet container integration and integration into local container for stand-alone (single JVM) ULC applications.|
|Client environment integration for applet deployment, JNLP deployment, and standalone deployment.|
|ext||contains the libraries of installed packages|
|license||the jar file with the deployment license key|
|previous_releasenotes||Previous release notes|
|Sample applications with ready to run Tomcat Servlet container|
|thirdpartylicenses||licenses of included third party libraries|
|license manager tool|
|build.txt||Contains the build number|
|LicenseAgreement.pdf||The license Agreement|
|UBA-8264||CellComponentTemplateStorage might hold too many templates|
|UBA-8270||Animators triggers set from server-side don't work anymore after Applet resume|
|UBA-8271||ulcApplet tag does not append the jsessionId anymore - leaving this as a liability to the developer|
|UBA-8272||NotSerializableException on AppEngine when loading icons from ResourceMap|
|UBA-8274||'ClientContext.loadFile' throws an NPE when the specified file is a directory or it does not exist.|
|UBA-8277||IllegalArgumentException when clicking 'Switch to Nested Header'||ULCTablePlusDemo|
|UBA-8276||ServiceLoader and OSGi does not work smoothly together.|
- Deprecated com.ulcjava.base.development.DevelopmentFileService, com.ulcjava.container.local.server.LocalFileService and com.ulcjava.environment.standalone.client.StandaloneFileService have been removed. Kindly use com.ulcjava.base.trusted.AllPermissionsFileService instead.
You can find known problems and limitations in our issue database.
Product and company names herein may be trademarks of their respective owners.