[Springframework-rcp-dev] [Spring-JIRA] Closed: (RCP-479) Refactor Message to interface

[Jan H. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/spring/browse/RCP-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Hoskens closed RCP-479.
---------------------------

       Resolution: Fixed
    Fix Version/s: 0.3.0

fixed with revisions:
http://spring-rich-c.svn.sourceforge.net/viewvc/spring-rich-c?view=rev&revision=1772

http://spring-rich-c.svn.sourceforge.net/viewvc/spring-rich-c?view=rev&revision=1773

> Refactor Message to interface
> -----------------------------
>
>                 Key: RCP-479
>                 URL: http://opensource.atlassian.com/projects/spring/browse/RCP-479
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>          Components: Application Framework
>            Reporter: Jan Hoskens
>            Assignee: Jan Hoskens
>             Fix For: 0.3.0
>
>
> Currently there's an implementation Message that's being used to propagate messages. Besides this we also have ValidationMessages that are spawned by the rules containing the same info with additional information concerning the validated property. These two are however unrelated which leads to converting between both of them.
> Refactoring should include:
> - make the Message an interface
> - make ValidationMessage extend Message
> - provide default implementation of Message (DefaultMessage)
> - remove converting between old Message and ValidationMessage
> - additionally: Message has a getText while ValidationMessage has a getMessage, these are basically the same properties so one of them should be renamed

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira