Information Technology Reference
In-Depth Information
UberFire
UberFire is a JBoss-based framework developed and maintained by the Drools and jBPM
team. UberFire creates a rich client platform built on top of GWT (
ht-
tp://www.gwtproject.org
)
and Errai (
http://erraiframework.org
)
. It is also the technology on
top of which the KIE workbench project is built. It provides a series of components for a
pluggable user administration, virtual file system management, and configurable perspect-
ives and user interfaces. It is thought of as a work on top of an application server, and de-
pends on JEE6 specifications (such as CDI, for dependency injection).
UberFire defines a few default implementations for a few of its services, but they are all
highly configurable. For example, for user management, they use a user properties file as
default, but the KIE workbench uses Java as a service implementation configured with a
file in the classpath at
META-INF/services/
org.uberfire.security.auth.AuthenticationSource
with the actual im-
plementation to use for authentication.
We will discuss only a few of the components of UberFire here due to the need of perhaps
a full topic to cover every component. However, if you wish to go deeper into the frame-
work utilities, visit
http://www.uberfireframework.org
.
Some of the most important functionalities that UberFire provides from our perspective are
follows:
• Integration of components
• Existing components and services used by jBPM6
• How to extend and reuse components
Tip
As I'm writing this topic, UberFire is still in Alpha state, so some things might change in
the near future. I'll try to cover the most important architecture components of UberFire
you will more likely use, and that are less likely to change in the future.
