Hi Vidal, The sling.servlet.resourceTypes annotation is required, otherwise the servlet is just ignored. That is, in your first example, where you just define the sling.servlet.extensions, Sling does not know to which resource type the servlet applies and cannot handle it.
@scr.property name="sling.servlet.extensions" value="menu" @scr.property name="sling.servlet.resourceTypes" value="foo/bar" This defines the servlet to handle requests for foo/bar resources where the reqest extension is menu. Hope this helps. Regards Felix Am Freitag, den 15.02.2008, 13:32 +0100 schrieb Vidar Ramdal: > I'm trying to register a servlet to handle requests with a ".menu" extension: > * @scr.property > * name="sling.servlet.extensions" > * value="menu" > > Then I post some content: > curl -F"sling:resourceType=foo/bar" -F"title=some title" > http://admin:[EMAIL PROTECTED]:8888/content/mynode > > If I now visit http://localhost:8888/content/mynode, I get the > expected default rendering (StreamRendererServlet). > > If I visit http://localhost:8888/content/mynode.menu, I get a "No > default renderer found for extension='menu' (500)" error. > > Just to make sure I haven't made a mistake in my servlet, I change the > javadoc annotation to > * @scr.property > * name="sling.servlet.resourceTypes" > * value="foo/bar" > > Visiting http://localhost:8888/content/mynode and even > http://localhost:8888/content/mynode.menu invokes my servlet. > > So it seems resolving a servlet from a resource type works, but not > from an extension. > Am I doing something wrong, or is this a bug? >
