[ 
http://jira.magnolia-cms.com/browse/MGNLGROOVY-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Federico Grilli updated MGNLGROOVY-32:
--------------------------------------

    Fix Version/s: 1.1.1
                       (was: 1.2)

> Inconsistent session returned when getting a QueryManager
> ---------------------------------------------------------
>
>                 Key: MGNLGROOVY-32
>                 URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-32
>             Project: Magnolia Groovy Module
>          Issue Type: Bug
>          Components: console, integration
>    Affects Versions: 1.1
>            Reporter: Grégory Joseph
>            Assignee: Federico Grilli
>            Priority: Major
>             Fix For: 1.1.1
>
>
> In the console, if one tries to obtain a QueryManager instance via a 
> HierarchyManager, it's provided with the correct jcr session:
> {noformat}
> mgnl> q = ctx.getHierarchyManager('config').getQueryManager()
> ===> 
> info.magnolia.cms.core.search.QueryManagerImpl@1ee3b2dd
> mgnl> q.createQuery("select * from nt:base where contains(*, 'forum-jcr')", 
> "sql")
> ===> 
> info.magnolia.cms.core.search.QueryImpl@343b8714
> {noformat}
> ... but if she tries to take the {{MgnlContext.getQueryManager()}} shortcut, 
> it isn't:
> {noformat}
> mgnl> q = ctx.getQueryManager('config')
> info.magnolia.cms.core.search.QueryManagerImpl@734a8075
> mgnl> q.createQuery("select * from nt:base where contains(*, 'forum-jcr')", 
> "sql")
> RepositoryException: corresponding session has been closed
> {noformat}

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




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to