[JBoss JIRA] Created: (JBIDE-4332) Impossible to deploy EJB3 with JPA annotations with JBossTools on a JBossESB installation
by Vincent Girard-Reydet (JIRA)
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
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
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-3155) Exceptions thrown when closing Visual Editor
by Asgeir Frimannsson (JIRA)
Exceptions thrown when closing Visual Editor
--------------------------------------------
Key: JBIDE-3155
URL: https://jira.jboss.org/jira/browse/JBIDE-3155
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.0.0.cr1
Environment: SUN jdk1.6_u10, Fedora 10 x86_64 using JBoss Tools and drivers from http://download.jboss.org/jbosstools/builds/nightly/3.0.0.CR1/20081108025...
Reporter: Asgeir Frimannsson
<probably-irrelevant>
Step 1: Create a new seam-gen project using ./seam create-project
Step 2: Import the project into JBoss tools using File->New->Project
Step 3: Set up the Seam build environment etc..
</probably-irrelevant>
Step 4: Open a page, e.g. home.xhtml in visual editor
Step 5: Close editor
... Exceptions thrown..
!ENTRY org.eclipse.ui 4 0 2008-11-11 09:44:34.790
!MESSAGE The function "removeSelectionListener" returned an error condition (0x80004005)
!STACK 0
org.mozilla.xpcom.XPCOMException: The function "removeSelectionListener" returned an error condition (0x80004005)
at org.mozilla.xpcom.internal.XPCOMJavaProxy.callXPCOMMethod(Native Method)
at org.mozilla.xpcom.internal.XPCOMJavaProxy.invoke(XPCOMJavaProxy.java:143)
at $Proxy16.removeSelectionListener(Unknown Source)
at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.removeSelectionListener(XulRunnerEditor.java:599)
at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor$2.widgetDisposed(XulRunnerEditor.java:133)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:117)
--
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
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-4201) Discriminator of RootClass is not exported.
by Dmitry Geraskov (JIRA)
Discriminator of RootClass is not exported.
-------------------------------------------
Key: JBIDE-4201
URL: https://jira.jboss.org/jira/browse/JBIDE-4201
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Hibernate
Affects Versions: 3.0.0.GA
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
RootClass.discriminator value used to determine discriminator type and columns when table-pre-type-hierarchy used in mapping, but element discriminator never exported and sessionFactory can't be built for such configuration:
org.hibernate.MappingException: No discriminator found for com.jboss.dvd.seam.Admin. Discriminator is needed when 'single-table-per-hierarchy' is used and a class has subclasses
org.hibernate.MappingException: No discriminator found for com.jboss.dvd.seam.Admin. Discriminator is needed when 'single-table-per-hierarchy' is used and a class has subclasses
at org.hibernate.mapping.SingleTableSubclass.validate(SingleTableSubclass.java:41)
at org.hibernate.cfg.Configuration.validate(Configuration.java:1102)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1287)
at org.hibernate.console.ConsoleConfiguration$3.execute(ConsoleConfiguration.java:502)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:64)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:95)
at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:497)
...
--
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
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-4050) Abstract attribute is never exported in persistent class.
by Dmitry Geraskov (JIRA)
Abstract attribute is never exported in persistent class.
---------------------------------------------------------
Key: JBIDE-4050
URL: https://jira.jboss.org/jira/browse/JBIDE-4050
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: FreeMarker, Hibernate
Affects Versions: 3.0.0.GA
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0
We use the following code to export the attrubute:
<#if clazz.abstract?exists && clazz.abstract>
abstract="true"
</#if>
but "abstract" attribute held into PersistentClass.isAbstract. I guess developers of freemarker check only get+Fieldname and is+Fieldname, like java convension says.
So, the working code is:
<#if clazz.isAbstract()?exists && clazz.isAbstract()>
abstract="true"
</#if>
Patch and unit test will be attached.
--
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
16 years, 5 months