[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3262) Non-concrete Collection types not supported on target model

[Max Rydahl Andersen (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12439655#action_12439655 ] 

Max Rydahl Andersen commented on JBIDE-3262:
--------------------------------------------

It is standard in eclipse to right click on errors in the Error Problem view to invoke any possible Quick fixes so that is standard.
But if that right click is in the actual editor then yes that is not intuitive - I would suggest adding a link in the error text if fixable i.e.

...cannot be instantiated (Fix this)   ...and the Fix this is underlined to indicate a link. 

alternatively add a button after the text, but I think the above fits better into the Form based  editors in eclipse.

> Non-concrete Collection types not supported on target model
> -----------------------------------------------------------
>
>                 Key: JBIDE-3262
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3262
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: smooks
>            Reporter: Tom Fennelly
>            Assignee: Xue Peng
>             Fix For: 3.0.0.cr1
>
>         Attachments: Screenshot-4.png
>
>
> If the target model contains a Collection property of a non-concrete type (e.g. java.util.List), the editor displays an error saying that the type can't be instantiated.  In this particular case, can't we default to an ArrayList, or pop up a dialog asking the user to select a concrete type.

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