cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <>
Subject Re: XSP "official" position
Date Sat, 22 Nov 2003 01:38:48 GMT
On 18.11.2003 15:47, Vadim Gritsenko wrote:

>>> XSP leaves room for heavy abuse! I guess that's the major problems.
>>> 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.


View raw message