{"id":11299,"date":"2013-04-17T10:00:41","date_gmt":"2013-04-17T07:00:41","guid":{"rendered":"http:\/\/www.javacodegeeks.com\/?p=11299"},"modified":"2019-12-09T21:40:53","modified_gmt":"2019-12-09T19:40:53","slug":"java-ee-cdi-conversationscoped-example","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2013\/04\/java-ee-cdi-conversationscoped-example.html","title":{"rendered":"Java EE CDI ConversationScoped example"},"content":{"rendered":"

In this tutorial we shall show you how to create and use a ConversationScoped<\/code> Bean in a web application. In CDI, a bean is a source of contextual objects that define application state and\/or logic. A Java EE component is a bean if the lifecycle of its instances may be managed by the container according to the lifecycle context model defined in the CDI specification.<\/p>\n

The ConversationScoped<\/code> Bean is a bean whose scope describes a user\u2019s interaction with a JavaServer Faces application, within explicit developer-controlled boundaries that extend the scope across multiple invocations of the JavaServer Faces lifecycle. All long-running conversations are scoped to a particular HTTP servlet session and may not cross session boundaries.<\/p>\n

With ConversationScoped<\/code> beans we can achieve the same functionality we need from a ViewScoped JSF bean. In addition, with the ConversationScoped<\/code> beans we can maintain the same conversation \u2013 or state \u2013 between distinct page requests. But when we leave a conversation without it, the managed bean will stay active until it times out.<\/p>\n

Here we will create a JFS web application that uses a ConversationScoped<\/code> bean so as to achieve a conversation between a client and a server. The client will make multiple requests to the server, by navigating to distinct pages, so as to show how the bean is able to maintain a state.<\/p>\n

Our preferred development environment is Eclipse<\/a>. We are using Eclipse Juno (4.2) version, along with Maven<\/a> Integration plugin version 3.1.0. You can download Eclipse from here<\/a> and Maven Plugin for Eclipse from here<\/a>. The installation of Maven plugin for Eclipse is out of the scope of this tutorial and will not be discussed. Tomcat 7<\/a> is the application server used.<\/p>\n

Let’s begin,<\/p>\n

1. Create a new Maven project<\/h2>\n

Go to File -> Project ->Maven -> Maven Project.<\/p>\n

\"New-Maven-Project\"<\/a><\/p>\n

In the “Select project name and location” page of the wizard, make sure that “Create a simple project (skip archetype selection)” option is unchecked<\/strong>, hit “Next” to continue with default values.<\/p>\n

\"new<\/a><\/p>\n

Here the maven archetype for creating a web application must be added. Click on “Add Archetype”<\/strong> and add the archetype. Set the “Archetype Group Id” variable to \"org.apache.maven.archetypes\"<\/code>, the “Archetype artifact Id” variable to \"maven-archetype-webapp\"<\/code> and the “Archetype Version” to \"1.0\"<\/code>. Click on “OK”<\/strong> to continue.<\/p>\n

\"maven-archetype-webapp\"<\/a><\/p>\n

In the “Enter an artifact id” page of the wizard, you can define the name and main package of your project. Set the “Group Id” variable to \"com.javacodegeeks.snippets.enterprise\"<\/code> and the “Artifact Id” variable to \"cdibeans\"<\/code>. The aforementioned selections compose the main project package as \"com.javacodegeeks.snippets.enterprise.cdibeans\"<\/code> and the project name as \"cdibeans\"<\/code>. Set the “Package” variable to \"war\"<\/code>, so that a war file will be created to be deployed to tomcat server. Hit “Finish” to exit the wizard and to create your project.<\/p>\n

\"newcdiproject1\"<\/a><\/p>\n

The Maven project structure is shown below:<\/p>\n

\"newcdiproject2\"<\/a><\/p>\n