XSP leaves room for heavy abuse! I guess that's the major problems. ...plus that debugging is a pain :)
Exactly, we must do it impossible to abuse it :-) Going towards an XML only template language would also allow to have an interpreter instead of compiling transformed java files.
May be you want to resurrect sll [1]? :)
Hmm, no. I want to start at another point, at the lowest level. No Java at all in a pure XSP file (without any extension, so any logicsheet). For avoiding exactly such an error as [1]. Or the bugfix for xsp:attribute handling [2]. At the moment we can not fix it, because XSP code is to "flexible", it allows additional startElement()s as you showed in your comment at this bug. And you never get it fixed appropriately when you mix abstraction levels or different coding languages (to be proven).
But if you know all the possible things that can occur, you can provide a working implementation of the transformation or even in interpreter.
[1] http://marc.theaimsgroup.com/?t=106931803600003&r=1&w=2 [2] http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15841
