From dev-return-45419-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Mon Feb 05 17:36:48 2007 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 55171 invoked from network); 5 Feb 2007 17:36:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Feb 2007 17:36:47 -0000 Received: (qmail 8129 invoked by uid 500); 5 Feb 2007 17:36:51 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 8086 invoked by uid 500); 5 Feb 2007 17:36:51 -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 8072 invoked by uid 99); 5 Feb 2007 17:36:51 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Feb 2007 09:36:51 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [209.181.65.237] (HELO sun.savoirtech.com) (209.181.65.237) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 05 Feb 2007 09:36:40 -0800 Received: from [206.197.197.25] ([206.197.197.25]) (authenticated bits=0) by sun.savoirtech.com (8.13.8/8.13.8) with ESMTP id l15HaIAI025364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 5 Feb 2007 10:36:18 -0700 Message-ID: <45C76B18.2010607@apache.org> Date: Mon, 05 Feb 2007 10:36:24 -0700 From: Jeff Genender Reply-To: jgenender@apache.org Organization: Apache Geronimo User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: in jetty-deployer plan.xml References: <5eb405c70702012007va7cfe67x7657db12fe35628f@mail.gmail.com> <5B0918C3-B814-420B-A3C9-D09F85D30D2C@iq80.com> In-Reply-To: <5B0918C3-B814-420B-A3C9-D09F85D30D2C@iq80.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on sun.savoirtech.com X-Virus-Scanned: ClamAV 0.88.7/2524/Mon Feb 5 05:48:22 2007 on sun.savoirtech.com X-Virus-Status: Clean X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-104.0 required=5.6 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.1.7 That was an issue with Hibernate and Spring, that's why it was there. It should be removable as I did it for Tomcat a while back after we found Liferay wasn't working with it in there. Dain Sundstrom wrote: > Tranql uses antlr, but there may be something else that does (maybe > spring). > > -dain > > On Feb 4, 2007, at 3:13 AM, Gianny Damour wrote: > >> Hi Jarek, >> >> I think the Spring filter is a leftover of the time when the Jetty >> module was used to import Spring to configure WADI. >> >> I do not know why antlr is there. As it is not directly imported by >> Jetty6 poms, I think that we can also drop it. >> >> Thanks, >> Gianny >> >> On 02/02/2007, at 3:07 PM, Jarek Gawor wrote: >> >>> Hi, >>> >>> I have a question about the following entry in the >>> configs/jett6-deployer/src/plan/plan.xml: >>> >>> >>> antlr. >>> org.springframework. >>> >>> >>> Is that still needed/necessary? tomcat6-deployer's plan.xml does not >>> have such entry. So is this jetty specific? I believe this is causing >>> problems for me with a WS client code that uses Spring API to >>> configure itself (a WS client gets an automatic dependency on CXF >>> which then has a dependency on the Spring API). >>> >>> Can someone please explain? >>> >>> Thanks, >>> Jarek >>