From dev-return-28693-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Fri Apr 28 02:21:25 2006 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 49725 invoked from network); 28 Apr 2006 02:21:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Apr 2006 02:21:25 -0000 Received: (qmail 85550 invoked by uid 500); 28 Apr 2006 02:21:14 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 85495 invoked by uid 500); 28 Apr 2006 02:21:13 -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 85478 invoked by uid 99); 28 Apr 2006 02:21:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Apr 2006 19:21:13 -0700 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of ammulder@gmail.com designates 64.233.166.181 as permitted sender) Received: from [64.233.166.181] (HELO pproxy.gmail.com) (64.233.166.181) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Apr 2006 19:21:12 -0700 Received: by pproxy.gmail.com with SMTP id t32so2095297pyc for ; Thu, 27 Apr 2006 19:20:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=JqotNFfGEGLQhq7Ok9iKojcCeDBDHXim4b3kBlCDZVFXi5wdo4s4KeAjc5VGFfdOgJ5AB5rpqk3w8RMzirjOt/OzLNnxLKI6it03iHebaeZR+CjnD1Rj+vMuhNEFOFoYzPpptM9KdsZAxYM4BAW/Y5H1fnFeQj38n04fcJ3ECTo= Received: by 10.35.31.14 with SMTP id i14mr45830pyj; Thu, 27 Apr 2006 19:20:52 -0700 (PDT) Received: by 10.35.116.1 with HTTP; Thu, 27 Apr 2006 19:20:52 -0700 (PDT) Message-ID: <74e15baa0604271920r20b30a7ah1f4473299fb475f0@mail.gmail.com> Date: Thu, 27 Apr 2006 22:20:52 -0400 From: "Aaron Mulder" Sender: ammulder@gmail.com To: dev@geronimo.apache.org Subject: Re: Release 1.1 - Question about Java 1.5 Warning message In-Reply-To: <44517B18.4090305@earthlink.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <44513B9E.2080900@hogstrom.org> <44517B18.4090305@earthlink.net> X-Google-Sender-Auth: 1616ca13ede11dce X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N FYI, if we distribute DayTrader as a plugin, we can tag it as running on JDK 1.4.* only, and then you won't be able to install it into a server running on 1.5. I think we should move the JDK 1.5 warning to a GBean we put in the j2ee-corba configuration, so if that configuration is started for any reason it will spew out the warning if running on JDK 1.5. Thanks, Aaron On 4/27/06, Joe Bohn wrote: > +1 on #3. We should not the JDK 1.5 concerns in the readme. > > I also like Dave Colasurdo's suggestion that we issue a warning message > if we can detect that we are running on JDK 1.5 and CORBA EJBs are being > used. Not sure how feasible (or visible) it will be to add those > warnings but it would be nice to have. > > Joe > > Matt Hogstrom wrote: > > All, > > > > I wanted to clarify what our plan is for the JVM Check that is done to > > verify that a user is running on Java 1.4. If someone chooses to accep= t > > the responsibility and use Java 1.5 it would be rather annoying to have > > this message come out every time. > > > > I think we have three options: > > > > 1. Leave it as is (warning comes out all the time) > > 2. Allow someone to set a property or other mechanism to tell the serve= r > > to not to issue the warning message. > > 3. Take the message out because 1.1 will tolerate 1.5 and we're not > > shipping DayTrader installed so the javax.xml.namespace.QName problem > > won't be visible. > > > > Personally I prefer 3 if there are no other issues. > > > > Thoughts? > > > > Matt > > > > > > -- > Joe Bohn > joe.bohn at earthlink.net > > "He is no fool who gives what he cannot keep, to gain what he cannot > lose." -- Jim Elliot >