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. > > You can get round this by registering some Servlets under /lib and > some under other locations /apps etc, then the path to each > ServletResource appears differently and gets tested, however, 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 think the request should be handled by the servlet with the highest service priority.
Reto
