org.jboss.webbeans.tck.integration.context.conversation
Class ConversationContextTest

java.lang.Object
  org.jboss.webbeans.tck.AbstractTest
      org.jboss.webbeans.tck.integration.context.conversation.ConversationContextTest

public class ConversationContextTest
extends AbstractTest

Author:

Nicklas Karlsson Spec version: PRD2

Nested Class Summary

Nested classes/interfaces inherited from class org.jboss.webbeans.tck.AbstractTest

AbstractTest.RunInDependentContext

Field Summary

Fields inherited from class org.jboss.webbeans.tck.AbstractTest

BUILT_IN_BEANS, manager, visited

Constructor Summary

ConversationContextTest()

Method Summary

void	testAllLongRunningConversationContextsOfInvalidatedHttpSessionAreDestroyed() When the HTTP servlet session is invalidated, all long-running conversation contexts created during the current session are destroyed
void	testAssociatedConversationOfJsfRequestDoesNotChangeDuringRequest() The conversation associated with a JSF request is determined at the end of the restore view phase and does not change during the request
void	testAssociatedConversationOfJsfRequestIsDeterminedAtEndOfRestoreViewPhase() The conversation associated with a JSF request is determined at the end of the restore view phase and does not change during the request
void	testConcurrentRequestsToLongRunningConversationsAreHandled() The Web Bean manager ensures that a long-running conversation may be associated with at most one request at a time, by blocking or rejecting concurrent requests.
void	testContextActiveDuringRenderResponsePhaseForNonFacesJsfRequest() For a JSF non-faces request, the context is active during the render response phase
void	testContextActiveFromBeginningOfApplyRequestValuesPhasetoResponseCompleteForJsfRequest() For a JSF faces request, the context is active from the beginning of the apply request values phase, until the response is complete.
void	testConversationsHaveUniqueStringIdentifiers() All long-running conversations have a string-valued unique identifier
void	testDefaultConversationIsTransient() By default, a conversation is transient
void	testJsfRequestHasExactlyOneAssociatedConversation() Any JSF request has exactly one associated conversation
void	testLongRunningConversationManuallyPropagatedToNonFacesRequest() The long-running conversation associated with a request may be propagated to any non-faces request via use of a GET request parameter named cid containing the unique identifier of the conversation.
void	testLongRunningConversationNotDestroyedAtEndOfJsfRequest() If the conversation associated with the current JSF request is in the long-running state at the end of a JSF request, it is not destroyed
void	testLongRunningConversationOfJsfRedirectIsPropagatedToNonFacesRequest() The long-running conversation context associated with a request that results in a JSF redirect (via a navigation rule) is automatically propagated to the resulting non-faces request, and to any other subsequent request to the same URL.
void	testLongRunningConversationOfJsfRenderingRequestIsPropagatedToRequestFromRenderedPage() The long-running conversation context associated with a request that renders a JSF view is automatically propagated to any faces request (JSF form submission) that originates from that rendered page.
void	testLongRunningConversationsMayNotCrossHttpSessions() All long-running conversations are scoped to a particular HTTP servlet session and may not cross session boundaries
void	testManagerCanDestroyOrphanedLongRunningConversations() The Web Bean manager is permitted to arbitrarily destroy any long-running conversation that is associated with no current JSF request, in order to conserve resources
void	testNewTransientConversationIsCreatedWhenConversationCannotBeRestored() If the propagated conversation cannot be restored, the request is associated with a new transient conversation
void	testNewTransientRequestIsCreatedWhenNoConversationIsPropagated() When no conversation is propagated to a JSF request, the request is associated with a new transient conversation.
void	testTransientConversationContextIsDestroyedAtEndOfJsfRequest() If the conversation associated with the current JSF request is in the transient state at the end of a JSF request, it is destroyed, and the conversation context is also destroyed.
void	testTransientConversationIsDestroyedAtEndOfJsfRequest() If the conversation associated with the current JSF request is in the transient state at the end of a JSF request, it is destroyed, and the conversation context is also destroyed.

Methods inherited from class org.jboss.webbeans.tck.AbstractTest

activateDependentContext, after, before, createEnterpriseBean, createProducerFieldBean, createProducerMethodBean, createSimpleBean, deactivateDependentContext, deployBeans, deserialize, getEnabledDeploymentTypes, getStandardDeploymentTypes, mockCreationalContext, serialize

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ConversationContextTest

public ConversationContextTest()

Method Detail

testContextActiveFromBeginningOfApplyRequestValuesPhasetoResponseCompleteForJsfRequest

@SpecAssertion(section="8.5.4")
public void testContextActiveFromBeginningOfApplyRequestValuesPhasetoResponseCompleteForJsfRequest()

For a JSF faces request, the context is active from the beginning of the apply request values phase, until the response is complete.

testContextActiveDuringRenderResponsePhaseForNonFacesJsfRequest

@SpecAssertion(section="8.5.4")
public void testContextActiveDuringRenderResponsePhaseForNonFacesJsfRequest()

For a JSF non-faces request, the context is active during the render response phase

testJsfRequestHasExactlyOneAssociatedConversation

@SpecAssertion(section="8.5.4")
public void testJsfRequestHasExactlyOneAssociatedConversation()

Any JSF request has exactly one associated conversation

testAssociatedConversationOfJsfRequestIsDeterminedAtEndOfRestoreViewPhase

@SpecAssertion(section="8.5.4")
public void testAssociatedConversationOfJsfRequestIsDeterminedAtEndOfRestoreViewPhase()

The conversation associated with a JSF request is determined at the end of the restore view phase and does not change during the request

testAssociatedConversationOfJsfRequestDoesNotChangeDuringRequest

@SpecAssertion(section="8.5.4")
public void testAssociatedConversationOfJsfRequestDoesNotChangeDuringRequest()

The conversation associated with a JSF request is determined at the end of the restore view phase and does not change during the request

testDefaultConversationIsTransient

@SpecAssertion(section="8.5.4")
public void testDefaultConversationIsTransient()

By default, a conversation is transient

testConversationsHaveUniqueStringIdentifiers

@SpecAssertion(section="8.5.4")
public void testConversationsHaveUniqueStringIdentifiers()

All long-running conversations have a string-valued unique identifier

testTransientConversationIsDestroyedAtEndOfJsfRequest

@SpecAssertion(section="8.5.4")
public void testTransientConversationIsDestroyedAtEndOfJsfRequest()

If the conversation associated with the current JSF request is in the transient state at the end of a JSF request, it is destroyed, and the conversation context is also destroyed.

testTransientConversationContextIsDestroyedAtEndOfJsfRequest

@SpecAssertion(section="8.5.4")
public void testTransientConversationContextIsDestroyedAtEndOfJsfRequest()

If the conversation associated with the current JSF request is in the transient state at the end of a JSF request, it is destroyed, and the conversation context is also destroyed.

testLongRunningConversationNotDestroyedAtEndOfJsfRequest

@SpecAssertion(section="8.5.4")
public void testLongRunningConversationNotDestroyedAtEndOfJsfRequest()

If the conversation associated with the current JSF request is in the long-running state at the end of a JSF request, it is not destroyed

testLongRunningConversationOfJsfRenderingRequestIsPropagatedToRequestFromRenderedPage

@SpecAssertion(section="8.5.4")
public void testLongRunningConversationOfJsfRenderingRequestIsPropagatedToRequestFromRenderedPage()

The long-running conversation context associated with a request that renders a JSF view is automatically propagated to any faces request (JSF form submission) that originates from that rendered page.

testLongRunningConversationOfJsfRedirectIsPropagatedToNonFacesRequest

@SpecAssertion(section="8.5.4")
public void testLongRunningConversationOfJsfRedirectIsPropagatedToNonFacesRequest()

The long-running conversation context associated with a request that results in a JSF redirect (via a navigation rule) is automatically propagated to the resulting non-faces request, and to any other subsequent request to the same URL. This is accomplished via use of a GET request parameter named cid containing the unique identifier of the conversation.

testLongRunningConversationManuallyPropagatedToNonFacesRequest

@SpecAssertion(section="8.5.4")
public void testLongRunningConversationManuallyPropagatedToNonFacesRequest()

The long-running conversation associated with a request may be propagated to any non-faces request via use of a GET request parameter named cid containing the unique identifier of the conversation. In this case, the application must manage this request parameter

testNewTransientRequestIsCreatedWhenNoConversationIsPropagated

@SpecAssertion(section="8.5.4")
public void testNewTransientRequestIsCreatedWhenNoConversationIsPropagated()

When no conversation is propagated to a JSF request, the request is associated with a new transient conversation.

testLongRunningConversationsMayNotCrossHttpSessions

@SpecAssertion(section="8.5.4")
public void testLongRunningConversationsMayNotCrossHttpSessions()

All long-running conversations are scoped to a particular HTTP servlet session and may not cross session boundaries

testAllLongRunningConversationContextsOfInvalidatedHttpSessionAreDestroyed

@SpecAssertion(section="8.5.4")
public void testAllLongRunningConversationContextsOfInvalidatedHttpSessionAreDestroyed()

When the HTTP servlet session is invalidated, all long-running conversation contexts created during the current session are destroyed

testManagerCanDestroyOrphanedLongRunningConversations

@SpecAssertion(section="8.5.4")
public void testManagerCanDestroyOrphanedLongRunningConversations()

The Web Bean manager is permitted to arbitrarily destroy any long-running conversation that is associated with no current JSF request, in order to conserve resources

testNewTransientConversationIsCreatedWhenConversationCannotBeRestored

@SpecAssertion(section="8.5.4")
public void testNewTransientConversationIsCreatedWhenConversationCannotBeRestored()

If the propagated conversation cannot be restored, the request is associated with a new transient conversation

testConcurrentRequestsToLongRunningConversationsAreHandled

@SpecAssertion(section="8.5.4")
public void testConcurrentRequestsToLongRunningConversationsAreHandled()

The Web Bean manager ensures that a long-running conversation may be associated with at most one request at a time, by blocking or rejecting concurrent requests.