17 Feb, 2015

1 commit

  • The type of an Expression is now given at the creation time,
    which means we do not provide it anymore for the evaluation.
    Furthermore, it helps the developper as it knows the expected
    type of an Expression.
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@897 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    laurent.vaills
     

13 Feb, 2015

1 commit


12 Feb, 2015

1 commit


09 Feb, 2015

7 commits


05 Feb, 2015

2 commits


04 Feb, 2015

5 commits


03 Feb, 2015

7 commits


29 Jan, 2015

3 commits


27 Jan, 2015

1 commit


23 Jan, 2015

5 commits


22 Jan, 2015

3 commits

  • git-svn-id: https://svn.forgerock.org/openig/trunk@845 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    violette
     
  • git-svn-id: https://svn.forgerock.org/openig/trunk@844 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    violette
     
  • As the URI rebasing is done at different places in the code
    we'd like to have a BaseUriHandler/Filter in order to factor
    out the code.
    
    Following the same scheme as the "Timer" decorator, the "baseURI"
    decorator is created by default in the Gateway Servlet.
    (Named "baseUri" and created at startup time in the top-level heap.)
    
    * GatewayServlet.class, Route.class
    The creation of the "baseUri" decorator means the attribute
    class 'baseURI' is no longer needed as the URI rebasing is now
    directly done by the decorator. In the other hand,
    the heap initialization performed within both class constructors,
    contained a list of reservedFieldNames where the 'baseURI'was present.
    It has been removed from there as it is now a global decorator.
    
    * RouteTest.java
    Removed unit test 'testRouteIsRebasingTheRequestUri'(Duplicated
    in the RouteBuilder test, and the RouteBuilder has the responsability
    to apply decorators).
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@843 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    violette
     

20 Jan, 2015

1 commit

  • The previous commit introduced a regression, especially for GET messages
    being sent with an empty entity where they should have no entity at all.
    
    They were being falsely detected as messages with content because we were
    comparing `EMPTY_STREAM` with `Entity.head` (the branched content) instead
    of the `Entity.trunk` (`head` being re-created every time OpenIG tries to read
    the content, so in the `HttpBasicAuthFilter` for example, we push the Entity,
    then delegates to the next handler in chain, so when message is sent, the
    `head` is != from the `trunk` and cannot be == to `EMPTY_STREAM`)
    
    I could not reliably reproduce that in a unit test with a real HTTP Server
    because the failure also need the HTTPClient to re-use the same connection
    for 2 consecutive messages. Thus, I only added a small `Entity` unit test
    to make sure that `Entity.mayContainData()` behave correct even when the
    entity is pushed/popped.
    
    git-svn-id: https://svn.forgerock.org/openig/trunk@838 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     

19 Jan, 2015

3 commits