Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
From: Jeffrey_M_Grossman@Countrywide.Com
Subject: Re: XSP debugging
To: cocoon-users@xml.apache.org
Message-ID: <OF2FB3D796.B56EF033-ON88256952.007FFE0C@countrywide.com>
Date: Wed, 6 Sep 2000 16:20:08 -0700
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii


The only way that I have found (under 1.7.4) to get the XSP to re-compile
in your case is to touch the XML file. This then forces Cocoon to
invalidate all the files associated with the process (XML-XSP-XSL to
HTML/PDF).
-----
Jeffery


>I find debugging XSP code to be a real pain.  Something somewhere on the
serverside is caching my code only when >I use XSP somewhere...the problem
is that when I make a change, it doesn't reflect that in my output.  I
could >completely rip out a huge chunk of XSP code, and nothing on the
output is affected.  What gives?  Restarting >Tomcat doesn't help, and I'm
beginning to wonder where this is getting put.
>
>I'm running Linux/Apache/Tomcat/IBM JDK and I'm doing XML -> XSP -> XSL
(XML points to a stylesheet with XSP in >it, which points to an XSL page
which formats everything).
>
>--man
>Michael A. Nachbaur (KE6WIA)
>mike(at)nachbaur(dot)com
>http://www.nachbaur.com
>"America does four things better than any other country in the world: rock
music, movies, software and high-speed >pizza delivery."  -- Neal
Stephenson
>

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org