1. 15 Feb, 2016 2 commits
    • Guus der Kinderen's avatar
      OF-1087: Do not add empty-string prefixed namespaces · e4b7a75b
      Guus der Kinderen authored
      In dom4j, the default namespace of an element cannot be set by adding
      a namespace that has an empty-string prefix. Although the string
      representation of the element will be correct, that namespace is not
      being recognized as the default namespace of the element (instead, it
      is a namespace like any other prefixed namespace, to be used in child
      elements).
      e4b7a75b
    • Guus der Kinderen's avatar
      OF-1087: Whitespace does not take into account element boundary. · 12eba2f8
      Guus der Kinderen authored
      The original code depends on a whitespace to be present within the limits
      of the element. This is not safe (eg: <message><foo/></message> fails).
      Instead, the closing characters ( > or /> ) of the first element should
      be used, as that's guaranteed to be present.
      12eba2f8
  2. 25 Nov, 2015 1 commit
    • Guus der Kinderen's avatar
      OF-946: Centralize connection configuration. · e58d590b
      Guus der Kinderen authored
      This commit (which is compilable, but breaks some important
      functionality - work in progess) aims to centralize the configuration
      for connections. "Connections" are used in a broad sense here, and
      includes socket-based (TLS and legacy-mode SSL) client connections,
      BOSH-based client connections, component connections, connectionmanager
      (multiplexer) connections, but also connections to the admin panel.
      e58d590b
  3. 21 Nov, 2015 1 commit
    • Christian Schudt's avatar
      Language info should be in the Session, not in the Connection · 170b20cc
      Christian Schudt authored
      I feel the language (the stream's "xml:lang" attribute) should be in the Session interface rather than the Connection (similar as the stream id), because it's unrelated to the session's transport.
      
      The HttpSession already did that.
      
      Otherwise the used language is not easy to retrieve, e.g. when using SessionManager to get the session and OF-208 is hard to solve.
      
      Alternatively we can expose the Connection in the Session interface, but this approach feels wrong to me.
      
      Also use `java.util.Locale` rather than String, because it better reflects what can be in `xml:lang` (it can also have country codes, e.g. "de-CH")
      170b20cc
  4. 09 Nov, 2015 2 commits
  5. 30 Oct, 2015 1 commit
  6. 29 Oct, 2015 1 commit
  7. 05 Aug, 2015 1 commit
  8. 28 Apr, 2015 1 commit
  9. 13 Mar, 2015 1 commit
  10. 06 Mar, 2015 6 commits
  11. 26 Jan, 2015 1 commit
  12. 11 Jan, 2015 1 commit
  13. 23 Dec, 2014 1 commit
  14. 17 Sep, 2014 1 commit
  15. 05 Jun, 2014 1 commit
  16. 11 Apr, 2013 1 commit
  17. 15 Mar, 2013 1 commit
  18. 27 Nov, 2012 1 commit
  19. 10 Oct, 2012 1 commit
  20. 29 Sep, 2012 1 commit
  21. 30 Aug, 2012 1 commit
  22. 21 May, 2012 1 commit
  23. 02 Apr, 2011 1 commit
  24. 18 Mar, 2011 1 commit
  25. 18 Feb, 2010 1 commit
  26. 13 Feb, 2010 1 commit
  27. 10 Feb, 2010 1 commit
  28. 07 Feb, 2010 1 commit
  29. 09 Nov, 2009 1 commit
  30. 30 Sep, 2009 1 commit
  31. 31 Jul, 2008 1 commit
  32. 25 Jul, 2008 1 commit
  33. 09 Jul, 2008 1 commit