The ordering is the ordering above in init, which must be carefully updated to prevent problems.  Since its maintained by hand its easy enough to ensure the ordering is correct.  Doing longest match is a pain just because we'd have to have knowledge of how the servlet decided to take a request.  In my opinion its not worth the effort to ensure longest match here.

I'm putting a warning comment in the binding code above.  If it ever becomes something we simply can't manage by code reviews someone can revisit this to do longest match, or something better.