[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4439) No Conversation Context error occurs when there is a separate faces-config.xml for an application because it causes the SeamPhaseListener to be added twice

Brian Sayrs (JIRA) jira-events at lists.jboss.org
Tue Oct 13 12:06:05 EDT 2009


   No Conversation Context error occurs when there is a separate faces-config.xml for an application because it causes  the SeamPhaseListener to be added twice
---------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBSEAM-4439
                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4439
             Project: Seam
          Issue Type: Task
    Affects Versions: 2.2.0.GA
         Environment: Seam on WebSphere
            Reporter: Brian Sayrs
            Priority: Minor




No Conversation Context error:

The jboss-seam.jar includes a faces-config.xml

adds the SeamPhaseListener.

If you have a separate faces-config.xml for your application and also

add the SeamPhaseListener, it  gets added twice.

Somehow this was causing the No Conversation Context error.

If you remove the phase listener from the faces-config.xml from

your application, everything  works

I think this should be added to the Seam documentation somewhere

the fact that the SeamPhaseListener has already been added

to the jboss-seam.jar and developers don't need to add it

to the faces-config.xml that is used by their application because

it appears to cause strange behavior.   This is also fixes problems
with the debug page. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the seam-issues mailing list