You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2019/01/06 13:54:00 UTC

[jira] [Closed] (ISIS-157) [WON'T FIX] parseTextEntry fix.

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

Dan Haywood closed ISIS-157.
----------------------------
    Resolution: Fixed

> [WON'T FIX] parseTextEntry fix.
> -------------------------------
>
>                 Key: ISIS-157
>                 URL: https://issues.apache.org/jira/browse/ISIS-157
>             Project: Isis
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.1.2-incubating
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: 1.17.0
>
>
> from email on isis-dev mailing list:
> > The issue with "T parseTextEntry(Object contextPojo, String entry)" is that
> > I went through the code making some previously raw types into generic ones.
> >  Doing that caused a runtime class-cast exception with some code, where the
> > owning pojo was being passed in (eg Employee) for the context rather than
> > the value (eg the String representing the Employee's firstName, say).
> So it sounds like I should reinstate the generic parameter (ie back to "T
> parseTextEntry(T context, String entry)" ), and then fix that place where
> the wrong object is being passed in.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)