org.forgerock / org.forgerock.openig

15 Jun, 2015

3 commits

11 Jun, 2015

2 commits

02 Jun, 2015

1 commit

  • a5e026df   OPENIG-543 (CR-7114) Update HttpClient API to support non-blocking calls ... Browse Dir » 
    `Handler` and `Filter` are now returning `Promises` (thus are non blocking from
an API point of view).
The CHF `Client` SPI also supports non-blocking calls.

But all elements of the processing chain need to support this in order to really
gain something out of the `Promises`.

The `HttpClient` was not offering such support, so the OpenIG `ClientHandler` could
not take advantage of it.

git-svn-id: https://svn.forgerock.org/openig/trunk@1031 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     

26 May, 2015

3 commits

13 May, 2015

3 commits

30 Apr, 2015

2 commits

  • efd00bff   Use a Status attribute in StaticResponseHandler ... Browse Dir » 
    There is no reason anymore to separate the code and the reason in
StaticResponseHandler, so we now use an attribute of type Status.

git-svn-id: https://svn.forgerock.org/openig/trunk@995 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    laurent.vaills
     
  • 63c38d31   Fix compilation error due to changeof the Status. ... Browse Dir » 
    Since we introduce the class Status in forgerock-http-framework, some code's
modifications have to be done :
- To get the code of the status we now have to do response.getStatus().getCode()
into of response.getStatus(). (in the Groovy script or EL expression that means
we'll have to write response.status.code.
- Furthermore, the attribute reason in Response does not exist any more, so it
is not possible anymore to assign a custom reason phrase, as it is set to
standardized reason phrase through the constants defined in the class Status.
- Any status code has to be in the range [100,1000[

git-svn-id: https://svn.forgerock.org/openig/trunk@994 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    laurent.vaills
     

27 Apr, 2015

1 commit

25 Apr, 2015

1 commit

24 Apr, 2015

1 commit

23 Apr, 2015

1 commit

16 Apr, 2015

1 commit

01 Apr, 2015

1 commit

24 Feb, 2015

1 commit

19 Feb, 2015

1 commit

18 Feb, 2015

2 commits

17 Feb, 2015

2 commits

  • 46cb2247   Ease the Expression's evaluation without any scope ... Browse Dir » 
    Add a convenient method to evaluate an Expression that do not require any scope.

git-svn-id: https://svn.forgerock.org/openig/trunk@898 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    laurent.vaills
     
  • 8b839dd7   Add a type to Expression ... Browse Dir » 
    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
     

09 Feb, 2015

3 commits

05 Feb, 2015

1 commit

04 Feb, 2015

2 commits

03 Feb, 2015

4 commits

23 Jan, 2015

1 commit

22 Jan, 2015

1 commit

  • b7229e8c   OPENIG-180 (CR-5830) Provide a baseURI decorator ... Browse Dir » 
    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

  • dcfbc791   OPENIG-315 Complete the fix for empty messages ... Browse Dir » 
    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

1 commit

  • c21359e2   Removed spaces from previous commit for OPENIG-394. ... Browse Dir » 
    IDE Eclipse divided by two the spaces length when special chars are used
in the line. I choose to trust the IDE instead of checkstyle and diff, my mistake.
Output is fine with IntelliJ. Looks like a bug in eclipse.

git-svn-id: https://svn.forgerock.org/openig/trunk@837 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    violette