An optional "@Resource name" annotation can be used to force the resource identifier to be something other than the first segment of the route URI. For example, if "@Resource /payment" is specified together with "@Router /invoice/{id}/payments [get]" then this operation will be part of the "payment" sub-api, rather than the "invoice" sub-api. This is also good for when the @Router specifies a path in which the first segment is almost correct, but not quite, e.g. /payments (plural) vs. /payment (singular). A leading slash in the name in the @Resource annotation is optional. So, "@Resource /payment" and "@Resource payment" are the same. (Issue #3)
Merge pull request #11 from polyglot-jones/issue_3

An optional "@Resource name" annotation ... (Issue #3)