Hitachi Vantara Pentaho Community Wiki
Child pages
  • Advanced Guide to MVC in Pentaho XUL Applications

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


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  The Xul framework 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 events or non-component-state events. These two classes of events are handled differently in the Controller.

Data Binding and Component-state Events

It is the responsiblity 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. 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 snippet below of a controller's onLoad method.  Following the Foo theme, notice how you can create a binding between a model's name property and a XUL component's value property. 

Code Block

onLoad() { 
	bind(fooViewModell, "name", "nameTextbox", "value");

In the diagram you will see that the XulDom fires "events" to the FooController.  Events in this contex