JBoss.orgCommunity Documentation

Chapter 1. Introduction

1.1. Guvnor Tools Key Features
1.2. What is Guvnor Tools?
1.3. Requirements and Installation

The purpose of this document is to describe briefly the functionality present in the Eclipse Guvnor Tools (EGT) for Drools 5. While not intended as a comprehensive reference, there should be enough detail included for early adopters using these tools.

The table below lists the key features of Guvnor Tools:

The following table lists all valuable features of the Guvnor Tools.


The Guvnor repository is not intended as a Source Code Management (SCM) solution, and the EGT is not intended to be an Eclipse “team provider” extension or replacement. Rather, the Guvnor repository is a location where certain artifacts (such as rules and SOA policy definitions) are controlled (“governed”) by policies defined by the deployment environment. The purpose of the EGT is then to enable access to resources held by the Guvnor repository, so they can be used in development. Thus, limited capabilities for reading, writing, adding, and removing Guvnor repository resources are provided in the EGT.

Guvnor Tools is a part of the JBoss Tools project. Thus to get started with Guvnor Tools, you should have the following:

To deploy JBoss Server with the Guvnor repository, you should download Drools Guvnor. When downloading you may choose either web based Guvnor to deploy to your JBoss Server or Standalone Guvnor with JBoss AS.

If you use JBoss AS 5 and Guvnor Tools doesn't work when deployed to the server, you should do the following to get Guvnor Tools running:

  1. Remove the JBoss Security libraries (authorization-spi-2.0.2.CR6.jar, identity-*, acl-spi-2.0.2.CR6.jar) from drools WAR file (not the app server itself). The JBoss Security libraries are provided in AS 5.

  2. Remove the JAXP libraries (xercesImpl-2.8.0.jar, xml-apis-2.*)

  3. Remove the EL libraries (el-*)

After this, Guvnor should operate as normal. During deployment, you would see the following exception in the log which indicates that the experimental JBoss Security based ACL integration has defined some EJB3/JPA stuff in guvnor that has not been configured.

ERROR [AbstractKernelController] Error installing to Start: name=persistence.unit:unitName=#ACL state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source 
for a RESOURCE_LOCAL enabled persistence context named: ACL            
    

Now refer to the Chapter 2, Tasks section to find out what you can do with Guvnor and Eclipse synchronization tool.