Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 80560 invoked from network); 15 Jul 2002 12:41:00 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Jul 2002 12:41:00 -0000 Received: (qmail 22430 invoked by uid 97); 15 Jul 2002 12:41:12 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 22414 invoked by uid 97); 15 Jul 2002 12:41:12 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 22402 invoked by uid 98); 15 Jul 2002 12:41:11 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <9B3E950CB293D411ADF4009027B0A4D2031F72F2@PARSV011> From: Stephane Bailliez To: Ant Developers List Subject: RE: Serializable Location? Date: Mon, 15 Jul 2002 13:52:25 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: Jonas G=F6ransson [mailto:jongo728@student.liu.se] > In my case it's only the convenience to be able to pass the=20 > BuildExceptions through to the client without having to > convert it into some serializable format. But the BuildException=20 > serialization will fail if the Throwable which might have > caused the exception isn't serializable so I would still have=20 > to perform a check in order to be safe. Yes and most of the time you will miss the important information (ie = the nested exception if any and the stacktrace of the buildexception). FYI I just committed Location that implements Serializable (cvs head) -- To unsubscribe, e-mail: For additional commands, e-mail: