Hi, Bertrand Delacretaz schrieb: > On Mon, Jul 6, 2009 at 11:17 AM, Felix Meschberger<[email protected]> wrote: >> This is most probably caused by a recent change in the default value for >> the JSP "development" mode flag:... > >> ...I am currently investigating what to do.... > > Could we set the JSP "development mode" via an HTTP request? The tests > could then do that.
That would be conceivable as a short-term workaround. But in fact this would be kind of a "breach of contract": Whether a request is handled by a JSP or not is an implementation detail. How the JSP is called is another implementation detail. "Publicizing" such details by supporting a "use JSP compiler in development mode" flag is IMHO wrong. My option is to allow sling.properties style overwrite of the default or configured value. Not sure, whether this is really the best of all options. Maybe we even have to go other routes.... Regards Felix
