ILOG JRules User Guide > Executing Rules > Tasks > Executing a Ruleset Using Rule Execution Server > Maintaining Execution Code Generators > Adding a New Execution Code Generator

Adding a New Execution Code Generator

 PREVIOUS NEXT

To add a new project generator to the list of proposed generators:

For the last three solutions, you need to create a plug-in project to declare your generator.

To create a plug-in project to declalre your generator:

  1. Create a Java class to generate the files in the new project. For more information on how to write this class, see Writing a New Generator Class.
  2. Declare the class as a new generator by adding it as a new extension managed by the plug-in, as follows:
    1. Double-click the plugin.xml file of your plug-in project.
    2. On the Extension page, click Add and create a new extension entry of type ilog.rules.studio.res.generator.
    3. Add a new generator to the new extension by selecting New/generator in the contextual menu on the ilog.rules.studio.res.generator.
      4. In the extension you can create a generator, a category, or a primary generator. The generator element is used to declare a generator. The category element is used to define categories that will be used in the generator declaration to group the generators. The primary generator element is used to declare a generator as a primary generator outside the categories. If no categories is defined, or if the category definition is incorrect, the generator will appear in the Other category.
    4. For the new generator, complete the extension element details as follows:
      5. - name: The name of your generator that will appear in the wizard.
      - id: A unique ID (in Eclipse) that references your generator.
      - description: The description of your generator that will appear in the wizard.
      - class: The Java class you previously created.
      - pageid: Enter ilog.rules.studio.res.generator.generatorChooserPage to see your generator in the Client Project for RuleApps wizard and the Artifacts for RuleApps wizard. Enter ilog.rules.studio.res.generator.generatorChooserPage.create to see your generator only in the Client Project for RuleApps wizard. Enter ilog.rules.studio.res.generator.generatorChooserPage.complete to see your generator only in the Artifacts for RuleApps wizard.
      - enabled: Set it to true to view your generator in the wizard.
      - wizard: The nested wizard of the generator. It will be displayed after the creation wizard or after the completion wizard.
      - creationWizardClass: The pages to use instead of the Client Project for RuleApps wizard default pages: the destination project, the RuleApp project used as source, and the ruleset to manage in the RuleApp project.
      - creationWizardPlugin: The name of the plug-in where the creationWizardClass can be found. By default it is the plug-in where the generator is defined.
      - completionWizardClass: The pages to use instead of the default in the Artifacts for RuleApps wizard: the destination project, the RuleApp project used as source, and the ruleset to manage in the RuleApp project.
      - completionWizardPlugin: The name of the plug-in where the completionWizardClass can be found. By default, this is the plug-in where the generator is defined.
    5. On the Dependencies page, as a minimum you must add the ilog.rules.studio.res plug-in and the ilog.rules.studio.res.ui plug-in if you redefine a wizard.

Related Concepts

Overview: Execution Code Generators
RuleApps and RuleApp Projects

Related Tasks

Invoking a Ruleset Using a Stateless Rule Session
Invoking a Ruleset Using a Stateful Rule Session
Invoking a Ruleset Using a Message-Driven Rule Bean
Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. PREVIOUS NEXT