SlideServe
Menu
Préférences
© SlideServe · v2026

Component-Based Software Engineering with Java Event Model: A Bakery Example

arin avatar
21 diapositives · 372 Views · Aug 05, 2014

This document explores Component-Based Software Engineering using the Java Event Model through a practical example of a bakery notifying customers when their pizzas are ready. It introduces key concepts such as event listeners, event broadcasting, and how to manage customer notifications effectively. The example demonstrates the implementation of a `Bakery` class that manages order listeners, broadcasting pizza readiness events to registered customers. It also discusses the customer class that responds to these events, highlighting the multi-threaded nature of the simulation.

Component-Based Software Engineering with Java Event Model: A Bakery Example - slide 1
01 / 21Component-Based Software Engineering with Java Event Model: A Bakery Example
1 / 17

Télécharger la présentation

Component-Based Software Engineering with Java Event Model: A Bakery Example
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation
  1. Component-Based Software Engineering Using the Java Event Model Paul Krause

  2. Using the Java Event Model Contents • Quick Review of the Java Event model • Using this model to notify Customers that Pizzas are ready from a Bakery • This example is taken from JavaBeans by Example, by Henri Jubin, Prentice Hall

  3. Register Event Listener Fire Event Java Event Model Event Source Event Object Event Listener

  4. «interface» OrderListener EventObject Bakery source pizzaStatus(evt) getSource() toString() addOrderListener() removeOrderListener() sendMessage(PizzaEvent) fires PizzaEvent passed to Customer 0..* registers with invokes notifications in 0..* iNumber iSliceNumber run( ) Chili PizzaExpress

  5. EventObject source getSource() toString() PizzaEvent PizzaEvent.java import java.util.EventObject; public class PizzaEvent extends EventObject { public PizzaEvent(Object aSource) { super(aSource); } }

  6. OrderListener pizzaStatus OrderListener.java import java.util.EventListener; public interface OrderListener extends EventListener { public void pizzaStatus(PizzaEvent anEvent); } EventListener

  7. Bakery addOrderListener removeOrderListener sendMessage(PizzaEvent) Bakery.java public class Bakery public Bakery( ) { // constructor of a Bakery instance } public addOrderListener( eL ) { // inserts OrderListeners in some // structure } public removeOrderListener( eL ) { // deletes OrderListeners from that // structure } private void sendMessage( evt ) { // broadcast evt somehow }

  8. Properties of Bakery.java import java.lang.Thread; import java.util.*; public class Bakery implements Runnable { private Vector iCustomers = new Vector( ); private Thread iThread; // methods go here… }

  9. Constructor for Bakery public Bakery ( ) { iThread = new Thread(this); iThread.start( ); } // When a new instance of Bakery is created, // a flow of control owned by it is started.

  10. The main flow of control public void run( ) { while(true) { iThread.sleep(4000); PizzaEvent event = new PizzaEvent(this); sendMessage(event); } } // a Bakery broadcasts a message that Pizza is ready // every 4 seconds

  11. Adding and removing Listeners public void addOrderListener(OrderListener aListener) { iCustomers.addElement(aListener); } // Remember iCustomers is a Vector field in Bakery public void removeOrderListener(OrderListener aListener) { iCustomers.removeElement(aListener); }

  12. Broadcasting the message private void sendMessage(PizzaEvent anEvent) { Vector v; v = iCustomers.clone( ); for (int i = 0; i<v.size( ); i++) { OrderListener ol = v.elementAt(i); ol.pizzaStatus(anEvent); // implement in Customer } System.out.println(“Pizza ready …”); }

  13. Summary for Sources • Record all the references to Listener Objects in a “Vector” • Register Listeners by adding their name to the Vector • Unregister Listeners by removing their name from the Vector • Step through the elements of the Vector to notify all the Listeners

  14. «interface» OrderListener EventObject Bakery source pizzaStatus(evt) getSource() toString() addOrderListener() removeOrderListener() sendMessage(PizzaEvent) fires PizzaEvent passed to Customer 0..* registers with invokes notifications in 0..* iNumber iSliceNumber run( ) The Story so Far

  15. The Customer Class • A Customer also has its own flow of control public class Customer implements OrderListener, Runnable { private int iNumber; // identify customer private boolean iHaveSlice; // something to eat? private Thread iThread; // identifiy flow of control private Randon iRandom; // gaps between bites private int iSliceNumber; // Slices eaten … }

  16. Construct a Customer public Customer(int aNumber) { iNumber = aNumber; iRandom = new Random(aNumber); iThread = new Thread(this); iThread.start( ); } // Construct a Customer with a specified identifier, and // start its own flow of control

  17. Making your Customer Run public void run( ) { while(true) { if (iHaveSlice) { for (int bites=0; bites<4; bites++) { System.out.println(“customer: “ + iNumber + bites + “ slice:” + iSliceNumber); iThread.sleep(iRandom.nextFloat( ) * 3000); } iHaveSlice = false; iThread.suspend( ); } } // Takes 4 bites, with a rest between each, then } // waits for some more Pizza.

  18. Response to PizzaEvents • Remember, we invoked a method called “pizzaStatus” when we broadcast messages from the Bakery. Customer must implement this: public void pizzaStatus(PizzaEvent anEvent) { if ( ! iHaveSlice) { iHaveSlice = true; iSliceNumber++; iThread.resume( ); }

  19. Warning • These slides have simplified the implementation a little bit • We have missed out: • Explicit type conversions; • “Synchronisation” of critical sections in threads • The full implementation can be found on the CSM-15 Web site • This is taken from JavaBeans by Examples, Henri Jubin, Prentice Hall

  20. Running the Bakery public class TestApp { public static void main(String args[ ]) { TestApp t = new TestApp( ); } public TestApp( ) { Bakery b = new Bakery( ); Customer c1 = new Customer( 1 ); Customer c2 = new Customer( 2 ); b.addOrderListener( c1 ); b.addOrderListener( c2 ); } }

  21. Summary • We have explored a simple example of a general Notifier-Observer design pattern • Everything in this example is available in the Java 2 Software Development Kit • The trick has been to use a design pattern that allows as many Observers (Customers, in our case) to be added as required