You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "TURPIN Michel (JIRA)" <ji...@apache.org> on 2017/07/19 14:47:00 UTC
[jira] [Commented] (TOMEE-2100) Jax-RS Providers are ordered by
?hashcode? instead of priority
[ https://issues.apache.org/jira/browse/TOMEE-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093198#comment-16093198 ]
TURPIN Michel commented on TOMEE-2100:
--------------------------------------
Changed the name of this issue. On my project, it looked like the name was the criteria used for ordering but it's not. I suspect it may use some hashcode or similar mechanisms.
> 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: Bug
> Components: TomEE Core Server
> Affects Versions: 7.0.3
> Reporter: TURPIN Michel
> Labels: features
> Attachments: tomee-priority.zip
>
>
> 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)