[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4332) Impossible to deploy EJB3 with JPA annotations with JBossTools on a JBossESB installation

[Kevin Conner (JIRA)]

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

Kevin Conner commented on JBIDE-4332:
-------------------------------------

This is not an issue with tooling, rather hibernate appears to be pulling in the orm.xml from any available resource.

I am still investigating on behalf of ESB.

> Impossible to deploy EJB3 with JPA annotations with JBossTools on a JBossESB installation
> -----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4332
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4332
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: drools, ejb3, esb, integration
>    Affects Versions: 3.0.1.GA
>         Environment: Windows XP SP2
> JbossAS 4.2.3 GA (default configuration)
> JbossESB 4.5 GA
> JbossTools 3.0.1 GA
> JDK 1.6_12
>            Reporter: Vincent Girard-Reydet
>            Priority: Blocker
>         Attachments: TestEJBJPA.jar, TestEJBJPA_Project.zip
>
>
> When I deploy an EJB3 that contains JPA annotations from within Eclipse, I systematically get an error:
> SessionFactoryImpl] Error in named query: ProcessInstancesWaitingForEvent
> org.hibernate.hql.ast.QuerySyntaxException: ProcessInstanceInfo is not mapped [select processInstanc
> eInfo.processInstanceId from ProcessInstanceInfo processInstanceInfo where :type in elements(process
> InstanceInfo.eventTypes)]
> 	at org.hibernate.hql.ast.util.SessionFactoryHelper.requireClassPersister(SessionFactoryHelper.java:
> 158)
> See the complete discussion here: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=154726&start=10
> This does *NOT* happen when deploying directly on the server, it only happens when deploying from Eclipse.
> Note that from the quoted thread on the forum, this may be linked to Drools also. i have however not been able to force the deployment of my EJB after Drools (I don't know Jboss enough to do it).
> In attachment you will find a minimum case that reproduces the problem. To reproduce, just import the project into Eclipse, then deploy it (with Eclipse) on a JBoss AS 4.2.3 with JbossESB 4.5 installed.
> If someone knows how to put this bug in the JbossESB section as well, I would appreciate.

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