On Mon, Aug 22, 2011 at 6:03 PM, Ian Boston <[email protected]> wrote: > IIRC, the problem is the way in which the list of potential servlets > is built and the way in which that list is processed. > I think the list is built with 1 slot per pattern, and then only the > first opting servlet that claims it can handle the request gets > through as a ServletResource...
Yes, IIUC that's where using a ServletResourceProvider per set of resource paths (as opposed to one per servlet currently) would help - that provider would then be mapped to the set of servlets that share the same set of resource paths, and select the one that accepts the current request. > ...its > still the first OptingServlet that gets used, and then fundamentally, > what would the code do if 2 servlets both opted to handle the same > request ?... I'd use the first one that accepts the request, and keep the servlets ordered by service ranking to make sure things are predictable. -Bertrand
