On Jan 18, 2008 1:30 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Am Freitag, den 18.01.2008, 11:39 +0100 schrieb Bertrand Delacretaz: > ...If the servlet has a path by which > the corresponding ServletResourceProvider may be attached into the > virtual resource tree, the ServletResourceProvider could then on request > select a servlet which it deems most appropriate and call the > canProcess() (or similar) method before actually returning the servlet... Ok, sounds fine. > > ...Also, is there any notion of priorities in Resource resolution in your > > design?... > ...Thus it is possible for two different Servlets serving the same resource > type but different extensions to be correctly selected.... And if they have the same extensions (by mistake), is the behaviour predictable? I'm asking because configuration/ bundle loading mistakes are fairly easy to do with a dynamic environment such as OSGi, and if Sling silently ignores a Servlet with duplicate selection parameters, that might be hard to troubleshoot. Not an urgent problem but we might want to open a JIRA issue about it if the risk exists now. -Bertrand
