[JBoss JIRA] Created: (WELD-878) WeldPhaseListener fails to activate conversation context if conversation is not found
8:34 a.m.
WeldPhaseListener fails to activate conversation context if conversation is not found
-------------------------------------------------------------------------------------
Key: WELD-878
URL: https://issues.jboss.org/browse/WELD-878
Project: Weld
Issue Type: Bug
Components: Conversations, Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.1.0.Final
Environment: Glassfish 3.1 B43 updated with weld-1.1.0-SNAPSHOT
(weld-osgi-bundle-1.1.0-20110329.041630-9.jar)
Reporter: Jarkko Hyöty
It seems that org.jboss.weld.jsf.WeldPhaseListener fails to activate conversation context
if a conversation is not found by the supplied conversation id. This problem is
potentially related to [SEAMCATCH-46],[WELD-855].
JSR-299 6.7.4 Conversation context lifecycle has a requirement that 'If the propagated
conversation cannot be restored, the container _must associate the request with a new
transient conversation_ and throw an exception of type
javax.enterprise.context.NonexistentConversationException from the restore view phase of
the JSF lifecycle.'. However, the implementation of
org.jboss.weld.jsf.WeldPhaseListener.activateConversations fails to do that if a
conversation is not found by the conversation id.
{code}
private void activateConversations(FacesContext facesContext)
{
ConversationContext conversationContext =
instance().select(HttpConversationContext.class).get();
String cid = getConversationId(facesContext, conversationContext);
log.debug(RESUMING_CONVERSATION, cid);
if (cid != null && conversationContext.getConversation(cid) == null)
{
throw new NonexistentConversationException(NO_CONVERSATION_FOUND_TO_RESTORE,
cid);
}
conversationContext.activate(cid);
}
{code}
Recovering from the exception becomes difficult since the context is not active. Typical
symptom is 'java.lang.IllegalStateException: Unable to load current conversations from
the associated request, something went badly wrong when associate() was called
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:12 p.m.
New subject: [JBoss JIRA] Commented: (WELD-878) WeldPhaseListener fails to activate conversation context if conversation is not found
[
https://issues.jboss.org/browse/WELD-878?page=com.atlassian.jira.plugin.s...
]
Nicklas Karlsson commented on WELD-878:
---------------------------------------
Hmm. Yes. I think we could get away with just calling conversationContext.activate()
before throwing the exception since that is a passthrough to
conversationContext.activate(null) which should use a temp BeanStore for the transient
conversation.
WeldPhaseListener fails to activate conversation context if
conversation is not found
-------------------------------------------------------------------------------------
Key: WELD-878
URL: https://issues.jboss.org/browse/WELD-878
Project: Weld
Issue Type: Bug
Components: Conversations, Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.1.0.Final
Environment: Glassfish 3.1 B43 updated with weld-1.1.0-SNAPSHOT
(weld-osgi-bundle-1.1.0-20110329.041630-9.jar)
Reporter: Jarkko Hyöty
It seems that org.jboss.weld.jsf.WeldPhaseListener fails to activate conversation context
if a conversation is not found by the supplied conversation id. This problem is
potentially related to [SEAMCATCH-46],[WELD-855].
JSR-299 6.7.4 Conversation context lifecycle has a requirement that 'If the
propagated conversation cannot be restored, the container _must associate the request with
a new transient conversation_ and throw an exception of type
javax.enterprise.context.NonexistentConversationException from the restore view phase of
the JSF lifecycle.'. However, the implementation of
org.jboss.weld.jsf.WeldPhaseListener.activateConversations fails to do that if a
conversation is not found by the conversation id.
{code}
private void activateConversations(FacesContext facesContext)
{
ConversationContext conversationContext =
instance().select(HttpConversationContext.class).get();
String cid = getConversationId(facesContext, conversationContext);
log.debug(RESUMING_CONVERSATION, cid);
if (cid != null && conversationContext.getConversation(cid) == null)
{
throw new NonexistentConversationException(NO_CONVERSATION_FOUND_TO_RESTORE,
cid);
}
conversationContext.activate(cid);
}
{code}
Recovering from the exception becomes difficult since the context is not active. Typical
symptom is 'java.lang.IllegalStateException: Unable to load current conversations from
the associated request, something went badly wrong when associate() was called
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:13 a.m.
New subject: [JBoss JIRA] Updated: (WELD-878) WeldPhaseListener fails to activate conversation context if conversation is not found
[
https://issues.jboss.org/browse/WELD-878?page=com.atlassian.jira.plugin.s...
]
Jarkko Hyöty updated WELD-878:
------------------------------
Affects Version/s: 1.1.1.Final
Environment: Glassfish 3.1 B43 updated with weld-1.1.1 (was: Glassfish 3.1 B43
updated with weld-1.1.0-SNAPSHOT (weld-osgi-bundle-1.1.0-20110329.041630-9.jar))
Still present in 1.1.1-Final.
WeldPhaseListener fails to activate conversation context if
conversation is not found
-------------------------------------------------------------------------------------
Key: WELD-878
URL: https://issues.jboss.org/browse/WELD-878
Project: Weld
Issue Type: Bug
Components: Conversations, Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.1.0.Final, 1.1.1.Final
Environment: Glassfish 3.1 B43 updated with weld-1.1.1
Reporter: Jarkko Hyöty
It seems that org.jboss.weld.jsf.WeldPhaseListener fails to activate conversation context
if a conversation is not found by the supplied conversation id. This problem is
potentially related to [SEAMCATCH-46],[WELD-855].
JSR-299 6.7.4 Conversation context lifecycle has a requirement that 'If the
propagated conversation cannot be restored, the container _must associate the request with
a new transient conversation_ and throw an exception of type
javax.enterprise.context.NonexistentConversationException from the restore view phase of
the JSF lifecycle.'. However, the implementation of
org.jboss.weld.jsf.WeldPhaseListener.activateConversations fails to do that if a
conversation is not found by the conversation id.
{code}
private void activateConversations(FacesContext facesContext)
{
ConversationContext conversationContext =
instance().select(HttpConversationContext.class).get();
String cid = getConversationId(facesContext, conversationContext);
log.debug(RESUMING_CONVERSATION, cid);
if (cid != null && conversationContext.getConversation(cid) == null)
{
throw new NonexistentConversationException(NO_CONVERSATION_FOUND_TO_RESTORE,
cid);
}
conversationContext.activate(cid);
}
{code}
Recovering from the exception becomes difficult since the context is not active. Typical
symptom is 'java.lang.IllegalStateException: Unable to load current conversations from
the associated request, something went badly wrong when associate() was called
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 a.m.
New subject: [JBoss JIRA] Commented: (WELD-878) WeldPhaseListener fails to activate conversation context if conversation is not found
[
https://issues.jboss.org/browse/WELD-878?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on WELD-878:
------------------------------------
This seems to be killing the viewAction from Seam Faces, preventing the viewAction
component from performing navigations. Can we re-assess the priority of resolving this?
Many eyes are looking at the viewAction right now, for possible inclusion in JSF 2.2.
I have a JSFUnit/Arquillian test in a feature branch of Seam Faces demonstrating this
failure. Please let me know if you would like details on running this test (building
JSFUnit is required at the moment).
WeldPhaseListener fails to activate conversation context if
conversation is not found
-------------------------------------------------------------------------------------
Key: WELD-878
URL: https://issues.jboss.org/browse/WELD-878
Project: Weld
Issue Type: Bug
Components: Conversations, Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.1.0.Final, 1.1.1.Final
Environment: Glassfish 3.1 B43 updated with weld-1.1.1
Reporter: Jarkko Hyöty
It seems that org.jboss.weld.jsf.WeldPhaseListener fails to activate conversation context
if a conversation is not found by the supplied conversation id. This problem is
potentially related to [SEAMCATCH-46],[WELD-855].
JSR-299 6.7.4 Conversation context lifecycle has a requirement that 'If the
propagated conversation cannot be restored, the container _must associate the request with
a new transient conversation_ and throw an exception of type
javax.enterprise.context.NonexistentConversationException from the restore view phase of
the JSF lifecycle.'. However, the implementation of
org.jboss.weld.jsf.WeldPhaseListener.activateConversations fails to do that if a
conversation is not found by the conversation id.
{code}
private void activateConversations(FacesContext facesContext)
{
ConversationContext conversationContext =
instance().select(HttpConversationContext.class).get();
String cid = getConversationId(facesContext, conversationContext);
log.debug(RESUMING_CONVERSATION, cid);
if (cid != null && conversationContext.getConversation(cid) == null)
{
throw new NonexistentConversationException(NO_CONVERSATION_FOUND_TO_RESTORE,
cid);
}
conversationContext.activate(cid);
}
{code}
Recovering from the exception becomes difficult since the context is not active. Typical
symptom is 'java.lang.IllegalStateException: Unable to load current conversations from
the associated request, something went badly wrong when associate() was called
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:01 p.m.
New subject: [JBoss JIRA] Commented: (WELD-878) WeldPhaseListener fails to activate conversation context if conversation is not found
[
https://issues.jboss.org/browse/WELD-878?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on WELD-878:
------------------------------------
Nevermind, Pete pointed out to me that the issue I am observing is most likely unrelated
to this issuse. Apologies for the Jira SPAM :)
WeldPhaseListener fails to activate conversation context if
conversation is not found
-------------------------------------------------------------------------------------
Key: WELD-878
URL: https://issues.jboss.org/browse/WELD-878
Project: Weld
Issue Type: Bug
Components: Conversations, Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.1.0.Final, 1.1.1.Final
Environment: Glassfish 3.1 B43 updated with weld-1.1.1
Reporter: Jarkko Hyöty
It seems that org.jboss.weld.jsf.WeldPhaseListener fails to activate conversation context
if a conversation is not found by the supplied conversation id. This problem is
potentially related to [SEAMCATCH-46],[WELD-855].
JSR-299 6.7.4 Conversation context lifecycle has a requirement that 'If the
propagated conversation cannot be restored, the container _must associate the request with
a new transient conversation_ and throw an exception of type
javax.enterprise.context.NonexistentConversationException from the restore view phase of
the JSF lifecycle.'. However, the implementation of
org.jboss.weld.jsf.WeldPhaseListener.activateConversations fails to do that if a
conversation is not found by the conversation id.
{code}
private void activateConversations(FacesContext facesContext)
{
ConversationContext conversationContext =
instance().select(HttpConversationContext.class).get();
String cid = getConversationId(facesContext, conversationContext);
log.debug(RESUMING_CONVERSATION, cid);
if (cid != null && conversationContext.getConversation(cid) == null)
{
throw new NonexistentConversationException(NO_CONVERSATION_FOUND_TO_RESTORE,
cid);
}
conversationContext.activate(cid);
}
{code}
Recovering from the exception becomes difficult since the context is not active. Typical
symptom is 'java.lang.IllegalStateException: Unable to load current conversations from
the associated request, something went badly wrong when associate() was called
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:21 a.m.
New subject: [JBoss JIRA] Commented: (WELD-878) WeldPhaseListener fails to activate conversation context if conversation is not found
[
https://issues.jboss.org/browse/WELD-878?page=com.atlassian.jira.plugin.s...
]
Martin Kouba commented on WELD-878:
-----------------------------------
Still present in 1.1.2.Final (JBoss AS7). Also causes CDI TCK test failure in 1.1 branch.
WeldPhaseListener fails to activate conversation context if
conversation is not found
-------------------------------------------------------------------------------------
Key: WELD-878
URL: https://issues.jboss.org/browse/WELD-878
Project: Weld
Issue Type: Bug
Components: Conversations, Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.1.0.Final, 1.1.1.Final
Environment: Glassfish 3.1 B43 updated with weld-1.1.1
Reporter: Jarkko Hyöty
It seems that org.jboss.weld.jsf.WeldPhaseListener fails to activate conversation context
if a conversation is not found by the supplied conversation id. This problem is
potentially related to [SEAMCATCH-46],[WELD-855].
JSR-299 6.7.4 Conversation context lifecycle has a requirement that 'If the
propagated conversation cannot be restored, the container _must associate the request with
a new transient conversation_ and throw an exception of type
javax.enterprise.context.NonexistentConversationException from the restore view phase of
the JSF lifecycle.'. However, the implementation of
org.jboss.weld.jsf.WeldPhaseListener.activateConversations fails to do that if a
conversation is not found by the conversation id.
{code}
private void activateConversations(FacesContext facesContext)
{
ConversationContext conversationContext =
instance().select(HttpConversationContext.class).get();
String cid = getConversationId(facesContext, conversationContext);
log.debug(RESUMING_CONVERSATION, cid);
if (cid != null && conversationContext.getConversation(cid) == null)
{
throw new NonexistentConversationException(NO_CONVERSATION_FOUND_TO_RESTORE,
cid);
}
conversationContext.activate(cid);
}
{code}
Recovering from the exception becomes difficult since the context is not active. Typical
symptom is 'java.lang.IllegalStateException: Unable to load current conversations from
the associated request, something went badly wrong when associate() was called
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:30 a.m.
New subject: [JBoss JIRA] Updated: (WELD-878) WeldPhaseListener fails to activate conversation context if conversation is not found
[
https://issues.jboss.org/browse/WELD-878?page=com.atlassian.jira.plugin.s...
]
Nicklas Karlsson updated WELD-878:
----------------------------------
Git Pull Request: https://github.com/weld/core/pull/136
WeldPhaseListener fails to activate conversation context if
conversation is not found
-------------------------------------------------------------------------------------
Key: WELD-878
URL: https://issues.jboss.org/browse/WELD-878
Project: Weld
Issue Type: Bug
Components: Conversations, Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.1.0.Final, 1.1.1.Final
Environment: Glassfish 3.1 B43 updated with weld-1.1.1
Reporter: Jarkko Hyöty
It seems that org.jboss.weld.jsf.WeldPhaseListener fails to activate conversation context
if a conversation is not found by the supplied conversation id. This problem is
potentially related to [SEAMCATCH-46],[WELD-855].
JSR-299 6.7.4 Conversation context lifecycle has a requirement that 'If the
propagated conversation cannot be restored, the container _must associate the request with
a new transient conversation_ and throw an exception of type
javax.enterprise.context.NonexistentConversationException from the restore view phase of
the JSF lifecycle.'. However, the implementation of
org.jboss.weld.jsf.WeldPhaseListener.activateConversations fails to do that if a
conversation is not found by the conversation id.
{code}
private void activateConversations(FacesContext facesContext)
{
ConversationContext conversationContext =
instance().select(HttpConversationContext.class).get();
String cid = getConversationId(facesContext, conversationContext);
log.debug(RESUMING_CONVERSATION, cid);
if (cid != null && conversationContext.getConversation(cid) == null)
{
throw new NonexistentConversationException(NO_CONVERSATION_FOUND_TO_RESTORE,
cid);
}
conversationContext.activate(cid);
}
{code}
Recovering from the exception becomes difficult since the context is not active. Typical
symptom is 'java.lang.IllegalStateException: Unable to load current conversations from
the associated request, something went badly wrong when associate() was called
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:14 p.m.
New subject: [JBoss JIRA] Resolved: (WELD-878) WeldPhaseListener fails to activate conversation context if conversation is not found
[
https://issues.jboss.org/browse/WELD-878?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas resolved WELD-878.
---------------------------------
Fix Version/s: 1.2.0.Beta1
Resolution: Done
WeldPhaseListener fails to activate conversation context if
conversation is not found
-------------------------------------------------------------------------------------
Key: WELD-878
URL: https://issues.jboss.org/browse/WELD-878
Project: Weld
Issue Type: Bug
Components: Conversations, Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.1.0.Final, 1.1.1.Final
Environment: Glassfish 3.1 B43 updated with weld-1.1.1
Reporter: Jarkko Hyöty
Fix For: 1.2.0.Beta1
It seems that org.jboss.weld.jsf.WeldPhaseListener fails to activate conversation context
if a conversation is not found by the supplied conversation id. This problem is
potentially related to [SEAMCATCH-46],[WELD-855].
JSR-299 6.7.4 Conversation context lifecycle has a requirement that 'If the
propagated conversation cannot be restored, the container _must associate the request with
a new transient conversation_ and throw an exception of type
javax.enterprise.context.NonexistentConversationException from the restore view phase of
the JSF lifecycle.'. However, the implementation of
org.jboss.weld.jsf.WeldPhaseListener.activateConversations fails to do that if a
conversation is not found by the conversation id.
{code}
private void activateConversations(FacesContext facesContext)
{
ConversationContext conversationContext =
instance().select(HttpConversationContext.class).get();
String cid = getConversationId(facesContext, conversationContext);
log.debug(RESUMING_CONVERSATION, cid);
if (cid != null && conversationContext.getConversation(cid) == null)
{
throw new NonexistentConversationException(NO_CONVERSATION_FOUND_TO_RESTORE,
cid);
}
conversationContext.activate(cid);
}
{code}
Recovering from the exception becomes difficult since the context is not active. Typical
symptom is 'java.lang.IllegalStateException: Unable to load current conversations from
the associated request, something went badly wrong when associate() was called
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:13 a.m.
New subject: [JBoss JIRA] Updated: (WELD-878) WeldPhaseListener fails to activate conversation context if conversation is not found
[
https://issues.jboss.org/browse/WELD-878?page=com.atlassian.jira.plugin.s...
]
Ales Justin updated WELD-878:
-----------------------------
Assignee: Stuart Douglas
Git Pull Request: https://github.com/weld/core/pull/136 (was:
https://github.com/weld/core/pull/136)
WeldPhaseListener fails to activate conversation context if
conversation is not found
-------------------------------------------------------------------------------------
Key: WELD-878
URL: https://issues.jboss.org/browse/WELD-878
Project: Weld
Issue Type: Bug
Components: Conversations, Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.1.0.Final, 1.1.1.Final
Environment: Glassfish 3.1 B43 updated with weld-1.1.1
Reporter: Jarkko Hyöty
Assignee: Stuart Douglas
Fix For: 1.2.0.Beta1
It seems that org.jboss.weld.jsf.WeldPhaseListener fails to activate conversation context
if a conversation is not found by the supplied conversation id. This problem is
potentially related to [SEAMCATCH-46],[WELD-855].
JSR-299 6.7.4 Conversation context lifecycle has a requirement that 'If the
propagated conversation cannot be restored, the container _must associate the request with
a new transient conversation_ and throw an exception of type
javax.enterprise.context.NonexistentConversationException from the restore view phase of
the JSF lifecycle.'. However, the implementation of
org.jboss.weld.jsf.WeldPhaseListener.activateConversations fails to do that if a
conversation is not found by the conversation id.
{code}
private void activateConversations(FacesContext facesContext)
{
ConversationContext conversationContext =
instance().select(HttpConversationContext.class).get();
String cid = getConversationId(facesContext, conversationContext);
log.debug(RESUMING_CONVERSATION, cid);
if (cid != null && conversationContext.getConversation(cid) == null)
{
throw new NonexistentConversationException(NO_CONVERSATION_FOUND_TO_RESTORE,
cid);
}
conversationContext.activate(cid);
}
{code}
Recovering from the exception becomes difficult since the context is not active. Typical
symptom is 'java.lang.IllegalStateException: Unable to load current conversations from
the associated request, something went badly wrong when associate() was called
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4812
days inactive
4988
days old
8 comments
6 participants
participants (6)
-
Ales Justin (JIRA) -
Brian Leathem (JIRA)
-
Jarkko Hyöty (JIRA)
-
Martin Kouba (JIRA)
-
Nicklas Karlsson (JIRA)
-
Stuart Douglas (JIRA)