From Joomla! Documentation

The "API16" namespace is an archived namespace. This page contains information for a Joomla! version which is no longer supported. It exists only as a historical reference, it will not be improved and its content may be incomplete and/or contain broken links.

JObserver is an abstract class which provides basic functionality to use the Observer/Observable design pattern within a Joomla Application. See also JObservable.

Defined in



Method name Description
__construct Constructor
update Method to update the state of observable objects


jimport( 'joomla.base.observer' );


Code Examples


Let's say, we want to integrate Error-Handling in our application, but we don't know yet, if we want the error to be display, logged in a file, stored to the database, or all of the above. Our goal is, to keep the object that raises the error independent of the objects that store the error message.

class MyError extends JObservable {
   public $msg = NULL;

   function raiseError($msg){
      $this->msg = $msg;
      //Notify all attached ErrorHandlers of the state change.

//We now implement the Observers, thus the error handlers
class ErrorHandlerDisplay extends JObserver {
   function update(){
      echo $this->subject->msg;
class ErrorHandlerFileStorage extends JObserver {
   function update(){
class ErrorHandlerDB extends JObserver {
   function update(){
      $db = JFactory::getDBO();
      $sql = "INSERT INTO #__myerrors (message) VALUES (".$db->quote($this->subject->msg).")";

//Now we can use newly implemented MyError class to raise Errors.
$error = new MyError();

/* The constructor of the observers automatically attaches the observer to the subject
 * In our example that means that the constructor of the error handler automatically
 * attaches the handler to the MyError Object.
new ErrorHandlerDisplay($error);
new ErrorHandlerFileStorate($error);
new ErrorHandlerDB($error);


 * Would cause 'Help!!!' to be display, logged in a file, and stored in the database.
 * You can simply add and remove the error handlers as you like

What happened here? We separated the functionality of raising an error of the functionality of handling an error. In the future you can add additional ErrorHandlers, or remove some of the existing handlers, without the need to change any classes at all. Furthermore you can simply change an Errorhandler, without the need to change the MyError class. This greatly increases the reusability of your code.

This example was originally contributed by Batch1211.

Chris Davenport 04:57, 17 April 2011 (CDT) Edit comment