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

[Max Rydahl Andersen]

>> 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.
To follow up after talking with Pete and Snjezana and tested this again.

JBT does *not* put 2 separate seam-core.jar into the EAR - there is only 
one jar.

Something in JBoss Classloader is probably causing duplicate URL's to be 
returned. We'll investigate.

/max