From adffaces-user-return-227-apmail-incubator-adffaces-user-archive=incubator.apache.org@incubator.apache.org Wed May 31 20:43:16 2006 Return-Path: Delivered-To: apmail-incubator-adffaces-user-archive@locus.apache.org Received: (qmail 98478 invoked from network); 31 May 2006 20:43:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 May 2006 20:43:16 -0000 Received: (qmail 38487 invoked by uid 500); 31 May 2006 20:43:16 -0000 Delivered-To: apmail-incubator-adffaces-user-archive@incubator.apache.org Received: (qmail 38465 invoked by uid 500); 31 May 2006 20:43:15 -0000 Mailing-List: contact adffaces-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: adffaces-user@incubator.apache.org Delivered-To: mailing list adffaces-user@incubator.apache.org Received: (qmail 38454 invoked by uid 99); 31 May 2006 20:43:15 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 May 2006 13:43:15 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of awiner@gmail.com designates 64.233.184.228 as permitted sender) Received: from [64.233.184.228] (HELO wr-out-0506.google.com) (64.233.184.228) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 May 2006 13:43:14 -0700 Received: by wr-out-0506.google.com with SMTP id i30so105315wra for ; Wed, 31 May 2006 13:42:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uf8WuITstsY/CvkZcBVpxtgrsh1swQHEe3mJuW5llSAwyqkisjhsRrUv3k1OIcnS+VCZmpncXSS3jvAe+sj/d3hS55VVQ8aIoFkIX+qI5W7UIQGDCt/PKzAFdCuQsMb/KXKJYCmWSwCxzwQw+NHbwz7FRwZSPfZJvRqM4UgsciU= Received: by 10.64.179.20 with SMTP id b20mr798756qbf; Wed, 31 May 2006 13:42:53 -0700 (PDT) Received: by 10.65.103.7 with HTTP; Wed, 31 May 2006 13:42:53 -0700 (PDT) Message-ID: <6dac79b90605311342o59f1e78bnbed3ce23a84664b2@mail.gmail.com> Date: Wed, 31 May 2006 13:42:53 -0700 From: "Adam Winer" To: adffaces-user@incubator.apache.org Subject: Re: Building ADF on JDK 1.4 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N There's a decent quantity of JDK 1.5 specific code in there; and JSF 1.2, which is our eventual target, will require JDK 1.5. I'm personally reluctant to put in the work to go back to JDK 1.4 just to undo that work when we move to JSF 1.2. When we do go to JSF 1.2, we'll certainly leave behind a JSF 1.1-based branch, since adoption of JSF 1.2 will take awhile. I'd be very happy to see others go through the JSF 1.1 branch to move it back to JDK 1.4. MyFaces core only requires JDK 1.3, but that's because JCP compatibility rules require this for a JSF 1.1 implementation. Dunno what Tobago requires. -- Adam On 5/31/06, Benj Fayle wrote: > I would prefer to see ADF remain 1.4 compliant for some time as well. We > are currently using Java 1.5 for many new projects but there are still a > large number of our enterprise customers who will continue to use Java > 1.4 for at least another year, possibly longer. It is for some of these > larger projects that ADF is particularly attractive but they are > restricted to Java 1.4. > > I would be willing to assist in this effort as well. > > Benj Fayle > > -----Original Message----- > From: Dan Robinson [mailto:dannyjrobinson@gmail.com] > Sent: Wednesday, May 31, 2006 12:35 PM > To: adffaces-user@incubator.apache.org > Subject: Re: Building ADF on JDK 1.4 > > Thanks for the clarification. Could someone confirm that this the final > decision for the Apache ADF code, or just the version as supplied by > Oracle. A recent email on the MyFaces list as of February Sean > Schofield > said > > "The ADF stuff is in incubation right now so there are all sorts of > possibilities for change. I envision a lively discussion where discuss > the > pros and cons of allowing tomahawk, tobago or adf to use jdk > 1.5functionality. Currently tomahawk does not have any jdk > 1.5 stuff (that I am aware of.)" > > We're really wanting to use ADF for our application development, but are > currently hampered by the JDK 1.5 requirement, given not all App Servers > have made it to this JDK yet. We're also wanting to deploy this > technology > to our existing users with 1.4 powered servers. > > I don't believe that MyFaces (as of 1.1.2) has mandated this JVM > version, so > it seems strange for a library that runs on MyFaces to have this > restriction. If there's support we could provide assistance in making > these > changes to allow 1.4. > > Thanks ... and I wait to be corrected ;-) > > D. > > On 5/26/06, Gabrielle Crawford wrote: > > > > ADF Faces requires 1.5. > > > > Thanks, > > > > Gabrielle > > > > Dan Robinson wrote: > > > > > Could anyone advise the steps to building ADF against JDK 1.4? I > have > > it > > > building correctly using the Maven Wiki instructions which seem to > > > rely on > > > JDK 1.5. > > > > > > Many thanks, > > > > > > D. > > > > > > > >