Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 62751 invoked by uid 500); 26 Apr 2002 12:26:21 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 62738 invoked from network); 26 Apr 2002 12:26:20 -0000 Date: Fri, 26 Apr 2002 14:26:19 +0200 (CEST) From: Torsten Curdt X-X-Sender: To: Subject: RE: Problems with XSP In-Reply-To: <010501c1ed1c$a66c30e0$0a00a8c0@vgritsenkopc> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 26 Apr 2002, Vadim Gritsenko wrote: > > From: Graaf, Edgar de (fin) [mailto:Edgar.de.Graaf@ordina.nl] > > > > Great... > > > > when I code XSP and when I make some error in the logic I get (of > course) an > > error. An error contains a line number. Now I have to go to the work > > directory and look at the generated java file to find the error. Isn't > it > > possible to display the line number of the error in the XSP? > > Suggest how it is possible. I have thought about this a while ago, too. We should be able to extract that from the exception stacktrace. It should also be even possible to display that line's sourcecode (preferable with some surrounding lines). But I wasn't sure if this is really worth the work... ...is there a need for it? -- Torsten --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: