Felix Meschberger wrote: > > So the request "GET /some/path.print.html" could be handled by any of > the following scripts > > path.GET.jsp > GET.jsp > PathGET.java > path.html.esp > html.esp > PathHtml.vlt > path.gsp > Path.groovy > > This would of course extend the list of checks to apply for finding > scripts, but would certainly gelp Java developers. > > The drawback of this is, that the request "GET /path.PrintA4.html" might > be handled by the same script as "GET /path.Print.A4.html". But this may > be a hypothetical collision and problem. > > WDYT ? > Hmm, I'm not sure if I want to go down this road. If you provide "real" servlets through bundles, you can register them properly. So you end up with the problem above only if you use the Java Servlet script support and store the source of the servlet in your repository. I think this is an edge case where we can live with the reduced usability. Either use a real scripting language (if you prefer java, use jsp) or use Java as it is intended to be used in Sling through OSGi bundles.
Carsten -- Carsten Ziegeler cziege...@apache.org
