Can we programmatically specify the default order for ambiguous calls?
For example, I recently added a json output for the /tika endpoint,
and that is now the default...if the client does not specify "accepts"
in the header. That'll be a breaking change, which I don't want.
Is the problem the design of our api? Or can we fix this as is...
Thank you!
Best,
Tim
On Wed, Apr 14, 2021 at 1:29 PM Subhajit Das <[email protected]> wrote:
>
>
>
> Hi,
>
>
>
> In Tika server, if a request is made against a REST resource and if it is
> matched with multiple resource handler method (like getXML and getText),
> then, is there predefined order of resolving method?
>
> There is always an warning printed, in such case.
>
> Practically I have seen uncertainty in method.
>
>
>
> Thanks and Regards,
>
> Subhajit Das
