Editing Seam (section)

==Contexts==
A context defines a namespace, a set of context variables. Usually we obtain components from a context via injection, and put component instances into a context via outjection. Each Seam component type has a default scope if not explicitly specified. The scope is specified by the [[#org.jboss.seam.annotations.Scope|@Scope]] annotation. Types are:

{| class="gallery"
|Type
|Description
|Default for
|-
|APPLICATION
|Analogous the servlet application scope.
|
|-
|BUSINESS_PROCESS
|Spans multiple conversations for multiple users as controlled declaratively by start and end states in the business process definition file.
|
|-
|CONVERSATION
|The conversation scope maintains data for a single user across a well-defined series of pages
|entities, SFSB
|-
|EVENT
|Analogous the servlet request scope. Exists form the beginning of the Restore View phase until the end of the render response phase in the JSF life cycle.
|JavaBeans
|-
|METHOD
|
|
|-
|PAGE
|Begins at the start of the JSF Render Response phase and carries on with each adjoining JSF postback until a redirect or a navigation to another page occurs.
|
|-
|SESSION
|Analogous to the servlet session scope.
|
|-
|STATELESS
|forces a component to be instatiated each time the component name is resolved.
|SLSB, message driven beans
|-
|UNSPECIFIED
|
|
|}

===Conversation===
There is always a conversation context often a temporary conversation context active during the apply request values, process validations, update model values, invoke application and render response phases of the JSF request lifecycle. Seam transparently propagates the conversation context (including the temporary conversation context) across JSF postbacks and redirects. If you don't do anything special, a non-faces request  (a GET request for example) will not propagate the conversation context and will be processed in a new temporary conversation.