=============================================================================== The Endeca Content Assembler API for Java GENERAL (1.0.1 Revision B) - Updated: October 16, 2008 - Revision B consists of an update to this release note file. The software has not changed since the 1.0.1 release. FEATURE (1.0.1 Revision B) - The 1.0.1 release of the Content Assembler API for Java includes support for Java 1.4 in addition to Java 1.5. For more details, see the API Reference for the Content Assembler API for Java and the Content Assembler API Developer's Guide for Java. ============================================================================= GENERAL (1.0.1 Revision A) - Updated: October 13, 2008 - Revision A consists of an update to this release note file. The software has not changed since the 1.0.1 release. KNOWN ISSUES (1.0.1 Revision A) Documentation: - OE3066: In the "Generating see-all links" section of the Content Assembler API Developer's Guide for Java, the documentation states that "You can provide front-end users with a "see-all" link to display the full results set of a record query." Instead of "record query" it should read "record or navigation query." ============================================================================= GENERAL (1.0.1) - Release Date: October 2008 - The release notes may have been updated since the release date. Access the Product Downloads section of the Endeca Support Center (https://support.endeca.com) for the most recent version of the release notes. BUG FIXES: (1.0.1) Content Assembler API: - OE2667: The property type in a template was treated as a pass-through element, so that retrieving the property through the Content Assembler API returned an untransformed XML element. The API now correctly returns the first matching Supplement object. - OE2280: Text search and range filters are now applied in addition to refinement selections when the "Restrict to Refinement State" option is selected in the Record Selector. In addition, record filters are now respected for record list properties. Record filters are applied by default, but this behavior is configurable on a per-property basis in the template. For details, see the Content Assembler API Developer's Guide for Java. - OE2664: A Property containing an ERecList value is now of a type that implements ERecListProperty, a new public interface. An ERecListProperty has additional public fields containing the corresponding ENEQuery and ENEQueryResult objects that were used to generate the record list. These two objects may be used to create a link to the target record set (or a "see all" link for the RecordList) in the application. For more information, see the Content Assembler API Developer's Guide for Java. ============================================================================= GENERAL (1.0.0) - Release Date: June 2008 - The release notes may have been updated since the release date. Access the Product Downloads section of the Endeca Support Center (https://support.endeca.com) for the most recent version of the release notes. - The Endeca Content Assembler API provides an interface to access template-driven content for rendering in Web-based applications based on a user's navigation state or other triggers. The Content Assembler API for Java is made up of the following components: - Content Assembler API - enables a Web application to pass an ENEQuery object to the MDEX Engine to access to dynamic page content based on page configurations created in the Endeca Page Builder. - Reference application - a modified version of the Endeca JSP reference application for use with the Page Builder and the Content Assembler API. The Content Assembler reference application provides a simple front-end interface that allows you to connect to an MDEX Engine and examine a record set as well as the content items that are returned by the Content Assembler API based on your navigation state. - Documentation - including the "Endeca API Reference for the Content Assembler API for Java" (an HTML help reference for the Content Assembler API for Java), "Endeca Content Assemmbler API Developer's Guide for Java" (CADevGuideJava.pdf), and this release note file. PREREQUISITES (1.0.0) The Content Assembler API requires Endeca Information Access Platform version 5.1.3 or later, with the following components installed: - The Endeca Presentation API for Java. - If you wish to run the Content Assembler reference application in the Endeca HTTP service, you must install the Web Studio and EAC Agent component. The Content Assembler API for Java is supported for all hardware and operating system platforms that are supported by Endeca IAP 5.1.3. The Content Assembler API requires Java 1.5. In addition, the Endeca Page Builder, a component of the Endeca Merchandising Workbench suite of tools, is required for content administrators to configure template-based pages. For details about installing the Merchandising Workbench, see the "Endeca Merchandising Workbench Installation and Migration Guide." INSTALLATION (1.0.0) 1. In your local environment, locate the Content Assembler API package (ContentAssemblerAPIJava-1.0.0.zip) that you downloaded from the Endeca Support Center (https://support.endeca.com). 2. Extract the Zip file. Endeca recommends that you extract the file into the Endeca directory. In a default installation, this is C:\Endeca (on Windows) or /usr/local/endeca (on UNIX). 3. For further information about using the Content Assembler API and deploying the reference application, see "Working with the Content Assembler API" in the Content Assembler API Developer's Guide in \doc\CADevGuideJava.pdf. KNOWN ISSUES (1.0.0) Documentation: - OE2173: The behavior of the Content Assembler API in the case when a cartridge is configured to display specific featured records and any of the specified record IDs are invalid is not documented. In this situation the API returns null for that record list property value. ===============================================================================