In general, I advocate against writing significant amounts of Java code in a
JET template - it is just plain hard to debug. Writing your Java logic in
Java classes is better for a number of reasons:
* JET templates are not burdened with large amounts of logic.
* It's easier to test and debug these separate classes.
* The Java editing experience is best when using the JDT editors.
On the idea of a JET debugger, I am open to proposals. Nothing is in plan
for the Ganymede release (Jun 2008). But the June 2009 release is a blank
"pankaj" <firstname.lastname@example.org> wrote in message
> There is a Java debug options one can debug the generated Java classe.
> Is there going to be JET debugging in Eclipse for future releases?