Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 43917 invoked by uid 500); 19 Jul 2001 14:27:13 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 43910 invoked from network); 19 Jul 2001 14:27:12 -0000 Received: from unknown (HELO sbs.network-sol.com) (195.152.139.202) by h31.sny.collab.net with SMTP; 19 Jul 2001 14:27:12 -0000 Received: by SBS with Internet Mail Service (5.5.2448.0) id <344J22AF>; Thu, 19 Jul 2001 15:10:14 +0100 Message-ID: <354983E1FD62D411BF4C00B0D03E1D6134EC3C@SBS> From: Paul Foxton To: "'tomcat-user@jakarta.apache.org'" Subject: RE: Class reloading Date: Thu, 19 Jul 2001 15:10:13 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N yes, I have 'reloadable' set to true in server.xml for my app directory (under webapps) but its never reloaded my bean classes without = restarting, servlets I havn't tried it with as yet. The question seemed to me to = relate to beans in JSPs. Sorry, I could have phrased my reply better : ) cheers, Paul > -----Original Message----- > From: Endre St=F8lsvik [mailto:Endre@Stolsvik.com] > Sent: 19 July 2001 15:10 > To: 'tomcat-user@jakarta.apache.org' > Subject: Re: Class reloading >=20 >=20 > On Thu, 19 Jul 2001, Paul Foxton wrote: >=20 > | AFAIK tomcat doesn't support automatic reloading of=20 > classes. You do have to > | restart. >=20 > AFAIK all tomcats does support automatic reload, but it (at least = 3.2) > sucks. If you have "very plain servlets", which doesn't put=20 > many "real" > objects into the HttpSession (just Strings, Longs and the=20 > like), then it > works pretty good. But if you try to use selfmade objects,=20 > you get hit by > severe ClassLoader issues (You'll get ClassCastExceptions all=20 > the time). >=20 > Tomcat 4 should work, but I haven't tested it yet. It uses a=20 > funky scheme > of serializing the whole Sessions stuff, and restarting the=20 > whole webapp, > and then "booting" it up again. What happens with singletons,=20 > I ask, but > haven't tested it yet, as mentioned. >=20 > Look at tomcat's xml configure file, it's a 'ish=20 > parameter, > turn it to true.. >=20 > --=20 > Mvh, > Endre >=20