[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4613) Do not load ConsoleConfiguration by default.

[Dmitry Geraskov (JIRA)]

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

Dmitry Geraskov commented on JBIDE-4613:
----------------------------------------

>1) So the build of the console configuration is only needed when the query actually need to get executed - not used when opening nor editing in the editor meaning it won't affect them.
ConsoleConfiguration needs to provide better evaluation context (it give us available persistent classes for completion proposals) - at the phase of editing, and required to be build for query execution.

>2) Yes, here the reason is that it can take a long time opening the editor if it is forced.
>I think we should roll back this change since it shows up in the ui in a place where the user doesn't really see any change/benefit of splitting it in two.

Because of the reasons I think we need leave this feature because if developer doesn't need persistent class names completion proposals and doesn't going to run the query he don't need the configuration to be built.

> Do not load ConsoleConfiguration by default.
> --------------------------------------------
>
>                 Key: JBIDE-4613
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4613
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: Hibernate
>    Affects Versions: 3.1.0.M2
>            Reporter: Dmitry Geraskov
>            Assignee: Dmitry Geraskov
>            Priority: Critical
>             Fix For: 3.1.0.CR2
>
>
> This should be done as completion proposal

-- 
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