[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
max.andersen at redhat.com
Thu Apr 9 07:58:00 EDT 2009
Max Rydahl Andersen wrote:
>>> Dan, as discussed before this is a broken design - duplicates on a
>>> classpath is not illegal; only the first one should be listened to
>>> AFAIK.
>>>
>>> Snjezana, if you remove the seam.jar from web-inf/lib does the
>>> compilation still work ? Or is it WTP that is putting it in there
>>> for us ?
>>
>> The compilation always works.
>> WTP is not putting this file in there. It is possible that earlier
>> versions of JBoss Tools (before releasing JBoss AS 4.2.3) were
>> copying the file to WEB-INF/lib.
> I don't think JBoss tools changed behavior in this aspect. The
> question is if JBT EAR projects actually put the seam jar both in ear
> and in web-inf/lib in the projects (not the deploy).
> That should not have any sideeffects (but it does because of the way
> seam 2.1.x is doing things), but if that is the case then we can fix
> it by not having the web-inf/lib/seam.jar.
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)
/max
>
> /max
>> Snjeza
>>> /max
>>>> -Dan
>>>>
>>>> --
>>>> Dan Allen
>>>> Senior Software Engineer, Red Hat | Author of Seam in Action
>>>>
>>>> http://mojavelinux.com
>>>> http://mojavelinux.com/seaminaction
>>>> http://in.relation.to/Bloggers/Dan
>>>>
>>>> NOTE: While I make a strong effort to keep up with my email on a daily
>>>> basis, personal or other work matters can sometimes keep me away
>>>> from my email. If you contact me, but don't hear back for more than
>>>> a week,
>>>> it is very likely that I am excessively backlogged or the message was
>>>> caught in the spam filters. Please don't hesitate to resend a
>>>> message if
>>>> you feel that it did not reach my attention.
More information about the seam-dev
mailing list