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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen moved JBDS-508 to JBIDE-3599:
-------------------------------------------------

              Project: Tools (JBoss Tools)  (was: Developer Studio)
                  Key: JBIDE-3599  (was: JBDS-508)
          Component/s: Hibernate
                           (was: hibernate)
                           (was: seam)
        Fix Version/s: 3.0.0.GA
                           (was: 2.0.0.cr2)
    Affects Version/s: 3.0.0.GA
                           (was: 2.0.0.beta1)


> HQL querying does not work out of the box in new Seam-web project
> -----------------------------------------------------------------
>
>                 Key: JBIDE-3599
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3599
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Hibernate
>    Affects Versions: 3.0.0.GA
>         Environment: JDK 5, 6
> Fedora 9 x68
> EAP 4.3.GA_CP03_FP01
>            Reporter: Jozef Hartinger
>            Assignee: Dmitry Geraskov
>            Priority: Minor
>             Fix For: 3.0.0.GA
>
>         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