Endpoint mapping ambiguity in Jersey 2.0
I am observing sporadic errors when processing Jersey request.
In my resource I have /{id} and /docShells mappings. {id} is string.
The same URl …/api/v1/institutions/429657/documents/docShells/9081/userDefinedParameters in 99.9% causes “docShells” to be used as an endpoint, which is correct. But in some rare cases, it treats it as Id (which is never “docShells”). How to explain this sporadic behavior and how to avoid it?