The main problem is the ambiguity that these PHP-style scripts introduce, which itselfs leads to a hackish programming style.
On 20.02.2008, at 18:42, Peter Svensson wrote:
One hackish solution could be for Bunkai to save the scripts as .esp.src or somethin like that, and then I could have a "deplot" button (which couldwork hierarchically) which just copies those files to .esp extensions. Cheers, PSOn Wed, Feb 20, 2008 at 5:32 PM, Lars Trieloff <[EMAIL PROTECTED]> wrote:After thinking a bit about it, I think that neither renaming server- side scripts to ecma nor having a designated /apps or /libs path nor having an executable bit would solve my problem in the light of Bunkai, where you actually want to edit the scripts you are going to execute later. I do not really understand yet when scripts are supposed to beexecuted on request and where this behavior is desired (it feels a bitlike PHP to me) regards, Lars On 20.02.2008, at 15:37, Felix Meschberger wrote:Hi, Am Mittwoch, den 20.02.2008, 14:33 +0100 schrieb Lars Trieloff:I was unable to get the JSON representation (curl -u admin:adminhttp://localhost:8888/dojo/dojo/AdapterRegistry.js.1.json)because Sling tries to execute the JS script then and gives me following error message: org.mozilla.javascript.EcmaError: ReferenceError: "dojo" is not defined. (/dojo/dojo/AdapterRegistry.js#1) ... and so on.Yes, we execute a resource, which adapts to Servlet, if the request hasan extension. Therefore the request /dojo/dojo/AdapterRegistry.js (no extension) is not executed by the given request is executed (extensionjson). This collision between streaming the script and executing the script is an issue only with .js files AFAIK. The reason for this is, that the JavaScript ScriptEngineFactory is registered for .js and .esp files. We might fix this by using .ecma instead of .js for server-side JavaScript files. WDYT ?So my question is how do I define subtrees that are not executable, even if they contain a script. I think microsling originally had a convention that only scripts in /scripts were actually executable, but the current code deviates from this convention.This depends from where you are looking from: I would say, microslingdevaiated from Sling in that respect ;-) Regards Felix-- Lars Trieloff [EMAIL PROTECTED] http://weblogs.goshaky.com/weblogs/lars
-- Lars Trieloff [EMAIL PROTECTED] http://weblogs.goshaky.com/weblogs/lars
smime.p7s
Description: S/MIME cryptographic signature
