[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3363) Exploaded deployment and jboss-seam.jar on the classpath causes Multiple SeamPhaseListeners

[Pete Muir (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12427578#action_12427578 ] 

Pete Muir commented on JBSEAM-3363:
-----------------------------------

The problem is referencing jboss-seam.jar as an ejb module in application.xml AND putting it in the MANIFEST.MF of the ejb module's MANIFEST.MF

This causes JSF to detect the faces-config.xml we have in jboss-seam.jar!/META-INF/faces-config.xml twice.

> Exploaded deployment and jboss-seam.jar on the classpath causes Multiple SeamPhaseListeners
> -------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-3363
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3363
>             Project: Seam
>          Issue Type: Bug
>         Environment: Windows XP, Java5, JBoss AS 4.2.3.GA
>            Reporter: Bernard Labno
>            Priority: Minor
>             Fix For: 2.0.1.CR1
>
>
> My EJB module has jboss-seam.jar on the Class-Path attribute in MANIFEST.MF. That is no problem when I deploy application as packaged archive, but when I deploy it as exploded directory jboss-seam.jar gets loaded twice which results in [SeamPhaseListener] There should only be one Seam phase listener per application.

-- 
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