Page tree
Skip to end of metadata
Go to start of metadata
Note that this extension was previously (in version 1.0) known as the DMT XML Scanner.

On this page:

Target audience:

CAST Administrators

Summary: This document provides technical information about the extension called DMT Framework Scanner (com.castsoftware.dmtxmlscanner).


The DMT Framework Scanner (com.castsoftware.dmtxmlscanner) extension automatically generates information for the Source Code Delivery report that is available in the CAST Delivery Manager ToolThe extension can be downloaded on its own as a standalone extension and is also shipped and automatically installed with CAST 8.3.x where x  5.

What does it do

The extension will scan all source code it encounters during the packaging action (scan phase) in the CAST Delivery Manager Tool and will attempt to identify a framework based on predefined patterns provided with the extension. Information about any framework that is identified in the source code will be provided in the Source Code Delivery report that is available in the CAST Delivery Manager Tool:

Note that when an XML file is 

Out of the box framework pattern support

The extension is shipped with a set of predefined pattern configuration files that are set up to identify the most common frameworks. When the extension is installed, the "active" pattern configuration files can be found in the following location:


The following patterns are provided "out of the box" - please check each .config file to see which frameworks are supported:

TechnologyPattern fileNotes
C / C++


Identifies frameworks based on file extensions and other methods.


Identifies frameworks based on file extensions and other methods.
JEE XML file


Identifies frameworks based on the URL referenced in the DOCTYPE element in the XML file.
JEE XML file


Identifies frameworks based on the XMLNS attribute of the first node in the XML file, or the schema location. For example, the following is taken from a Spring Framework 3.1 for Spring Beans:

<beans xmlns=""

The above would be matched by the following predefined pattern:

Note that if a version number attribute is found in the XMLNS, then this number will be recorded, rather than the version number specified in the *.config file.
JEE XML file


Identifies frameworks based on the first XML element in the XML file if it doesn't have any attributes.

If it is not possible to identify the framework with the first element in the XML file, then the next child element will be used: this is targeted at build systems such as Maven and Ant which use an initial <project> element with attributes and then a child element called <target>, take for example this Ant XML file:

<project name="simpleCompile" default="deploy" basedir=".">
   <target name="init">
      <property name="sourceDir" value="src"/ >
      <property name="outputDir" value="classes" />
      <property name="deployJSP" value="/web/deploy/jsp" />
      <property name="deployProperties" value="/web/deploy/conf" />

To match the above, use the following configuration in the .config file:

Javajava_language.configIdentifies frameworks based on file extensions and other methods.
PHPphp_language.configIdentifies frameworks based on file extensions and other methods.
Pythonpython_language.configIdentifies frameworks based on file extensions and other methods.
Web related (AngularJS, jQuery etc.)web_language.configIdentifies frameworks based on file extensions and other methods.

Customizing framework support

If you would like to customize the list of frameworks identified by the extension, you can do so by modifying the appropriate *.config file located here:


This will modify the extension in the current Delivery folder for all Applications managed in that Delivery folder. The majority of *.config files use the following format:



When using the framework_xmlnamespaces.config to match XML namespaces, you can use a "wildcard" pattern when you want to match multiple different frameworks in the same XML file, as follows:


For example, to avoid entering the following in the .config file to match the specific versions of the ActiveMQ framework:


you can use the following to match all versions of the framework:


XML file size limit

All XML files over 1MB in size will be ignored - this is to avoid performance issues when very large XML files are present in the source code.

CAST AIP compatibility

This extension is compatible with:

CAST AIP release
8.3.x where x 5(tick)

Supported DBMS servers

This extension is compatible with the following DBMS servers:

CAST AIP release
All supported releases (see above)(tick)(tick)(tick)



An installation of any compatible release of CAST AIP (see table above)

Download and installation instructions

Please see:

The latest release status of this extension can be seen when downloading it from the CAST Extend server.

CAST Delivery Manager Tool GUI

Source file scannerScans file extensions only as defined in the .config files named <technology>_language.config
XML scannerScans only XML files as defined in the .config files named framework_<type>.config
  • If you have existing packages:
    • and this extension (nor its predecessor the DMT XML Scanner 1.0) have been installed before, then both discoverers will not be automatically activated (i.e. ticked). If you would like to benefit from the information provided by the extension in the Source Code Delivery report, please enable them before the next package action.
    • and the extension's predecessor (DMT XML Scanner 1.0) has been installed before, then the XML scanner discoverer will be ticked, but the Source file scanner will not.
  • For all packages created after the installation of the extension, both discoverers will be automatically activated (i.e. ticked).

What results can you expect?

The results of the source code scan can be seen in the Source Code Delivery report in the CAST Delivery Manager Tool:

This report is an XML file and a specific section is dedicated to reporting any frameworks/versions that have been identified in the source code, for example:

  • No labels