ImagoX Extensions 

The ImagoX Extensions package is a group of standard and contributed Imago XSLT extensions. ImagoX provides a framework for the development of custom or application- specific extensions. Once an extension is incorporated into an Imago system it's methods are available from within the XSLT stylesheets. Unless otherwise noted these extensions require the Imago engine to function properly.
The general process for inserting extension content into a document is to create an element that will be transformed by an XSLT. The XSLT transform will execute the extension element. First create an XML document to be transformed. In the example below we create an Imago namespace that we will use to trigger the XSLT template.

<?xml version="1.0"?>
<document xmlns:imago="" >

The XSLT will use the Imago extension org.xenei.imago.extensions.ImagoSystem to get the format the client should received. Note that the Imago namespace has the same definition as in the XML document.

<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl=""
    extension-element-prefixes="xsystem "
<xsl:template match="document">
    <xsl:apply-templates />

<xsl:template match="imago:format">
    The desired format is <xsystem:format/>

Creating an XML document that has a <xsystem:format/> element will not cause the extension element to execute.

 ImagoX Counter 

ImagoX Counter Extension is an implementation of a "hit counter". ImagoX Counter can register hits, report hit totals, or both in a single request. Counter may be configured to use either a file-based or database-based datastore. Other datastore implementations are possible and may be plugged-in.

 ImagoX Forms 

ImagoX Forms Extension is an implementation of a forms processor. ImagoX Forms is an extensible HTTP GET/POST mechanism that provides field validation, validation error marking, and is resistant to hack attempts because Forms ignores valid input and extraneous input fields.

 ImagoX Mail 

ImagoX Mail Extension is an implementation of a mail sending mechanism. ImagoX Mail can send email to one or more "to" or "bcc" addresses, and HTML markup may be included.

 Release Contents product releases usually provide three (3) different distributions:
  1. A release file like  <product>_<version>_<build>.zip   contains everything needed to execute the package (except a JRE/JDK), product and API documentation, and the file from #2. The ImagoX full release also contains a "war" (web archive) file ready for deployment.
  2. A release file like  <product>_<version>_<build>   contains the source code, build support, and documentation support.
  3. A release file like  <product>_<version>_<build>   contains update pieces only.

 Other Information 

All trademarks and copyrights are the property of their respective owners.
Copyright © 2002-2003 by, All Rights Reserved

Go to home page.