Hi,
Bertrand Delacretaz schrieb:
On Fri, Jul 4, 2008 at 11:13 AM, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
...It would be handy if the servlet containers JSP servlet could
resume processing if a URL was not handled by the sling servlet....
If you request a .jsp resource that is not in the repository, the
Sling resource resolver will select an
o.a.s.api.resource.NonExistingResource, with a resource type of
"sling:nonexisting".
To be precise we operate in the Resource tree. This in an extended
repository. So, not all JSPs are required to be present in the JCR
repository. You may also provide JSPs in bundles. So, if you for example
pack your existing JSP files into a bundle and define
"Sling-Bundle-Resources" manifest headers, you can use them directly.
Alternatively you may create a ResourceProvider providing JSP file
resources from the filesystem. You might take a look at the
BundleResourceProvider for a hint on how to do this.
Regards
Felix
This means you could create a servlet to handle this resource type
(@scr.property name="sling.servlet.resourceTypes"
value="sling:nonexisting"), which could then forward to the servlet
container as needed.
To experiment with this, you can also create a
apps/sling/nonexisting/nonexisting.esp script in the repository.
-Bertrand
