* Sylvain Wallez: > Mark Lundquist wrote: > > > One thing that is really troublesome is that if an > > exception gets thrown out of something called by the macros > > (typically class JXMacrosHelper), JXTG reports the error with > > line+column corresponding to the outermost macro, i.e. the > > <ft:form-template>. Needless to say that's not super-helpful. > > What we actually want is a location stack. And know what? Just > right now (yeah, I know, it's sat. morning...) I'm working on > adding "Cocoon stack traces" we talked about a long time ago, as > this became really obvious after the changes I made to the > CForms parsing stuff [1].
It's true, exception handling in JXTemplate is very poor. I'm often getting NPE while developing JX macros, and it's actually impossible to know where it happens, so I have to comment the lines one by one or output dummy values to finally track down the problem. Thank you Sylvain for working on that, we really need it. Cocoon stack traces rule! Keep up the good work, and enjoy your week-end. -- Jean-Baptiste Quenot Systèmes d'Information ANYWARE TECHNOLOGIES Tel : +33 (0)5 61 00 52 90 Fax : +33 (0)5 61 00 51 46 http://www.anyware-tech.com/
