23 Oct, 2014

1 commit


21 Oct, 2014

2 commits


15 Oct, 2014

2 commits

  • Consider using Jackson for parsing the JSON configuration
    - Renamed JsonValueUtil to Json.
    - Renamed JsonValueUtilTest to JsonTest.
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@622 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    violette
     
  • configuration
    
    - Remove json simple from openig pom file configuration. (added com.fasterxml.jackson.core / databind)
    - Jackson throws now IOExceptions instead of json exceptions.
    - Added unit tests.
    - Fixed javadoc.
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@621 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    violette
     

15 Sep, 2014

4 commits

  • git-svn-id: https://svn.forgerock.org/openig/trunk@574 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     
  • It was misplaced in the openig-core module where it was used in openig-war module.
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@573 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     
  • Heap.get(String):Object gains type safety
    
        Heap.get(String, Class<T>):T
    
    Heap.getRequiredObject(JsonValue, Class<T>) has a shorter name
    
        Heap.resolve(JsonValue, Class<T>):T
    
    Heap.getObject(JsonValue, Class<T>) is replaced by a resolve
    variant that supports optional dependencies:
    
        Heap.resolve(JsonValue, Class<T>, boolean):T
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@572 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     
  • Inline object declarations are a mean to ease understanding of
    Exchange processing.
    They permit to describe anonymously, inner objects when a reference to
    another heap object is required. That introduce, in the configuration
    files, some hierarchical support, easing the user to mentally
    represents his processing chain.
    
    This is done in a fully backward compatible way, without requiring any
    changes to existing object declarations (the one that requires other
    objects through references or names).
    
    The idea is to automatically extract inline declaration when the Heaplet
    is calling the get***Object() methods: if the provided JsonValue is a
    String, traditional object lookup is performed, but when the JsonValue
    represents a JSONObject (a Map), we try to turn this into a normal
    object declaration (just like what is done during heap initialisation).
    If the given JsonValue does not describe a valid declaration, a
    JsonValueException is thrown (again, just like the heap init process
    is doing).
    
    Notice that inline declarations do not require a 'name' attribute to
    be specified (like anonymous Java classes), so we generate a unique name
    based on the JsonPointer (represents the location of the node in
    the JSON structure).
    
    Notice that OPENIG-316 is partly resolved in this commit: HeapUtil methods
    have only been moved into the Heap interface: no additional type safety,
    no renaming.
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@571 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     

10 Sep, 2014

2 commits

  • git-svn-id: https://svn.forgerock.org/openig/trunk@566 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     
  • OpenIG used to provide a default Session implementation based on the
    underlying Servlet container's HttpSession. This changeset intends to
    gives to the user the ability to change the session persistence
    strategy (in other words: changing the Session implementation).
    
    This can be done at the global level (in the config.json, declaring a
    SessionFactory object named 'Session') or on a per-route basis (with the
    new 'session' attribute).
    When an Exchanges comes into a route that declares a new session type, a new
    session is build (no existing session items are propagated) and replace
    the old session. When the exchange exits the route, the new session is closed
    (notify the session that it's time to persist its content) and is replaced
    by the old one. Really like a push/pop stack mechanism.
    
    Notice that the 2 sessions are completely separated (cannot access the old
    content from the new and vis-versa). First, that would defeat the purpose of
    different session persistence modes (if items are propagated, where should
    I persist them ?). Secondly, Session is not intended to share data between
    handlers/filters: the Exchange is basically a request-scoped Map that is
    designed for that purpose.
    
    The JWT based session is a session implementation whose persistence is done
    using an HTTP Cookie, the session's content being serialized as JSON (usable
    types are constrained, see list below) and used as the payload of an
    encrypted JSON Web Token (JWT).
    
    The use of the JWT session has a few constraints:
     * HTTP Cookies are size-limited to 4K -> Small objects can be stored
     * Only JSON compatible types are supported:
        * null
        * Java primitive types + their boxed equivalent
        * Strings (and any CharSequence)
        * List and Map (of the supported types, recursively)
     * Same client performing concurrent HTTP invocations (so within the
       same HTTP session) that will modify their own session content will
       see inconsistencies in the session. This is due to the fact that the JWT
       session is not shared, each concurrent Thread has its own instance and
       can modify it at will. At the end of the processing, each Thread will
       serialize its own session's content regardless of other Threads.
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@565 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     

08 Sep, 2014

1 commit


03 Aug, 2014

4 commits


01 Aug, 2014

1 commit


31 Jul, 2014

1 commit

  • … order to add addition "enhanced" getters and setters for fields
    
    * perform mechanical changes to encapsulate fields for Message, Request, and Response
    * added Javadoc for getters and setters
    * Message no longer extends FieldMap since the expression library leverages the BeanResolver.
    
    Remaining non-mechanical changes (e.g. adding enhanced getters/setters) will be performed as separate changes.
    
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@430 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    matthew
     

28 Jul, 2014

1 commit


25 Jul, 2014

1 commit


07 Jul, 2014

1 commit

  • Replaced Copyrighted with Copyright
    removed the (c) character not required
    removed All rights reserved from Apex Identity copyrights. The code is open source, thus rights are no longer reserved.
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@345 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    ludo
     

03 Apr, 2014

1 commit


01 Nov, 2011

1 commit


13 Oct, 2011

1 commit