You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Michael Bolz (JIRA)" <ji...@apache.org> on 2014/03/13 14:47:45 UTC

[jira] [Assigned] (OLINGO-197) A means should be exposed to get translated message for MessageReference key

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

Michael Bolz reassigned OLINGO-197:
-----------------------------------

    Assignee: Michael Bolz

> A means should be exposed to get translated message for MessageReference key
> ----------------------------------------------------------------------------
>
>                 Key: OLINGO-197
>                 URL: https://issues.apache.org/jira/browse/OLINGO-197
>             Project: Olingo
>          Issue Type: New Feature
>          Components: odata2-core
>    Affects Versions: V2 1.0.0, V2 1.1.0
>            Reporter: Sumitesh R S
>            Assignee: Michael Bolz
>            Priority: Critical
>             Fix For: V2 1.3.0
>
>
> In few scenarios when there is a internal bug or otherwise (such as https://issues.apache.org/jira/i#browse/OLINGO-195), an exception is thrown where the error message is null but the exception has a MessageReference object. Now in order to show users appropriate translated error message as to what went wrong, there is no means exposed to get translated message. So, either the exceptions should be thrown with a translated message or a means should be exposed through a utility to get a translated message from a MessageReference object / key



--
This message was sent by Atlassian JIRA
(v6.2#6252)