This document contains the release notes for each new release of eContent, with the latest notes appearing first. For completely detailed changes of all changes including bugs fixed, please consult the eContent Changelog
The release 3.0-ea series will be a little bit different from previous ea release cycles in that eContent's stability will be much greater than that of a typical "early access" release. The only difference is that new features are going to be added in a rapid cycle as the code base converges on the 3.0 final code. Therefore, to give people access to these features as fast as possible, we are releasing these changes in a series of iterative developments.
There have been many database changes in this release. Please consult the "Upgrading" document for specific table modification details.
This release of eContent corrects a few minor bugs and incorporates a number of performance enhancements. No functional changes are made with this release. Note that Expresso 4.03 is required.
The table RESOURCEDEF (associated with the DB Object "Resource" has 3 new fields in this version - run DBCreate and check the database discrepancy messages for details. The table must be manually altered to add these new fields, then DBCreate must be run again to populate them correctly.
eContent 2.0 is a major upgrade from previous versions. Great care should be taken when upgrading from previous versions - please contact Jcorporate support for assistance in upgrading your database from previous versions.
eContent 2.0 is characterized by a number of substantial new features, notably Templates and the changes to Resource definitions.
TOC "Styles" are obsolete - replaced by templates used with categories
The administrative user interface of eContent has been upgraded substantially, and now a number of different "views", and is JSP (Struts) -driven, meaning modifications are easy and quick. Each of the different administrative views has the ability to switch to another view, allowing indivudual administrative users to select their preferred interface.
Templates introduced, with Template Types - A template can be used with a category or a single resource - Page: a template combined with a specific resource or category
DB-Based repository now included, rather than implemented by specific resource types only. Any type of Resource that can be published can be defined to be stored in the database, or on an external filesystem-based repository.s
Attributes are now resource-type specific, and may have valid values defined.
Attributes can consist of other resources, allowing resources to be "nested".
Packages are re-organized for easier structure: see Javadoc for details
All servlets in eContent have been replaced with Controller objects, providing flexibility in UI for all functions.
New Resource type classes: DBResource - where a resource is defined as a table in a database, and CVSResource - where the resource is an entry in a CVS repository
Resource Editing: Resources can now be edited directly online. An editor type can be defined for each type of resource, with a default editor supplied.
Template Editing: Templates can be edited online
There are a number of facilities in eContent 2.0 that are not fully enabled yet, and some limitations on features:
The resource type implementation for access to CVS resources is not yet available for use.
It is currently not possible to store very large binary content in resources using the "DBResource" resource type implementation. The size depends on a number of factors, including the specific database engine being used, but resources over about 100k should be used with caution with this feature. More specifics on the size limitations are being determined, as well as ways to overcome them.
The new eContent User's Guide and eContent Administrator's Guide will be enhanced to include more details on the new features soon, as well as more exensitive examples.
Currently the functionality to import categories by deriving from directory structures is not enabled. It is still possible to create the categories manually within eContent, then import the individual resources. Export of Categories is fully functional.
The Job object that reads resource schedules and activates/deactivates scheduled resources is not operational yet. You can enter resource schedules, but they will not yet be taken into account.
This release of eContent includes the updates necessary to operate and take advantage of enhancements made to Expresso for Expresso version 3.11, as well as a number of small bug fixes and enhancements to eContent itself. This is primarily a compatability release - major functional enhancements to eContent are scheduled for 2.0, due for release very soon.
Please review the specific Upgrade notes for details on how to upgrade from previous versions of eContent.
Please note that 1.6 of eContent requires version 3.11 of Expresso - it will not run at all with any other version, and a message at startup will warn you of this.
This release of eContent contains updates to enable it to utilize the enhancements made to Expresso in version 3.00. These include configurable logging (utilizing the Apache log4j package), enhanced and configurable error handling, many improvements in customizability, and more. See the release notes for Expresso 3.00 for details.
A new Resource Type has been added to this release: When redirecting to a URL using the "Redirect to URL" resource type, different application server and browser combinations react differently if the redirect is "server-side" (e.g different content is supplied by the server) or "browser side" (e.g. the browser is told to move to a different URL). The new resource type allows client-side redirects to be used where appropriate.
The upload facility now uses a sequential number to assign it's temporary file names, overcoming a potential problem on some systems that assigned unusual or log session identifiers.
The user interface of eContent has been updated to conform to the standard for Expresso applications, including an easier-to-navigate left-hand menu and better access to the administrative view and the user view of a table of contents.
In previous versions of eContent, the output type for a particular piece of content was determined by attempting to match it's extension (e.g. .html) to the extension specified for a specific output type. This was limiting in several ways, one of which was the problem that .html and .htm, even though they might be the same content type, were in fact different output types. Case-sensitivity was also an issue on some database/platform combinations. In version 1.5, each Output Type has associated with it an extension pattern, rather than a single extension. These patterns are regular expressions, and thus can match more than one extension: for example, "html|HTML" matches either HTML or lowercase HTML. You can also specify a "catch-all" pattern for an output type by specifying * as it's pattern.
As it is now possible for an extension to match more than one output type, the output types are searched in order by the Search Sequence field specified for the output type - the first pattern that matches is used.
A number of other small enhancements and performance optimizations have been made to eContent.
Release 1.4 includes all of the changes necessary to be compatible with the latest enhancements to the Expresso Framwork. Please refer to the release notes for Expresso for details on those enhancements, and changes in the installation and setup sequence.
This release includes new functionality in the area of Workflow sequences: see the documentation about workflow in the "How-To" section of the documentation for details.
This new release is packaged (as is the new Expresso) as a .war file, for easier deployment in Servlet 2.2 -compatible servlet containers and J2EE-compatible application servers. The new .war file *includes* a copy of the appropriate Expresso release, making eContent easier than ever to install and administer.
Please contact support for assistance in transitioning to the 1.4 version - we recommend using the DBTool utility and it's "verify" option to list any required database modifications for your specific installation.
You should not install 1.4 without first moving to a backup directory any of the files from the 1.3 or earlier release - a number of files have changed locations and directories have been removed, and this will not be done if you install 1.4 "over" any previous release.
Release 1.4's .war file also includes complete Javadoc documentation for eContent and Expresso - it is no longer necessary to download a seperate file to access the Javadoc on your local system. Javadoc comments provide an invaluable additional insight into the workings of eContent, and we recommend reviewing them.
In addition to the corrections and enhancements in version 1.3ea, 1.3 includes updates to use the new facilities of Expresso 2.01, and reflects the package name changes and other updates in 2.01. In addition, this release now requires at least Servlet API 2.1 support (as 2.0 support in Expresso will be removed soon as well).
Release 1.3ea (Early Access) of eContent corrects a number of issues found in the previous release, including pathname issues specific to databases running on Windows NT. It also includes preliminary support for the new multi-database capabilities release in version 2.00 of Expresso.
Econtent 1.3ea uses a new series of JSP pages for access to it's administrative functions, allowing a higher level of customization and control - the new "start" page is installed in /components/rol/jsp/eContent.jsp. This replaces the previous page /components/rol/jsp/eContent.html.
Configuration changes required by Expresso 2 are also required by eContent - the properties file in the configDir directory referred to by the DefaultInit servlet must be renamed "default.properties" from it's current name (previously the name did not matter, many users used "expresso.properties"). This corresponds to the changes required by Expresso 2's support for multiple databases/environments.
This release includes a number of corrections and enhancements to documentation, including new sections in the How-To and the installation documentation.
A minor enhancement to facilitate easier creation of resources has been made: When a new resource is added, the "Admin" group is automatically granted all possible permissions to the new resource. This allows any "Admin" member to immediately access the resource and set up the remainder of it's required information without having to manually create permission.
Please see the release notes for Expresso 2.00ea for other enhancements included in this release of eContent. Note that this version of eContent requires Expresso 2.00ea or higher.
Release 1.2 of eContent provided a number of small corrections that made creating new resources difficult, including default values for status codes and workflow sequence codes.
Release 1.1 of eContent introduces some significant enhancements to the administrative user interface, and includes all of the appropriate updates to the documentation to correspond to these changes. In addition, it introduces the Resource Status Code facility, and the beginnings of the WorkFlow capabilities.
The user interface for Administration of eContent has been enhanced. The new main administrative page can be found at /components/rol/jsp/eContent.html, and is presented via frames for easy access.
This new interface presents all of the common administrative functions for eContent on a single page, with a special link to "Administer a Table of Contents". This link presents a special three-paned UI ideally suited to manipulating resources and categories in a more visual format than was possible before. Please see the new documentation for details.
As eContent is built using Expresso, access to Expresso's administrative pages has also been provided directly from the main administrative page in eContent.
A new facility to be able to indicate a custom "status" for any resource has been added. A Status code can also indicate that a resource is "preview only". Resources in this state will not present the latest version of their content to the usual end user requests, but instead will display the previous version of their content until the resource has been changed to a status code that is not "preview only". A new permission has been added to the available permissions for a resource, "Preview", which indicates what groups of users can use a new "file=preview" argument to the ShowResource servlet to look at the latest copy of a "preview-only" resource.
In this way, security can be used to define who is allowed to preview resources, and the resource status can be used to "release" new content to resources when it has been approved.
The basics of workflow processing have been added to this release - this support is still undergoing development, and more detailed documentation will be provided in it's use shortly.
Release 1.0 was the first commercially available release of eContent.