JBoss.orgCommunity Documentation
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.
Table 1.1. Key Functionality of Guvnor Tools
Feature | Benefit | Chapter |
---|---|---|
Guvnor Repositories View |
The purpose of this view is to enable access to Guvnor repository resources in a standard tree format | Section 3.4, “Guvnor Repositories View” |
Guvnor Connection Wizard |
This wizard helps to create a connection to a Guvnor repository. | Section 3.2, “Guvnor Connection Wizard” |
Guvnor Resource History View |
This view shows revisions of specific resources available in the repository. | Section 3.5, “Guvnor Resource History View” |
Resource from Guvnor wizard |
This wizard helps to get local copies of Guvnor repository resources. | Section 3.3, “Resource from Guvnor Wizard” |
A number of actions for working with files |
The Guvnor actions (available through the Guvnor context menu on files) are provided for working with files, both those associated with Guvnor repository master copies and those not associated. | Section 2.3, “Managing Guvnor Resources” |
The Guvnor repository is not intended to be 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:
JBoss Developer Studio, which can be downloaded through the RedHat customer portal.
JBoss Server 4.2 or higher with Guvnor repository deployed.
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 perform the following steps to get Guvnor Tools running:
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.
Remove the JAXP libraries (xercesImpl-2.8.0.jar
, xml-apis-2.*
)
Remove the EL libraries (el-*
)
When these steps have been performed, 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 features in guvnor that have 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