org.forgerock / org.forgerock.openig

21 Oct, 2014

6 commits

  • b68d4ec6   OPENIG-299 Provide a default 'capture' decorator instance ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/openig/trunk@639 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     
  • ae57b57c   Style only ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/openig/trunk@638 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     
  • 3c08dd4c   OPENIG-299 (CR-4904) Add capture decoration for Filter/Handler ... Browse Code » 
    This decorator can be applied on any Filters or Handlers whose
input/outputs needs to be observed.

This decorator prints the message's values in the observed
component's logSink or in its own configurable logSink (if one
was specified).

Multiple observation points can be specified depending on what you're
interested in.

Observation points for Filter:
                            ---
          -- (request) ->  |   | -- (filtered-request) ->
                           | F |
 <- (filtered-response) -- |   | <- (response) --
                            ---

Observation points for Handler:
                   ---
 -- (request) ->  |   |
                  | H |
 <- (response) -- |   |
                   ---

git-svn-id: https://svn.forgerock.org/openig/trunk@637 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     
  • dfbe06f1   Introduce Json.ofEnum(Class<T> enumType) to transform JsonValue list to list of Enums ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/openig/trunk@636 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     
  • ae05730f   OPENIG-340 (CR-4904) Introduce heap object decorators. ... Browse Code » 
    Decorators have the unique capability of transforming heap objects: they
can encapsulate the original object into another compatible one (they
still have to share the same interface), they can post-configure
instances, ...

Two levels of decorations are supported: per-instance and global.

Global decoration allows to share widely a decoration for all objects
managed inside of a Heap. This is very useful to avoid writing the same
decoration over and over for each heap object.

Per-instance decoration permits to selectively apply decoration on some
instances. That can be very useful if you want to focus on a given heap
object, without impacting others.

Here is an example of decoration configuration for an instance:

    {
      "name": "Handler",
      "type": "ClientHandler",
      "capture": "request" <-- the decoration
    }

An arbitrary number of decorations can be applied on any instance.

The attribute name has to match a heap object name of the wanted decorator.
The attribute value is the configuration that will be passed to the
decorator when asked to decorate the heap object instance.

Decorators have to be declared in the /heap/objects list, just like
any other heap objects. The name of a decorator is the key that will be
used to lookup the right decorator in the heap when decorations are
processed.

Global decorations are Heap-scoped decorations: all heap objects
provided/managed by a given Heap will be decorated with that special
decorator. They are inherited between heaps.

Global decorations are enabled when a /heap/decorations object in the
JSON configuration (system config or route config) is found. Each
attributes of that object are representing a decoration configuration
to be applied on heap objects.

Example of global decoration configuration:

    {
      "heap": {
        "objects": [ ... ],
        "decorations": {
          "decorator-name": a JSON node representing the decoration config
          ...
        }
      }
    }

Notice that, in order to prevent infinite recursions, decorators cannot
be decorated themselves.

git-svn-id: https://svn.forgerock.org/openig/trunk@635 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    guillaume.sauthier
     
  • c4e17004   Supports multiple declaration resolution. ... Browse Code » 
    This case can happen when a component tries to resolve twice the same
object declaration.

This is unlikely to happen without any decorator support because all the
heap interactions are going on in one place and it's easy to refactor the
code to only resolve a declaration once.

But when decorators comes into play, it's no more easy to share resolved
objects references around.

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

15 Oct, 2014

4 commits

  • 68890016   Minor code cleanup. ... Browse Code » 
    - Reorganized imports.
- Removed extra spaces.
- Closed previously 'omitted' inputstreamreader in RouteBuilder.
(OPENIG-312)

git-svn-id: https://svn.forgerock.org/openig/trunk@623 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    violette
     
  • 98500dfe   CR-4828 OPENIG-312 ... Browse Code » 
    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
     
  • 77bed597   CR-4763 CR-4828 OPENIG-312 Consider using Jackson for parsing the JSON ... Browse Code » 
    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
     
  • 75b7e40a   DOCS-221: Update doc build tools ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/openig/trunk@620 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
    mark
     

10 Oct, 2014

1 commit

09 Oct, 2014

1 commit

08 Oct, 2014

1 commit

06 Oct, 2014

1 commit

01 Oct, 2014

1 commit

25 Sep, 2014

4 commits

24 Sep, 2014

4 commits

23 Sep, 2014

4 commits

22 Sep, 2014

2 commits

19 Sep, 2014

1 commit

18 Sep, 2014

1 commit

  • 6f608832   CR-4573 OPENIG-275: Document what is needed for load balancing and failover ... Browse Code » 
    If you can store all state on the user-agent,
for example by using the JwtSession implementation,
then perhaps OpenIG can be stateless enough
that there is no need to do anything special when load balancing.

If some of the state is stored on the server,
then you need to configure the load balancer for session stickiness
and to configure the container for session replication.

Neither the load balancer configuration
nor the container configuration
are specific to OpenIG,
so this patch explains what needs doing
and points to the documentation
for supported containers Apache Tomcat & Jetty.

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

17 Sep, 2014

1 commit

16 Sep, 2014

4 commits

15 Sep, 2014

4 commits