Return-Path: X-Original-To: apmail-myfaces-users-archive@www.apache.org Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 91F0CDCDB for ; Wed, 24 Oct 2012 11:22:04 +0000 (UTC) Received: (qmail 79932 invoked by uid 500); 24 Oct 2012 11:22:04 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 79690 invoked by uid 500); 24 Oct 2012 11:22:03 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 79654 invoked by uid 99); 24 Oct 2012 11:22:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Oct 2012 11:22:02 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of smithh032772@gmail.com designates 209.85.212.171 as permitted sender) Received: from [209.85.212.171] (HELO mail-wi0-f171.google.com) (209.85.212.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Oct 2012 11:21:55 +0000 Received: by mail-wi0-f171.google.com with SMTP id hj13so3545218wib.0 for ; Wed, 24 Oct 2012 04:21:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=CgetmFh/pKE3fye8V8Rxy6gwZziYKte+rqTbdYr4iTU=; b=xoulp3QnyE6G2jNPYGGX+n6YR7YJ2/dELI4DM/Wcc7WL/ZoNFkhN1BfPSKklEY5r2B whGfI/31L9IP8HS6c+egXLzMqdhXli0egMOX8RdHCRE1OAatHQqpbT7lLkuBTCOvEb/5 9KHzUCWhRURDMKoBapMijUgPN3WNhW3Fblzyh1C4DCTFAnjHPp4t2uVz1/Xl8QTNF4Uk cnDO8nJXPI+R+wUEBynUA8X5bxYgnbzDR24DoWvW8ByQbBvZioLk0hQ1VWG7YixaQCwn orppTXWBbyYywADD/mvHUuZfijkktOZnNsoKvvZINtP+qlM+25h6qs/j83PeGA8nUmUu VPxg== MIME-Version: 1.0 Received: by 10.180.100.35 with SMTP id ev3mr1771473wib.7.1351077694994; Wed, 24 Oct 2012 04:21:34 -0700 (PDT) Received: by 10.194.152.69 with HTTP; Wed, 24 Oct 2012 04:21:34 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Oct 2012 07:21:34 -0400 Message-ID: Subject: Re: [ CODI ] JSF resource injection issue with Mojarra 2.1.8 and above From: "Howard W. Smith, Jr." To: MyFaces Discussion Content-Type: multipart/alternative; boundary=f46d044282a612fa5a04cccc4ab4 X-Virus-Checked: Checked by ClamAV on apache.org --f46d044282a612fa5a04cccc4ab4 Content-Type: text/plain; charset=ISO-8859-1 One last thing, I am only a user of MyFaces Core 2.1.9 at the moment. I'm not using CODI or any other MyFaces libraries at the present. On Wed, Oct 24, 2012 at 7:14 AM, Howard W. Smith, Jr. < smithh032772@gmail.com> wrote: > Gerhard, > > Interesting response and this is good to know. > > Stephen, > > Yes, it's me Howard (smithh032772) from PrimeFaces Core community forum. I > fully recommend Gerhard's suggestion. *Prior* to migrating from Mojarra > 2.1.7 to MyFaces 2.1.8, I had ui:include issues and had to customize or > tailor the PARTIAL_STATE_SAVING to true, server, and to index.xhtml, which > is the parent xhtml page that contains any/all other children xhtml pages > via ui:include src="#{bean.page}". Also, please note that I had all JSF > ViewScoped (non-CODI) beans except for UsersController and > PageNavigationController beans where were JSF SessionScoped. > > I'm sure you are aware of BalusC (on stackoverflow.com), I learned from > his posts and/or blogs that ViewScoped beans had issues with partial state > saving and ui:include, and I experienced all that, but I managed to get > things working while using Mojarra with the configuration I mentioned in > the previous paragraph. > > Also, immediately prior to migrating from Mojarra 2.1.7 to MyFaces 2.1.8, > I heard time-and-time-again of other expert JSF developers to 'try' MyFaces > where Mojarra may fail on AJAX updates/rendering, so I tried MyFaces 2.1.8, > after hearing that MyFaces 2.1.7+ has great performance with (AJAX) page > rendering over Mojarra. > > After migrating from Mojarra 2.1.7 to MyFaces 2.1.8, I decided to change > all my beans from ViewScoped to SessionScoped, because of errors/issues I > had migrating from Mojarra 2.1.7 to MyFaces 2.1.8 (I recently saw that > MyFaces 2.1.9 might have fixed that issue, something to do with EJB > injection, if I'm not mistaking). > > Anyway, after telling you all of this (above), my web.xml has the > following as I am now the happy and satisfied user of MyFaces 2.1.9 (and > previously and initially, MyFaces 2.1.8): > > > javax.faces.STATE_SAVING_METHOD > server > > > javax.faces.PARTIAL_STATE_SAVING > true > > > > > > > Howard > > > On Wed, Oct 24, 2012 at 7:00 AM, Stephen More wrote: > >> In my notes that was required because of a JSF 2.0 include bug I ran >> into. I will have to research the original ui:include bug, and turn >> this back to true to see if that bug comes back. >> >> -Thanks >> Stephen More >> >> >> On Wed, Oct 24, 2012 at 3:54 AM, Gerhard Petracek >> wrote: >> > hi stephen, >> > >> > if you remove: >> > >> > >> > javax.faces.PARTIAL_STATE_SAVING >> > false >> > >> > >> > everything works as expected. >> > >> > regards, >> > gerhard >> > >> > http://www.irian.at >> > >> > Your JSF/JavaEE powerhouse - >> > JavaEE Consulting, Development and >> > Courses in English and German >> > >> > Professional Support for Apache MyFaces >> > >> > >> > >> > 2012/10/24 Stephen More >> > >> >> Here is an example showing the issue: >> >> >> >> svn co https://maven-examples.googlecode.com/svn/trunk/prime-codi >> >> cd prime-codi >> >> mvn jetty:run >> >> >> >> http://127.0.0.1:9090/helloworld/index.jsf >> >> >> >> ( View page source == end of html file look like: >> >> ) >> >> >> >> Click "Count" so the Count increases to 0. >> >> >> >> Now view page source again...bottom now shows: >> >> >> >> > >> >> href="/helloworld/javax.faces.resource/primefaces.css.jsf?ln=primefaces" >> >> /> >> >> >> >> >> >> -Stephen More >> >> >> >> >> >> On Tue, Oct 23, 2012 at 11:02 AM, Gerhard Petracek >> >> wrote: >> >> > hi stephen, >> >> > >> >> > codi doesn't use that part of the jsf-api. >> >> > ed is currently working on [1], but besides that he isn't aware of an >> >> issue. >> >> > it would be great if you can provide a link to a sample application >> which >> >> > illustrates the issue. >> >> > >> >> > regards, >> >> > gerhard >> >> > >> >> > [1] http://java.net/jira/browse/JAVASERVERFACES-2552 >> >> > >> >> > http://www.irian.at >> >> > >> >> > Your JSF/JavaEE powerhouse - >> >> > JavaEE Consulting, Development and >> >> > Courses in English and German >> >> > >> >> > Professional Support for Apache MyFaces >> >> > >> >> > >> >> > 2012/10/23 Stephen More >> >> > >> >> >> I am having a JSF resource injection issue, and I think the bug may >> >> >> exist in CODI. >> >> >> >> >> >> Working scenarios will display jquery like this: >> >> >> ... >> >> >> ... >> >> >> >> >> >> Broken scenarios will display jquery at the very end of the html >> >> >> output like this: >> >> >> >> >> >> >> >> >> The component contains: >> >> >> @ResourceDependencies({ >> >> >> @ResourceDependency(library="primefaces", >> >> name="jquery/jquery.js"), >> >> >> @ResourceDependency(library="primefaces", >> name="primefaces.js") >> >> >> }) >> >> >> >> >> >> Working stacks: >> >> >> Mojarra 2.0.9 + weld + CODI >> >> >> Mojarra 2.1.6 + weld + CODI >> >> >> Mojarra 2.1.7 + weld + CODI >> >> >> Mojarra 2.1.13 >> >> >> >> >> >> Broken stacks: >> >> >> Mojarra 2.1.8 + weld + CODI >> >> >> Mojarra 2.1.10 + weld + CODI >> >> >> Mojarra 2.1.13 + weld + CODI >> >> >> Mojarra 2.1.13 + OpenWebBeans + CODI >> >> >> >> >> >> >> >> >> Is there some compatibility issue between Mojarra 2.1.8 and above >> and >> >> >> CODI 1.0.5 ? >> >> >> >> >> >> -Stephen More >> >> >> >> >> >> > > --f46d044282a612fa5a04cccc4ab4--