Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 34656 invoked from network); 7 May 2003 16:48:35 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 7 May 2003 16:48:35 -0000 Received: (qmail 17023 invoked by uid 97); 7 May 2003 16:50:39 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 17016 invoked from network); 7 May 2003 16:50:39 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 7 May 2003 16:50:39 -0000 Received: (qmail 33218 invoked by uid 500); 7 May 2003 16:48:18 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 33207 invoked from network); 7 May 2003 16:48:18 -0000 Received: from host5.webserver1010.com (209.239.61.197) by daedalus.apache.org with SMTP; 7 May 2003 16:48:18 -0000 Received: from MOTIVUS (12.33.252.64.snet.net [64.252.33.12]) by host5.webserver1010.com (8.10.2/8.10.2) with ESMTP id h47GmKX24734 for ; Wed, 7 May 2003 12:48:20 -0400 From: "Brian McDonald" To: "'Tomcat Users List'" Subject: RE: Tomcat 4.1: non-LE or LE Date: Wed, 7 May 2003 12:48:35 -0400 Message-ID: <000001c314b8$804b43a0$0202a8c0@MOTIVUS> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal In-Reply-To: <5.2.0.9.2.20030507095312.03111c58@shell.visi.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4925.2800 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I imagine I don't need connection pooling at this stage of my = development. I'm more concerned - as I've written at the top of this thread - with = setting up a development environment for an end-to-end XML-based JSP application. And = even though I don't /need/ to integrate Tomcat with IIS5 on my W2K machine to = develop this app, it seems like a valuable exercise in and of itself. That said, = if it proves to be too maddening a process - I'll short circuit and go for = Tomcat standalone. I don't know very much about Java's XML processing capability. But it = sounds like Jacob is stating that I'll be able - at the very least - to use j2sdk1.4.x's Crimson. But what if I want Xerces? (Why wouldn't I?) Can I = add that capability to j2sdk1.4.x? I realize that these sound like questions = for a J2SE newsgroup... but can someone tell me specifically how choosing = Tomcat-LE will affect me in this regard - i.e., with regard to XML support? And, Yoav, I would prefer to get the download/install right /before/ I = bang my head against unnecessary problems. That's why I'm posting to = Tomcat-Users! Expert advice and insight! I'm a newbie not a newborn! Brian > -----Original Message----- > From: Jacob Kjome [mailto:hoju@visi.com]=20 > Sent: Wednesday, May 07, 2003 11:06 AM > To: Tomcat Users List > Subject: RE: Tomcat 4.1: non-LE or LE >=20 >=20 > At 09:07 AM 5/7/2003 -0400, you wrote: > >There are no ramifications [to using the Tomcat LE version]=20 > if you have > >JDK 1.4. That's why it's so > >simple ;) >=20 > Hi Yoav, >=20 > I beg to differ on this issue. There *are* ramifications to=20 > using the LE=20 > version because the way it is set up. The difference isn't=20 > just that=20 > Tomcat doesn't include libraries that the j2sdk1.4.x already=20 > provides. It=20 > excludes stuff like, for instance, commons-dbcp, so you when=20 > you try to use=20 > container managed connection pooling in Tomcat, it will just=20 > blow up at you=20 > at runtime. There are other similar cases that I won't=20 > detail here. Why=20 > these essential libraries are excluded as part of the LE=20 > release, I fail to=20 > understand....especially when the README pretty much talks about only=20 > excluding libraries that duplicate j2sdk1.4.x functionality. Quite=20 > misleading. Also, if your app requires Xerces (which it shouldn't,=20 > but....) then you will feel the ramifications since=20 > j2sdk1.4.x provides=20 > only Crimson. Xerces is probably also faster and more up to=20 > date with the=20 > specs since it is actively developed where Crimson=20 > development is pretty=20 > much stagnant. >=20 > These are the reasons why this thread continues on and on. I=20 > just use the=20 > full release of Tomcat because I want its full functionality=20 > and don't want=20 > to have to worry about things blowing up in my face when I=20 > use standard=20 > Tomcat features and have to wonder which commons-* libraries I'm=20 > missing. The download isn't that much bigger and it avoids a=20 > whole bunch=20 > of headaches. >=20 > My $0.02 >=20 > Jake=20 >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org