title: Basic App Architecture - Basic Observer / Observable in JAVA
body: <p>I have a web-service written in JAVA that retrieves information about the weather and sends objects with that information.</p>
  
  <p>This information should be crunched using the Observer-Observable design pattern in JAVA.</p>
  
  <p>Also, I do need to send that information to a JList in SWING for the Graphical User Interface.</p>
  
  <p>The model, is implemented as the following :</p>
  
  <pre><code>public class Model implements Observer{
  // all the code that receives, override the update method and so on
  }
  </code></pre>
  
  <p>Then, I need to put that object in an array and send that information to the UI.</p>
  
  <p>The model receives automatically every 15 minutes a new weather object.</p>
  
  <p>I want to know which is the best architecture to implement this. Im not sure if I should receive the information in the model, process it, and update the UI manually using a button or something like that on the UI that triggers some method.</p>
  
  <p>The best scenario is to automatically update the JList after I processed the information on the Model.
  In that case, should I implement the observer in both the Model AND the UI ? Because the model receives from the web service and the model sends to the UI.</p>
  
  <p>Is a really basic problem, but Im not sure which is the best option to implement it, so I want some help.</p>
  
  <p>Im adding the picture to clarify the situation.</p>
  
  <p><a href="https://i.stack.imgur.com/egxf1.png" rel="nofollow noreferrer">BASIC ARCHITECTURE</a></p>
  
  <p>Thanks!</p>