> Sorry, it's only post JBoss AS 4.2.3 that JSF 1.2.10 was included,
> 4.2.3 has 1.2.09...
You need to spoon feed me here - i'm still groggy from friday ;)
This means Seam 2.1.1 won't work on any current community released
JBoss AS 4.2.x
if it uses meta-inf to declare dependencies ?
/max
>
> On 7 Apr 2009, at 12:44, Max Rydahl Andersen wrote:
>
>>
>> ----- "Pete Muir" <pmuir(a)redhat.com> wrote:
>>
>>> Here is the canonical JIRA
https://jira.jboss.org/jira/browse/
>>> JBIDE-2190, and the answer is given by the OP - this was an issue
>
>>> with
>>>
>>> JSF < 1.2_10, the first version of JBoss AS that incorporates this
> is
>>>
>>> 4.2.3 or 5.
>>
>> He *is* using 4.2.3:
>>
>> "Deployed to JBoss AS 4.2.3.GA."
>>
>> Any other suggestions ? :)
>
> Upgrade JSF to 1.2.10 or later? Bug JBoss AS team for a release? Use
>
> JBoss 5?
>
>>
>>
>>> There is no Seam version that fixes this, as it's not a bug in
> Seam
>>> (nb Seam had a related problem, but we fixed that for 2.1.0).
>>>
>>> Really, I would recommend that you switch to not using MANIFEST.MF
>
>>> for
>>>
>>> defining the classpath of apps, but instead use lib/ directories.
>>>
https://jira.jboss.org/jira/browse/JBIDE-4136
>>
>> Using meta-inf is spec and should just work. Plus it is what all
>> IDE's supports and
>> it is not available for J2EE 1.4 apps.
>
> Right, but it's not recommended packaging for Seam apps. However, we
>
> are doing our best to support it - just you need to use newer
> versions
>
> of stuff...
>
>>
>>
>> I'm fighting hard with Eclipse to fix their broken lib support but
>
>> until
>> then my hands are tied in that direction.
>>
>> /max
>>
>>>
>>> On 7 Apr 2009, at 09:33, Max Rydahl Andersen wrote:
>>>
>>>> Hi guys,
>>>>
>>>> Please see
>>>
>
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223780#...
>>>>
>>>> We keep bumping into this "two listener instances installed"
on
> Seam
>>>
>>>> 2.1.x.
>>>>
>>>> Remind me again why this happens on deployments that works great
> on
>>>
>>>> all previous versions of Seam ?
>>>>
>>>> Can I point users to Seam 2.1.2 builds that will fix this ?
>>>>
>>>> /max
>>>> _______________________________________________
>>>> seam-dev mailing list
>>>> seam-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>> --
>>> Pete Muir
>>>
http://www.seamframework.org
>>>
http://in.relation.to/Bloggers/Pete
>
> --
> Pete Muir
>
http://www.seamframework.org
>
http://in.relation.to/Bloggers/Pete