Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 29872 invoked from network); 3 Nov 2010 02:57:18 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Nov 2010 02:57:18 -0000 Received: (qmail 58386 invoked by uid 500); 3 Nov 2010 02:57:49 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 58113 invoked by uid 500); 3 Nov 2010 02:57:49 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 58106 invoked by uid 99); 3 Nov 2010 02:57:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Nov 2010 02:57:49 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of xhhsld@gmail.com designates 209.85.214.182 as permitted sender) Received: from [209.85.214.182] (HELO mail-iw0-f182.google.com) (209.85.214.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Nov 2010 02:57:41 +0000 Received: by iwn39 with SMTP id 39so138275iwn.13 for ; Tue, 02 Nov 2010 19:57:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=BrRW4kESuXPhgXUGqDAOcNkg8MBEHDHwhYFnejNKr4M=; b=h/IfYy4BALrUtVrez2fYoTIbNR2hLvEKZn8o9gHvIAN+r1o891uRCnPUfaQoAXB4tI uT92Y2qzSTd+BxdXQzzVpxoTKGd3aVtc906K6+isXI4TD6/SvWck8lnyPi2I9mQvY57f jhnkOC9xChnd+WzlFBxEvnZO7mkZC50ZN5zfQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ZSgtUCCBkqIWi+TpuiiHizggr7uAR4Gk6+6nm+eDnX2OKvRRBARKxa5YYCl4QDdUau IxAZ6Rf4R0n71lpYBp+C6zK8FvaJiSIPpaxulWPpqECNrWhjRI/Si/GFDzN1EcownXY3 fbdpXUa3xWvTIYAOyxCYjngfOfutzMxzNOhSI= MIME-Version: 1.0 Received: by 10.42.12.138 with SMTP id y10mr4364413icy.128.1288753039932; Tue, 02 Nov 2010 19:57:19 -0700 (PDT) Received: by 10.231.13.71 with HTTP; Tue, 2 Nov 2010 19:57:19 -0700 (PDT) In-Reply-To: References: <81514878-5B2B-4337-8C78-EFCB80B717C9@yahoo.com> Date: Wed, 3 Nov 2010 10:57:19 +0800 Message-ID: Subject: Re: Changes in processing faces-config.xml in non-app bundles? From: Ivan To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=20cf301d3d9a25fd4704941d3365 X-Virus-Checked: Checked by ClamAV on apache.org --20cf301d3d9a25fd4704941d3365 Content-Type: text/plain; charset=ISO-8859-1 I think I have fixed the JSF TCK cases, there is a typo error :-( Not sure whether it is helpful for the failed web beans cases. 2010/11/2 Ivan > OK, I will check it, do you mean the TCK cases ? > > 2010/11/2 Jarek Gawor > > I don't know if that's related but the myfaces testsuite failed in >> trunk. Which probably means there is some regression somewhere. >> >> Jarek >> >> On Tue, Nov 2, 2010 at 12:30 AM, Ivan wrote: >> > Hmm... >> > If the reason is that the faces-config.xml file is in the >> webbeans-jsf.jar, >> > it should not work in the past, as MyFaces seems have no chance to read >> it >> > in the OSGI environment, except for the jar file is in the WEB-INF/lib >> > folder. The current done JSF integration changes were to use MyFaces SPI >> to >> > configure application resources and annotations. >> > >> > 2010/11/2 David Jencks >> >> >> >> The jetty and tomcat owb integrations now have about the same 23 or 24 >> >> failures. 22 of them appear to be because a jsf phase listener isn't >> >> getting installed in myfaces whereas I think it was a few days ago when >> I >> >> had no tomcat failures. >> >> >> >> The faces-config.xml is in the webbeans-jsf jar. >> >> >> >> I haven't reviewed the recent myfaces integration changes yet.... is it >> >> plausible that they could have caused this problem? Is there something >> we >> >> need to do to explicitly register our interest in having this >> faces-config >> >> file processed? >> >> >> >> thanks >> >> david jencks >> >> >> > >> > >> > >> > -- >> > Ivan >> > >> > > > > -- > Ivan > -- Ivan --20cf301d3d9a25fd4704941d3365 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I think I have fixed the JSF TCK cases, there is a typo error :-(
Not su= re whether it is helpful for the failed web beans cases.

2010/11/2 Ivan <xhhsld@gmail.com>
OK, I will check = it, do you mean the TCK cases ?

2010/11/2= Jarek Gawor <jgawor@gmail.com>

I don't know if that's related but the myfaces testsuite failed in<= br> trunk. Which probably means there is some regression somewhere.

Jarek

On Tue, Nov 2, 2010 at 12:30 AM, Ivan <xhhsld@gmail.com> wrote:
> Hmm...
> If the reason is that the faces-config.xml file is in the webbeans-jsf= .jar,
> it should not work in the past, as MyFaces seems have no chance to rea= d it
> in the OSGI environment, except for the jar file is in the WEB-INF/lib=
> folder. The current done JSF integration changes were to use MyFaces S= PI to
> configure application resources and annotations.
>
> 2010/11/2 David Jencks <david_jencks@yahoo.com>
>>
>> The jetty and tomcat owb integrations now have about the same 23 o= r 24
>> failures. =A022 of them appear to be because a jsf phase listener = isn't
>> getting installed in myfaces whereas I think it was a few days ago= when I
>> had no tomcat failures.
>>
>> The faces-config.xml is in the webbeans-jsf jar.
>>
>> I haven't reviewed the recent myfaces integration changes yet.= ... is it
>> plausible that they could have caused this problem? =A0Is there so= mething we
>> need to do to explicitly register our interest in having this face= s-config
>> file processed?
>>
>> thanks
>> david jencks
>>
>
>
>
> --
> Ivan
>



-- Ivan



--
Ivan
--20cf301d3d9a25fd4704941d3365--