Packaging

A common processor class and all the .properties file needed to configure it must be correctly packaged in a JAR file before you can deploy it. To package it you must:

1. Copy the files into a folder structure that matches:

   • The package name of your common processor

   • The package naming conventions required by the Content Engine's architecture

2. Pack it in a JAR file using an archiving utility that is capable of creating JAR files

Common widget processor package structure

For the common processor example shown earlier , you would need to create a JAR file with the following structure:

com
  +-escenic
  |  +-servlet
  |   +-default-config
  |     +-com
  |       +-escenic
  |       |  +-framework
  |       |   +-controller
  |       |    +-impl
  |       |      +-DefaultMapController.properties
  |       +-mycompany
  |           +-controller
  |            +-processor
  |              +-CustomCommonWidgetProcessor.properties
  +-mycompany
    +-controller
      +-processor
        +-CustomCommonWidgetProcessor.class