Once the extension is created, Integration Studio automatically generates, according to the definition of the extension elements, the necessary template files for the development boot-strap of that extension. Once these templates are generated, the source files listed below are added as resources of your extension and you can start coding the behavior of your extension actions.

The extension source files are stored in the file system in the Extension folder, under the Source folder in the corresponding sub-folder, according to the application server you are using. You can check them in the Resources tree.

.NET Source files

By default, for a .NET application server, your extension has the following source files, stored under the Source\NET folder:

This file contains the signature of the methods that correspond to the actions exposed by your extension. You must not change these signatures. Any action, either defined in Integration Studio or imported from an assembly, must be defined in this file.

Actions are declared in the Interface.cs file in the same way as explained above for <ExtensionName>.cs file.

These files are automatically generated by Integration Studio, during the Update Source Code operation, and you should not change them in the IDE.

J2EE Source Files

By default, for a .J2EE application server, the source files for your extension, stored under the Source\J2EE folder, are as follows:

These files are automatically generated by Integration Studio, during the Update Source Code operation, and you should not change them in the IDE.

Both Source Files

By default, for a .(Both) application server, the source files of your extension, stored under the Source\NET and Source\J2EE folders, are the files explained above for each platform.

If necessary, you can explicitly add more source files to your extension. How?

Properties of the Source Files

The Extension Source Files are added as resources of the extension with the following properties:

For more information about the Deploy Action property, see Resource Properties.

See Also

Code the Extension | Update Source Code | About Extension Life Cycle | Resource Editor