Overview of DeltaSpike Modules

@@ -242,13 +242,13 @@ DeltaSpike.

Custom Project Stages

It’s possible to provide custom project stage implementations. +

It is possible to provide custom project stage implementations. Therefore, you have to provide an implementation of the ProjectStageHolder interface. In this class you nest the custom -project-stage implementations which have to be -public static final class and it’s required to extend ProjectStage. -It’s required to provide a public static final instance even though, -you won’t use it directly.

+ProjectStage implementations which have to be +public static final class and it is required to extend ProjectStage. +It is required to provide a public static final instance even though, +you will not use it directly.

ProjectStageHolder for custom project stage implementations:

@@ -287,26 +287,27 @@ customProjectStage = CustomProjectStageH

ProjectStageProducer (for 3rd party portable extensions)

ProjectStageProducer (for Third-party Portable Extensions)

ProjectStageProducer provides the producer method which allows to -inject the current project-stage. However, in some cases it’s needed to -use project-stages also during the bootstrapping process of the CDI -container and you can’t use injection. In such cases you can use +inject the current ProjectStage. However, in some cases it is needed to +use ProjectStages also during the bootstrapping process of the CDI +container and you cais not use injection. In such cases you can use ProjectStageProducer.getInstance().getProjectStage() to resolve the -current project-stage. This helper also contains helpers for unit-tests -- e.g. #setProjectStage. However, those methods shouldn’t be needed -for users (we just need them for testing different project-stage +current ProjectStage. This helper also contains helpers for unit-tests +- e.g. #setProjectStage. However, those methods shouldis not be needed +for users (we just need them for testing different ProjectStage scenarios).

Setting the active ProjectStage

Setting the Active ProjectStage

For setting the ProjectStage which shall get used in your application you can specify it in a few ways. The underlying mechanism used to -determine the string is the ConfigResolver. E.g.:

+determine the string is the ConfigResolver.

Example

-Dorg.apache.deltaspike.ProjectStage=Development

Modified: websites/staging/deltaspike/trunk/content/documentation/scheduler.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/scheduler.html (original) +++ websites/staging/deltaspike/trunk/content/documentation/scheduler.html Mon Dec 15 22:31:42 2014 @@ -134,7 +134,7 @@ body { data-target=".nav-collapse"> Apache DeltaSpike + href="http://deltaspike.apache.org/index.html">Apache DeltaSpike []

- Intro
- External Dependencies
- Overview
- Configure Your Projects +
  - 1. Declare Scheduler Module Dependencies
  - 2. Declare External Dependencies
  +
- Use the Module Features +
  +
-
Intro
+
Overview

-
This module provides a simple integration with Quartz v2 (per default) -or any other scheduler which supports cron-expressions for job-classes.
+
The Scheduler module provides simple integration with Quartz v2 (default) or any other scheduler that supports cron-expressions for job-classes.
-
External Dependencies
+
Configure Your Projects
-
If you would like to use the default-integration with quartz (which is -optional), you have to add quartz 2.x.
+
The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in Configure DeltaSpike in Your Projects. For Maven-independent projects, see Configure DeltaSpike in Maven-independent Projects.
+
+
+
1. Declare Scheduler Module Dependencies
+
+
Add the Scheduler module to the list of dependencies in the project pom.xml file using this code snippet:
+
+
+
+
<dependency> + <groupId>org.apache.deltaspike.modules</groupId> + <artifactId>deltaspike-scheduler-module-api</artifactId> + <version>${deltaspike.version}</version> + <scope>compile</scope> +</dependency> + +<dependency> + <groupId>org.apache.deltaspike.modules</groupId> + <artifactId>deltaspike-scheduler-module-impl</artifactId> + <version>${deltaspike.version}</version> + <scope>runtime</scope> +</dependency>
+
+
+
+
+
2. Declare External Dependencies
+
+
By default, the Scheduler module looks to integrate with Quartz. If this is the scheduler you would like to use, add Quartz 2.x to the list of project dependencies using this code snippet:

@@ -204,9 +239,12 @@ optional), you have to add quartz 2.x.

+
-
@Scheduled
+
Use the Module Features
+
+
@Scheduled

Just annotate your Quartz-Jobs with @Scheduled and they will get picked up and passed to the scheduler automatically (during the @@ -237,10 +275,11 @@ DeltaSpike) is required. That can be con container-control module as well as {} for 'no scopes').

-
With 'false' for @Scheduled#onStartup it’s even possible to -schedule/install jobs dynamically - e.g.:
+
With 'false' for @Scheduled#onStartup, it is even possible to +schedule/install jobs dynamically.

+
Example

@ApplicationScoped public class ProjectStageAwareSchedulerController @@ -276,16 +315,14 @@ schedule/install jobs dynamically - e.g.
-
-
-Manual Scheduler Control -
+
+Manual Scheduler Control -This SPI allows to control the scheduler (or integrate any other + Th SPI allows to control the scheduler (or integrate any other compatible scheduler as an alternative to Quartz2) -Via std. injection like +Via standard injection like @@ -294,15 +331,12 @@ compatible scheduler as an alternative t -it’s possible to manually start/stop the scheduler, + it is possible to manually start/stop the scheduler, pause/resume/interrupt/check scheduled jobs, register jobs manually or start a job once (without registering it permanently). -Attention: - - -With some versions of Weld you have to use +Attention: To use a typed injection-point and avoid deployment failure with some versions of Weld, you must use
@@ -327,19 +361,13 @@ start a job once (without registering it </alternatives>

-
-
to use a typed injection-point. Otherwise the deployment will fail.
-
-

-
-
Custom Scheduler
-
+
+
Custom Scheduler

-
It’s possible to replace the default integration with Quartz. Any other -scheduler which supports cron-expressions for job-classes can be used. -Please have a look at org.apache.deltaspike.test.scheduler.custom for -further details.
+
It is possible to replace the default integration with Quartz. Any scheduler that supports cron-expressions for job-classes can be used. +For more information, see http://org.apache.deltaspike.test.scheduler.custom.
+

Modified: websites/staging/deltaspike/trunk/content/documentation/security.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/security.html (original) +++ websites/staging/deltaspike/trunk/content/documentation/security.html Mon Dec 15 22:31:42 2014 @@ -6,7 +6,7 @@ -DeltaSpike Security Module +Security Module @@ -134,7 +134,7 @@ body { data-target=".nav-collapse"> Apache DeltaSpike + href="http://deltaspike.apache.org/index.html">Apache DeltaSpike []

-
DeltaSpike Security Module
+
Security Module

-
Hint
-
SecurityBinding for class and method invocations
-
Integrating 3rd party security frameworks +
Overview
+
Configure Your Projects
+
1. Declare Security Module Dependencies
+
2. Enable the Security Interceptor
+
+
+
Use the Module Features +
+
SecurityBinding for Class and Method Invocations
+
Integrating Third-party Security Frameworks +

@Secured

AccessDecisionVoter

SecurityViolation
-
AbstractAccessDecisionVoter
-
@Secured and Stereotypes with custom Meta-data

-
Making intitially requested and secured page available for redirect after login -
-
CDI Implementation to redirect the login to the first denied page
-
PicketLink Implementation to redirect the login to the first denied page
+
AbstractAccessDecisionVoter +
+
@Secured and Stereotypes with Custom Meta-data
+
+
+
Making Intitially Requested and Secured Page available for Redirect after Login +
+
CDI Implementation to Redirect the Login to the First Denied Page
+
PicketLink Implementation to Redirect the Login to the First Denied Page

AccessDecisionVoterContext -
+

SecurityStrategy SPI

+
+

-
Hint
+
Overview
+
+
+
The Security module provides intercept and security checking on method calls. This module also enables integration of third-party security frameworks and custom security concepts.
+
+
+
+
+
Configure Your Projects

-
Hint: If you are using features described by this page with CDI 1.0 -(or DeltaSpike up to v1.1.0 with CDI 1.1+), you have -to enable the security interceptor in your beans.xml file:
+
The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in Configure DeltaSpike in Your Projects. For Maven-independent projects, see Configure DeltaSpike in Maven-independent Projects.
+
+
+
1. Declare Security Module Dependencies
+
+
Add the Security module to the list of dependencies in the project pom.xml file using this code snippet:
+
+
+
+
<dependency> + <groupId>org.apache.deltaspike.modules</groupId> + <artifactId>deltaspike-security-module-api</artifactId> + <version>${deltaspike.version}</version> + <scope>compile</scope> +</dependency> + +<dependency> + <groupId>org.apache.deltaspike.modules</groupId> + <artifactId>deltaspike-security-module-impl</artifactId> + <version>${deltaspike.version}</version> + <scope>runtime</scope> +</dependency>
+
+
+
+
+
2. Enable the Security Interceptor
+
+
For CDI 1.0 (or DeltaSpike v1.1.0 and earlier together with CDI 1.1+), you must enable the security interceptor in the project beans.xml file:

@@ -214,25 +261,24 @@ to enable the security interceptor in yo

+

-
SecurityBinding for class and method invocations
+
Use the Module Features

+
+
SecurityBinding for Class and Method Invocations

-
This feature of the security module functions by intercepting method -calls, and performing a security check before invocation is allowed to -proceed.
+
This feature of the Security module intercepts method calls and performs a security check before invocation is allowed to proceed.

In order to use the DeltaSpike security module, you must first have -installed the proper dependencies into your POM file. Once this is +installed the proper dependencies into the pom.xml file. Once this is complete, you may proceed to create a security parameter binding annotation. This is what we will use to add security behavior to our business classes and methods.

-
-
Create the SecurityBinding:
-

+
Create the SecurityBinding

@Retention(value = RUNTIME) @Target({TYPE, METHOD}) @@ -254,10 +300,8 @@ if we need to access parameter arguments context. Note that we may also inject other beans into the parameter list of our @Secures method.
- -Create the Authorizer: - +Create the Authorizer @ApplicationScoped public class CustomAuthorizer @@ -276,10 +320,8 @@ list of our @Secures method. This binding annotation may be placed on the entire class (securing all methods,) or on individual methods that you wish to secure. - -Secure a bean method: - +Secure a Bean Method @ApplicationScoped public class SecuredBean1 @@ -297,10 +339,8 @@ methods,) or on individual methods that in our authorizer bean by creating custom @SecurityParameterBinding types; this is a simple step once we have completed the work above: - -Create a parameter binding annotation: - +Create a Parameter Binding Annotation @Retention(value = RUNTIME) @Target({PARAMETER}) @@ -315,10 +355,8 @@ types; this is a simple step once we hav values as arguments into our authorizer method, providing domain-level security in our applications: - -Update the Authorizer to use parameter binding: - +Update the Authorizer to use Parameter Binding @ApplicationScoped public class CustomAuthorizer @@ -335,10 +373,8 @@ security in our applications: Note that our business method must also be annotated. - -Complete the parameter binding: - +Complete the Parameter Binding @ApplicationScoped public class SecuredBean1 @@ -396,10 +432,8 @@ to use a secured return value: Now the authorization will take place after the method invocation using the return value of the business method. - -Complete the parameter binding: - +Complete the Parameter Binding @ApplicationScoped public class SecuredBean1 @@ -417,17 +451,15 @@ the return value of the business method. as part of our security authorizer! - - -Integrating 3rd party security frameworks - -@Secured +Integrating Third-party Security Frameworks + +@Secured @Secured is build on @SecurityBindingType and a very simple -alternative to the rest of the security module. It’s a basic hook to -integrate a custom security concept, 3rd party frameworks,… . It -doesn’t provide a full blown security concept like the rest of the +alternative to the rest of the security module. It is a basic hook to +integrate a custom security concept, third-party frameworks, etc. It +doesis not provide a full blown security concept like the rest of the security module, but other DeltaSpike modules ensure that the security concepts are integrated properly (e.g. correct behaviour within custom scope implementations,…). It just allows to integrate other security @@ -440,10 +472,8 @@ a bit, because between the interceptor a approach. Therefore the basic behaviour remains the same and you can think about it like an interceptor.) - -Securing all intercepted methods of a CDI bean: - +Securing All Intercepted Methods of a CDI Bean //... @Secured(CustomAccessDecisionVoter.class) @@ -453,13 +483,8 @@ think about it like an interceptor.) } - -or - - -Securing specific methods: - +Securing Specific Methods //... public class SecuredBean @@ -473,8 +498,8 @@ think about it like an interceptor.) - -AccessDecisionVoter + +AccessDecisionVoter This interface is (besides the Secured annotation) the most important part of the concept. Both artifact types are also the only required @@ -495,16 +520,17 @@ parts: -[TODO] hint about the changed parameter/s +[TODO] tip about the changed parameter/s - -SecurityViolation + +SecurityViolation In case of a detected violation a SecurityViolation has to be added to the result returned by the AccessDecisionVoter. + AbstractAccessDecisionVoter @@ -526,19 +552,16 @@ This is a convenience class which allows } - - -@Secured and Stereotypes with custom Meta-data + +@Secured and Stereotypes with Custom Meta-data If there are multiple AccessDecisionVoter and maybe in different -constellations, it’s easier to provide an expressive CDI stereotypes for +constellations, it is easier to provide an expressive CDI stereotypes for it. Later on that also allows to change the behaviour in a central place. - -Stereotype support of @Secured: - +Stereotype Support of @Secured @Named @Admin @@ -556,12 +579,10 @@ place. -Furthermore, it’s possible to provide custom meta-data easily. - - -Stereotype of @Secured with custom meta-data: +Furthermore, it is possible to provide custom meta-data easily. +Stereotype of @Secured with Custom Meta-data @Named @Admin(securityLevel=3) @@ -594,17 +615,15 @@ place. - - -Making intitially requested and secured page available for redirect after login - + +Making Intitially Requested and Secured Page available for Redirect after Login DeltaSpike can be combined with pure CDI or with any other security frameworks (like PicketLink) to track the denied page and make it available after user logs in. - -CDI Implementation to redirect the login to the first denied page + +CDI Implementation to Redirect the Login to the First Denied Page Your LoginService will fire a custom UserLoggedInEvent @@ -678,8 +697,8 @@ store the denied page on your own. - -PicketLink Implementation to redirect the login to the first denied page + +PicketLink Implementation to Redirect the Login to the First Denied Page Once that PicketLink handles the authentication for you, you only need to store the denied page and observe PicketLink LoggedInEvent to @@ -745,10 +764,8 @@ store the denied page on your own. - - -AccessDecisionVoterContext - + +AccessDecisionVoterContext Because the AccessDecisionVoter can be chained, AccessDecisionVoterContext allows to get the current state as well as @@ -766,18 +783,18 @@ the results of the security check. getViolations() - Exposes the found violations
-getSource() - Exposes e.g. the current instance of javax.interceptor.InvocationContext in combination with @Secured used as interceptor. +getSource() - Exposes, for example, the current instance of javax.interceptor.InvocationContext in combination with @Secured used as interceptor. -getMetaData() - Exposes the found meta-data e.g. the view-config-class if @Secured is used in combination with type-safe view-configs +getMetaData() - Exposes the found meta-data, for example the view-config-class if @Secured is used in combination with type-safe view-configs getMetaDataFor(String, Class<T>) - Exposes meta-data for the given key
- -SecurityStrategy SPI + +SecurityStrategy SPI The SecurityStrategy interface allows to provide a custom implementation which should be used for @Secured. Provide a custom @@ -785,15 +802,28 @@ implementation as bean-class in combinat @Specializes (or as global-alternative). -In case of global-alternatives an additional config needs to be added to -/META-INF/apache-deltaspike.properties - e.g.: +In case of global-alternatives an additional configuration needs to be added to +/META-INF/apache-deltaspike.properties. - -globalAlternatives.org.apache.deltaspike.security.spi.authorization.SecurityStrategy=mypackage.CustomSecurityStrategy + +Example + +globalAlternatives.org.apache.deltaspike.security.spi.authorization.SecurityStrategy=mypackage.CustomSecurityStrategy + + + + + + + + + +Tip + +The configuration for global-alternatives is following the pattern: +globalAlternatives.<interface-name>=<implementation-class-name> + - -Note: The config for global-alternatives is following the pattern: -globalAlternatives.<interface-name>=<implementation-class-name> Modified: websites/staging/deltaspike/trunk/content/documentation/servlet.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/servlet.html (original) +++ websites/staging/deltaspike/trunk/content/documentation/servlet.html Mon Dec 15 22:31:42 2014 @@ -134,7 +134,7 @@ body { data-target=".nav-collapse"> Apache DeltaSpike + href="http://deltaspike.apache.org/index.html">Apache DeltaSpike [] -Configuration -Injectable Servlet objects + Overview +Configure Your Projects +1. Declare Servlet Module Dependencies + + +2. Configure Listeners and Filters +Use the Module Features + +Injectable Servlet Objects + ServletContext ServletRequest / HttpServletRequest ServletResponse / HttpServletResponse @@ -179,18 +187,59 @@ body { Principal -Servlet event propagation - -Servlet context lifecycle events -Request and response lifecycle events -Session lifecycle events +Servlet Event Propagation + +Servlet Context Lifecycle Events +Request and Response Lifecycle Events +Session Lifecycle Events + + -Configuration +Overview + + +The Servlet module provides CDI integration with the Java Servlet API. It enables injection of common servlet objects and propagation of servlet events to the CDI event bus. + + + + +Configure Your Projects + + +The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in Configure DeltaSpike in Your Projects. For Maven-independent projects, see Configure DeltaSpike in Maven-independent Projects. + + +1. Declare Servlet Module Dependencies + +Add the Servlet module to the list of dependencies in the project pom.xml file using this code snippet: + + + +<dependency> + <groupId>org.apache.deltaspike.modules</groupId> + <artifactId>deltaspike-servlet-module-api</artifactId> + <version>${deltaspike.version}</version> + <scope>compile</scope> +</dependency> + +<dependency> + <groupId>org.apache.deltaspike.modules</groupId> + <artifactId>deltaspike-servlet-module-impl</artifactId> + <version>${deltaspike.version}</version> + <scope>runtime</scope> +</dependency> + + + + + + +2. Configure Listeners and Filters In most cases there is no need for any additional configuration beside @@ -204,7 +253,7 @@ register the listeners and filters in yo -Your container doesn’t support Servlet 3.0 or newer. +Your container doesis not support Servlet 3.0 or newer. You have set metadata-complete=true in your web.xml. @@ -215,8 +264,7 @@ register the listeners and filters in yo -In these cases you will have to add the following section manually to -your web.xml: +In these cases you will have to add the following section manually to the project web.xml: @@ -264,8 +312,10 @@ your web.xml: -Injectable Servlet objects +Use the Module Features + +Injectable Servlet Objects The DeltaSpike Servlet module contains producers for many objects of a Servlet environment. All produces are using the special qualifier @@ -281,8 +331,8 @@ injection of some Servlet objects out of private ServletObject servletObject; - -ServletContext + +ServletContext The ServletContext is made available in the application scope. It can be injected into any CDI bean like this: @@ -294,8 +344,8 @@ be injected into any CDI bean like this: - -ServletRequest / HttpServletRequest + +ServletRequest / HttpServletRequest The ServletRequest is made available in the request scope. The current request can be injected into a CDI bean like this: @@ -316,8 +366,8 @@ request can be injected into a CDI bean - -ServletResponse / HttpServletResponse + +ServletResponse / HttpServletResponse The ServletResponse is made available in the request scope. The current response can be injected into a CDI bean like this: @@ -338,8 +388,8 @@ current response can be injected into a - -HttpSession + +HttpSession The HttpSession is made available in the session scope. You can inject the current session of a user into a CDI bean like this: @@ -355,8 +405,8 @@ the current session of a user into a CDI of a session. - -Principal + +Principal The Principal is made available in the request scope. The current principal can be injected into a CDI bean like this: @@ -373,12 +423,10 @@ principal can be injected into a CDI bea - - -Servlet event propagation - + +Servlet Event Propagation -The DeltaSpike Servlet module will propagate a number of Servlet object + The DeltaSpike Servlet module propagates a number of Servlet object lifecycle events to the CDI event bus. This allows regular CDI beans to observe these events and react accordingly. @@ -388,11 +436,11 @@ To distinguish between construction and object, DeltaSpike uses the qualifiers @Initialized and @Destroyed. -The following sections will show which concrete Servlet objects are + The following sections shows which concrete Servlet objects are supported and how their lifecycle can be observed. - -Servlet context lifecycle events + +Servlet Context Lifecycle Events The Servlet module supports initialization and destruction events for the ServletContext. These events can for example be used to detect @@ -417,7 +465,7 @@ events can be observed: -org.apache.deltaspike.servlet.impl.event.EventBridgeContextListener +org.apache.deltaspike.servlet.impl.event.EventBridgeContextListener @@ -426,8 +474,8 @@ also simply remove the entry for the web.xml to disable the events. - -Request and response lifecycle events + +Request and Response Lifecycle Events The Servlet module also supports initialization and destruction events for the HttpServletRequest and HttpServletResponse. These events can @@ -471,7 +519,7 @@ class: -org.apache.deltaspike.servlet.impl.event.EventBridgeFilter +org.apache.deltaspike.servlet.impl.event.EventBridgeFilter @@ -480,8 +528,8 @@ also simply remove the entry for the web.xml to disable the events. - -Session lifecycle events + +Session Lifecycle Events The last category of events supported by the DeltaSpike Servlet module are the lifecycle events for the user’s HTTP session. The following @@ -505,7 +553,7 @@ this event category, deactivate the foll -org.apache.deltaspike.servlet.impl.event.EventBridgeSessionListener +org.apache.deltaspike.servlet.impl.event.EventBridgeSessionListener @@ -515,6 +563,7 @@ your web.xml to disable the +

Table 1. DeltaSpike Modules
Core	Required	+ For fundamental and defining DeltaSpike API and utility classes +
Bean Validation	Optional	+ For adding CDI support in Bean Validation, enabling creation of CDI aware `ConstraintValidator` methods that can use business objects (EJBs, ManagedBeans) to support validation needs +
Container Control	Optional	+ For CDI container booting and shutdown and associated context lifecycle management +
Data	Optional	+ For an enhanced JPA experience with declarative queries, reducing boilerplate to a minimum +
JPA	Optional	+ For transactional context and scope +
JSF	Optional	+ For CDI integration with JSF, with type-safe view config, multi-window handling, new scopes (WindowScoped, ViewScope, ViewAccessScoped, GroupedConversationScoped) and integration with DeltaSpike âcoreâ messages and exception handling +
Partial-Bean	Optional	+ For implementing a generic handler to replace manual implementations of interfaces (or abstract classes) +
Scheduler	Optional	+ For simple integration with Quartz v2 (default) or any other scheduler that supports cron-expressions for job-classes +
Security	Optional	+ For intercept and security checking on method calls +
Servlet	Optional	+ For integration with the Java Servlet API, enabling injection of common servlet objects and propagation of servlet events to the CDI event bus +
Test-Control	Optional	+ For writing CDI-based tests easily +

Overview of DeltaSpike Modules

Overview of DeltaSpike

Background

CDI

Portable CDI Extensions

About Apache DeltaSpike

Features of DeltaSpike

Java EE 7 without Java EE 7!

JSF Improvements

Productivity Improvements

Next

Partial-Bean

Partial-Bean Module

Usage

Overview

Configure Your Projects

Declare Partial-Bean Module Dependencies

Use the Module Features

@PartialBeanBinding

Custom Project Stages

ProjectStageProducer (for 3rd party portable extensions)

ProjectStageProducer (for Third-party Portable Extensions)

Setting the active ProjectStage

Setting the Active ProjectStage

Intro

Overview

External Dependencies

Configure Your Projects

1. Declare Scheduler Module Dependencies

2. Declare External Dependencies

@Scheduled

Use the Module Features

@Scheduled

Manual Scheduler Control

Manual Scheduler Control

Custom Scheduler

Custom Scheduler

DeltaSpike Security Module

Security Module

Hint

Overview

Configure Your Projects

1. Declare Security Module Dependencies

2. Enable the Security Interceptor

SecurityBinding for class and method invocations

Use the Module Features

SecurityBinding for Class and Method Invocations

Integrating 3rd party security frameworks

@Secured

Integrating Third-party Security Frameworks

@Secured

AccessDecisionVoter

AccessDecisionVoter

SecurityViolation

SecurityViolation

AbstractAccessDecisionVoter

@Secured and Stereotypes with custom Meta-data

@Secured and Stereotypes with Custom Meta-data

Making intitially requested and secured page available for redirect after login

Making Intitially Requested and Secured Page available for Redirect after Login

CDI Implementation to redirect the login to the first denied page

CDI Implementation to Redirect the Login to the First Denied Page

PicketLink Implementation to redirect the login to the first denied page

PicketLink Implementation to Redirect the Login to the First Denied Page

AccessDecisionVoterContext

AccessDecisionVoterContext

SecurityStrategy SPI

SecurityStrategy SPI

Configuration

Overview

Configure Your Projects

1. Declare Servlet Module Dependencies

2. Configure Listeners and Filters

Injectable Servlet objects

Use the Module Features

Injectable Servlet Objects

ServletContext

ServletContext

ServletRequest / HttpServletRequest

ServletRequest / HttpServletRequest