tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TOMEE-2100) Jax-RS Providers are ordered by ?hashcode? instead of priority
Date Tue, 25 Jul 2017 13:46:00 GMT

     [ https://issues.apache.org/jira/browse/TOMEE-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Romain Manni-Bucau updated TOMEE-2100:
--------------------------------------
    Issue Type: New Feature  (was: Bug)

> Jax-RS Providers are ordered by ?hashcode? instead of priority
> --------------------------------------------------------------
>
>                 Key: TOMEE-2100
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2100
>             Project: TomEE
>          Issue Type: New Feature
>          Components: TomEE Core Server
>    Affects Versions: 7.0.3
>            Reporter: TURPIN Michel
>              Labels: features
>         Attachments: tomee-priority.zip
>
>
> When multiple providers share the same possible tasks, their priority is not taken into
consideration when it comes to choose the effective implementation. This would allow effective
overriding of providers, for instance using Jackson instead of Johnzon as a writer/reader.
> The attached zip contains a project with 5 body writers with differents priorities. You
may run it with the {{mvn clean package tomee:run}} command.
> The {{FooResource}} class is then accessible through the {{http://localhost:8080/tomee-priority/resources/foo/}}
URL. It must show "B".
> As I run it, it shows me "D", you might have different values.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message