Re: [seam-dev] java.lang.IllegalStateException: No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed))

> I see now that I worded this wrongly. > > What I meant was: > > If JBT packaging ends up with the deployment having 2 physical > seperate seam.jar jar's then that is wrong. > If JBT packaging ends up with the deployment having 1 physical jar, > referenced from MANIFEST.MF and application.ml then I can't fix that > - and would like to know why that is causing a failure (since it > shouldn't imo) I think that frameworks assume they will only get a resource back once from the classloader, not multiple times. We do in Seam, and JSF does too. As discussed, file an issue for both, it's easy to fix using an LinkedHashSet to remove dupes.