MVC in Pentaho XUL applications can be acheived by architecting your application using the pattern we will detail here. As a refresher, the purpose of the MVC pattern is separation of concerns in UI applications. The idea is to keep a clear separation between the data we would like to display and how that data is being displayed. In Pentaho XUL framework (PXF) the view layer is represented at least partially represented in a xul dom object (typically coming from a xul file). I say "partially" because you could consider view logic to be part of the view and view logic is not included in the XUL DOM
The diagram below shows how Pentaho XUL MVC would operate in an example UI widget project Foo. Starting from the left we see that the XUL file foo.xul is represented in your application as a XulDom. The XulDom is what we consider to be the View of our MVC implementation PXF by way of the XulDom is responsible for instantiating and laying out UI components, however, as we mentioned earlier view logic is not handled by the XulDom. The responsiblity for handling view logic rests on the Controller and can be thought of as being component-state changes or non-component-state events. These two classes of events are handled differently in the Controller. Events are handled directly in the controller whereas component state changes are simply mapped in the controller, leaving the handling of state changes to the binding layer. By structuring your application this way, you will have zero dependencies on Xul inside your Model which makes your model much more testable. Only your Controller code will know anything about Xul in the case that it needs to launch XulDialogs for example. Your Controller, however, should never need to reference a XulComponent directly.
Data Binding and Component-state Events
It is the responsibility of your Controller implementation to setup bindings between your XUL components and your data model (a POJO/Java Bean). What do we mean by "binding"? Binding is a way to associate bean properties so that when one changes, the other is kept in sync. Binding can be unidirectional or bidirectional, but we won't get into that here. For more information on Pentaho XUL binding see XUL Bindings. We will assume that a binding is always bidirectional meaning when either side of the binding changes, the other will reflect the change. This is useful in UI applications because we can tie, say, a text box's value to a model bean String property. Consider the following XUL file snippet that defines a text box component by id "nameTextBox". Notice that there are no attribute specifying event handler calls; these are not needed when using data binding.
Here is a snippet of the corresponding controller onLoad method. Notice how you create a binding between the model's name property and the nameTextBox XUL component value property.
Behind the scenes this bind method is retrieving a XulComponent by id "nameTextBox" and linking the name property of the model to the value property of the XulComponent instance. Now let's say in addition to binding the name property to a text box we want to wire the enabled state of an OK button to a boolean bean property on the model. We would just add another bind call that ties the two properties together, notice the "!" expression which does an in-flight negation of boolean value (very helpful with XulComponents which use disabled rather than enabled properties).
Event Handling and non-Component-state Events
In the diagram you will see that the XulDom fires "events" to the FooController. As we mentioned before, these events are not state changes of a XulComponent, rather these are launching and routing operations such as displaying a dialog. Events are declared in xul source file as tag attributes, e.g.:
When PXF parses this tag, it will register an onclick property on the button component such that when the button is clicked PXF will try to find a registered event handler by the name of "fooController" and call it's displaySearchDialog method. You register an event handler on a XulDomContainer object like so (you will likely do this during your application's initialization):
Foo Example Source
- represented as a Java Bean (with property change support)
- "models" view state as bean properties
- contains view logic such as enablement and visibility
- applies form validation
- represented in the XUL dom (via XUL source file)
- contains syntax for creation of UI components
- layout of UI components
- represented as a Java class that implements XulEventHandler
- binds UI state to the model
- performs UI evnt handling (not related to component state) such as launching of dialogs (XulDialog and XulWindow)
- should *never* reference XulComponent or subclasses