Tag Archives: jsf

JAVA EE – CDI Interceptor Example

In this post I will explain you one simple way of using interceptors in Java EE.

We have a simple java project that only displays a name wich is setted in the Controller class by the init method. But as you will see next, the final result it’s not the name that is setted by the controler, because we have an interceptor that changes the name behind the scenes.

The index page index.xhtm makes a server request to display the name. But that request is going to be intercepted by our interceptor MyInterceptor.java. Then who makes the request to the controller is the interceptor and if the response is of the type String it changes it to another string. When the page renders it will show not the response from the controller but the object that our interceptor returns to it.

And that’s it. Even without the final user knows nothing about it, the response has been manipulated by our interceptor.

  • Project Scheme


  • index.xhtml


  • Controller.java

Note that in line 10 we have a special annotation. This marks this bean to be intercepted, as you will see next.  The code in the 20th line, just sets the variable name to John Doe.

  • LogToConsoleAndModifyResult.java

This is a simple annotation class (out of the scope of this post, for now). The important thing here is the @InterceptorBinding annotation.

  • MyInterceptor.java

In the MyInterceptor class we have 3 important annotations:

@Interceptor  (line 10),
@LogToConsoleAndModifyResult  (line 11) and the
@AroundInvoke  (line 14).

The first one makes this bean an interceptor. The second, marks this interceptor to intercept all methods in classes  annotated with the the same annotation. The last one, marks the method that is going to manipulate all the data.

Note that this method must returns an Object and as a parameter it takes the invocation context.

First we have a logger that prints out to the console a message before the interception. Then with the help of the invocation context, it lets the original method to proceed and keeps the result. Then it prints again to the console the real name returned by the controller (John Doe). After this, it changes the return value to Jane Doe, that is exactly what is going to be displayed in the page as the final result.

  • beans.xml

Finally, in order to use interceptors we must register them in the beans.xml file (line 3). Another possibility is to annotate the controller with @Interceptors({MyInterceptor.class}) but this approach is not recommended.

  •  The Log

the log messages

Here are the three messages sent to the console.

  • The result page

web page

As you can see here the displayed name isn’t John Doe, as you might expect, but the modified result: Jane Doe.

Source code

Feel free to comment.

JSF 2.2 Flash Scope Example

JSF 2.2 Flash Scope Example

In this article I will try to explain you how to use the flash scope in Java EE.

Introduced in JSF 2.0, the flash scope provides a short-lived conversation (flash session). It is a way to pass temporary objects (not only strings) that are propagated across a single view transition and cleaned up before moving on to another view. The flash scope can only be used programmatically as there is no annotation.

In some cases we need to redirect from one view to another view in JSF.  But when we do a redirect we lost everything that is stored in the url with a GET request. One solution is to use an EL expression of the abstract class Flash #{flash.foo}. So, this is a pretty simple solution to redirect without lost anything:

Source files:


The special thing here is the use of #{flash.foo}, where foo is the name of the variable in the flash scope.



The goal of this controller is just to do a redirect from the index.xhtml to the target.xhtml.



Here we fetch the value of the foo variable by doing again #{flash.foo} to display the data.

The results:
This is the first page with the message Hello World.



And finally this is the second page (target.xhtml) wich displays the message from the previous page.

Final Considerations

We’ve learned how to pass values with the help of flash from one view to another with redirects.

Notice that if you refresh the second page after it shows up, all the data has gone. That’s because the flash scope was destroyed immediately when the rendering of the second page occurs. This is the goal of the flash scope. It just holds some values (in a flash session) between one HTTP request and the subsequent HTTP response.

This type of scope must be done programmatically. There is no annotation, like there is, for example, to the request scope (@RequestScoped).

Please feel free to comment.

Download Source Files

See it running here…