[jira] [Updated] (ISIS-502) wicket componentList order sensitivity

["Dan Haywood (JIRA)" <ji...@apache.org>]

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

Dan Haywood updated ISIS-502:
-----------------------------

    Affects Version/s:     (was: viewer-wicket-1.3.0)
        Fix Version/s: viewer-wicket-1.4.0

> wicket componentList order sensitivity
> --------------------------------------
>
>                 Key: ISIS-502
>                 URL: https://issues.apache.org/jira/browse/ISIS-502
>             Project: Isis
>          Issue Type: Bug
>          Components: Viewer: Wicket
>            Reporter: Jeremy Gurr
>            Assignee: Dan Haywood
>             Fix For: viewer-wicket-1.4.0
>
>         Attachments: patch
>
>
> When replacing a component factory (IsisBlobPanelFactory, for example), it is added to the end of the component list instead of the same place it came from. Since, unfortunately, the order of these components affects which factory is chosen to render a component type, this actually changes the behavior of the app in unexpected and hard to debug ways, since a different factory now will intercept the component request. 
> I've got a patch which fixes this, basically by injecting the replacement factory into the same location in the component list, but I'm not sure how to attach it to the bug ticket. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)