[jbosstools-issues] [JBoss JIRA] Updated: (JBDS-508) HQL querying does not work out of the box in new Seam-web project

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBDS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBDS-508:
-------------------------------------

    Fix Version/s: 2.0.0.cr2


ok, so this is a minor one caused by the tree seem to be using the Configuration build for the first usage (pre reverse engineering) - we need to fix that but can be worked around now by doing the refresh of the configuration (which actually is the workflow to do when reverse engineering or doing other things that could cause a change)

> HQL querying does not work out of the box in new Seam-web project
> -----------------------------------------------------------------
>
>                 Key: JBDS-508
>                 URL: https://jira.jboss.org/jira/browse/JBDS-508
>             Project: Developer Studio
>          Issue Type: Bug
>          Components: hibernate, seam
>    Affects Versions: 2.0.0.beta1
>         Environment: JDK 5, 6
> Fedora 9 x68
> EAP 4.3.GA_CP03_FP01
>            Reporter: Jozef Hartinger
>            Assignee: Dmitry Geraskov
>             Fix For: 2.0.0.cr2
>
>         Attachments: hibernate-querying.txt
>
>
> HQL query editor does not work in new Seam-web projects in JBDS 2.0.Beta1 failing with attached exception. Entities are present and is available in Hibernate Configurations.
> I found test case to reproduce:
> 1. Create seam web project with new connection profile
> 2. add required jars (additional jbds driver)
> 3. Seam generate entities - reverse engeneering from db, select 1 table(Person, for ex), insclude, finish
> 4. Open hibernate configuration view
> 5. Expand your console configuration - it builds successfully, but without entity (Person)
> - this is the problem
> if rebuild the console configuration, then hql begins to work properly.

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