Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 7272 invoked from network); 5 Dec 2006 18:21:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Dec 2006 18:21:40 -0000 Received: (qmail 43245 invoked by uid 500); 5 Dec 2006 18:21:46 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 43196 invoked by uid 500); 5 Dec 2006 18:21:45 -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 43185 invoked by uid 99); 5 Dec 2006 18:21:45 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Dec 2006 10:21:45 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of paulmcmahan@gmail.com designates 66.249.92.171 as permitted sender) Received: from [66.249.92.171] (HELO ug-out-1314.google.com) (66.249.92.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Dec 2006 10:21:34 -0800 Received: by ug-out-1314.google.com with SMTP id m2so4295609ugc for ; Tue, 05 Dec 2006 10:21:13 -0800 (PST) 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=X2AnBZa2IT8ASVJZ981la8z3kvz4TDBCaF7sq/IDCtDvMCuR5pP1+DuCtscdfoiXjC1zjHzeHoe8UY/wMN13ZPmvu3zEbvi2RZfPyLJ2FME7EuA6HOb18rxdUpgCQaGGCR1MLLB6X/M5BSZfWnRiVrPWOnWWK1vbUqMAgp8wNIg= Received: by 10.67.22.14 with SMTP id z14mr14145740ugi.1165342873220; Tue, 05 Dec 2006 10:21:13 -0800 (PST) Received: by 10.66.249.9 with HTTP; Tue, 5 Dec 2006 10:21:13 -0800 (PST) Message-ID: <21df75940612051021g4a3c9e98sdbca47ef32dc29d4@mail.gmail.com> Date: Tue, 5 Dec 2006 13:21:13 -0500 From: "Paul McMahan" To: dev@geronimo.apache.org Subject: Re: Geronimo 2.0 Milestone's and how were doing In-Reply-To: <8F55614B-4E3C-4526-A503-AA1A56E4BF2F@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <54AFC3D6-0348-4BD4-BFFE-2091243A945B@hogstrom.org> <8F55614B-4E3C-4526-A503-AA1A56E4BF2F@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On 12/5/06, Kevan Miller wrote: > > Paul, Tomcat integration might have the most work to do for M1. How > is that looking? I have the JSP 2.1 and EL 1.0 specs checked in and published to the snapshot repo, reversioned to 1.0-SNAPSHOT this morning per Jason's advice. The annotation 1.0 and servlet 2.5 specs were already available thanks to Joe and Greg. In my local build I have tc6 running the web console OK in a new tomcat-jee5 assembly and the default app in the tomcat-minimal assembly. Deploying a simple 2.4 WAR from the CLI works. I'm pretty confident that I'll be able to commit this first stage of tomcat integration this week. Current issues: Deploying 2.5 servlets While tc6 deploys and runs 2.4 WARs ok I haven't tried deploying a 2.5 WAR yet. All the webapps in the tc6 dist use 2.4 so I really hope I'm not the first one trying this :-S I googled up some JEE5 servlet samples but they are tightly coupled with other new JEE5 stuff like JPA, EJB 3.0, etc, so I need something simpler. I'll probably end up adding some 2.5 content to our unit test cases and cross my fingers. Worst case scenario is that for M1 we'll have a 2.5 servlet engine that you can only deploy <=2.4. servlets to. Failing unit test- A unit tests in geronimo-tomcat fails intermittently apparently due to a change in how tc6 handles connections. Still investigating if its a bug in geronimo, tomcat or the unit test. For the initial checkin I may need to disable the unit test. Noise factor- Shutdown of the JEE5 assemblies generates a huge stack trace. Looks like tranql/derby is the culpirt and not tomcat but I'm not 100% sure. I'll probably have to commit while the stack trace still appears so others can have a look. Also I need to figure out how to avoid logging tomcat's INFO messages to the command window. Its really noisy right now. Best wishes, Paul