Hello,
> *Multiple possible methods / root resource classes for one request*
> in the algorithm for matching requests to resource methods, part 1e
> does not define what happens, when multiple root resource classes have
> the same @Path annotation. The same is in part 2 f/g and 3b/c. Is it
> implementation dependent, like the choose of the constructor, if there
> are more valid constructors (all parameters correct annotated and with
> the same no of parameters?) Or must the runtime environment generates
> error status 500?
for Part 3b/c another problem: We have multiple resource methods for the
same Path, producing different Mime-Types, "text/html" and "text/plain",
for example.
In a request they are both accepted with the same quality (or "text/*"
was requested). What should happens? I think it is not a good idea to
reject the request as not acceptable, as internal error or what ever.
In @ProduceMime it is not possible to specify a method to prefer. A
possibility is to add an attribute ("preference" for example, a numeric
type), where the runtime environment choose the method with the highest
(or lowest) preference, if the
If we don't want to complicate the API, the implementation should be
allowed to use anyone of the methods. That's ok I think, because the
client allows this in the request.
best regards
Stephan