1. 06 Nov, 2016 1 commit
  2. 03 Nov, 2016 4 commits
  3. 02 Nov, 2016 4 commits
  4. 26 Oct, 2016 3 commits
  5. 19 Oct, 2016 1 commit
  6. 17 Oct, 2016 3 commits
  7. 16 Oct, 2016 2 commits
  8. 15 Oct, 2016 2 commits
  9. 14 Oct, 2016 1 commit
    • Fix using objects as arguments for jmx operations · 5e55293b
      Johannes Edmeier authored
      With this commit objects are passed now correctly to jolokia. The
      object's needs to be written in json, which is validated for well-
      formedness.
      From now on the attributes are read autmatically when the bean gets
      selected and I fixed that errors weren't displayed.
      
      fixes #301
  10. 13 Oct, 2016 1 commit
    • Wrap acitivti module.js with a scope · e0bd77bf
      Johannes Edmeier authored
      The 'use strict' in the activit module affected the global scope and
      broke the ui for some orderings of the modules. With this commit the
      module is wrapped into a function so the global scope isn't affected.
      
      fixes #294
  11. 12 Oct, 2016 3 commits
  12. 11 Oct, 2016 4 commits
  13. 04 Oct, 2016 1 commit
  14. 03 Oct, 2016 2 commits
  15. 01 Oct, 2016 1 commit
  16. 28 Sep, 2016 1 commit
    • Update to linkifyjs 2.1.2 · c564c898
      Johannes Edmeier authored
      Updated linkifyjs to 2.1.2 which treats single quotes as punctuation and now
      renders the detected links in the yml nicely.
  17. 27 Sep, 2016 4 commits
  18. 26 Sep, 2016 1 commit
    • Don't ignore events from child contexts · 9304e6a4
      Johannes Edmeier authored
      With the fix for #260 we ignored all events from child contexts which turns out
      to be wrong since the "main" application context is, in case spring cloud config
      is used, is a child  of the bootstrap context. So we just act on the events from
      WebApplicationContexts. After they're fired up the needed port information is
      available.
      
      fixes #277
  19. 25 Sep, 2016 1 commit
    • Don't use a eventsource for detecting hystrix · 57bae5d1
      Johannes Edmeier authored
      In case a hystrix.stream does'nt sends any data and just a ping the endpoint is
      not detecet correctly and the ui get unresponsive. The problem is that the sent
      "ping:" chunk doesn't triggers the message event listener.
      So instead we use a simple HEAD-request to get the header and status.
      
      fixes #276