Thanks for the thorough answer, Joakim.
On Tue, Feb 6, 2018, at 16:06, Joakim Erdfelt wrote: > The path mappings in ServletHandler are not currently expose for > embedded jetty users.> If you want this exposed, open an issue at > https://github.com/eclipse/jetty.project/issues asking for it.> Note: There > is some debate internally within Jetty developers that the > search/lookup order of the PathMappings matching logic hasn't > been rigorously tested enough (its a touchy area of the Servlet > spec).> If you suspect any such behavioral concerns in your usage, let > us know! I won't open an issue, I can imagine the path spec matching to be tricky enough with the Servlet spec as-is. Should I encounter a problem while using the pathmap package, I'll surely will send an issue or pull request upstream. > In the JSR356 (javax.websocket) implementation we use the > UriTemplatePathSpec like this ...> 1. The WebSocketUpgradeFilter is servlet > mapped to "/* > [...] > 1. If the PathSpec is UriTemplatePathSpec, then it will grab the path > parameters out via Map<String, String> pathMap = > pathSpec.getPathParams(requestPath); That pretty much sums up also what I'm doing internally in my servlets with the UriTemplatePathSpec. Thanks again, Robert
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
