[
https://jira.jboss.org/browse/ARQ-185?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-185:
-----------------------------------
The WeldEmbedded(containers/weld-embedded) container should be renamed to WeldSEEmbedded
and should simulate the Weld SE environment. Only ApplicationScope active.
The WeldEEMockEmbedded(containers/weld-ee-embedded) container should mimic the EE behavior
and activate Session and Request Scope. The CDI spec states Conversation scope should only
be active during a JSF request, so WeldEEMockEmbedded will not default active the
Conversation Scope as part of the Test lifecycle. To test Conversation Scope we need to
use JSFUnit or some other JSF mockery framework.
WeldEEMockEmbedded container should have a option to enable Conversation scope during HTTP
request to mimic the behavior of Seam Servlet. Interact with the ConversationManager(2) to
setup/tear down context/conversations. Check if a transient conversation has been
activated by the user and store the Conversation Id between Request(TestMethod) to
reactive it on next Request.
Conversation context not activated in tests
-------------------------------------------
Key: ARQ-185
URL:
https://jira.jboss.org/browse/ARQ-185
Project: Arquillian
Issue Type: Bug
Reporter: Nicklas Karlsson
Conversation context should be active, right?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira