Re: svn commit: r598331 [1/22] - in /incubator/sling/trunk/scripting/jsp: ./ src/main/java/org/apache/jasper/ src/main/java/org/apache/jasper/compiler/ src/main/java/org/apache/jasper/compiler/tagplugin/ src/main/java/org/apache/jasper/runtime/ src/main/ja...

[Roy T. Fielding]

On Nov 26, 2007, at 8:15 AM, [EMAIL PROTECTED] wrote:

SLING-98 Migrate JSP scripting support
  + plus include Jasper Compiler and EL implementation

Ouch.  Just out of curiosity, why do we need the source of jasper?
Is it to replace the back-end storage bits with JCR?  Would it be
possible to use some OOP to override the specific storage classes
within jasper instead of building the entire tree?  If not, then
I think we should rename jasper to sling/ssi4j (or something) to
avoid the library binding clashes.

....Roy