On Jan 13, 2004, at 10:34 AM, Bertrand Delacretaz wrote:

Le Mardi, 13 jan 2004, à 09:47 Europe/Zurich, Steven Noels a écrit :
... saw Marc once hooking the Eclipse debugger into an Apple, and that seriously kicked ass - you don't need println() anymore of you have a full-blown debugger at your service.

Yes, if you're debugging java code it's fairly easy to setup the JVM for remote debugging before starting Cocoon, and then do whatever.


But I don't think this helps for debugging flowscript or other stuff that Cocoon interprets by itself (sitemaps, XSLT, etc.). That's where a debugging framework could help.

Sure! I was basically trying to indicate my support for the effort of going along that road instead of JFID with println() - but as Chris pointed out, going for one doesn't exclude the other.


</Steven>
--
Steven Noels                            http://outerthought.org/
Outerthought - Open Source Java & XML            An Orixo Member
Read my weblog at            http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org                stevenn at apache.org



Reply via email to