[JBoss JIRA] (JBIDE-16899) HQL query cannot be executed when using Hibernate 4.3 (MappingException)
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16899?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-16899:
------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> HQL query cannot be executed when using Hibernate 4.3 (MappingException)
> -------------------------------------------------------------------------
>
> Key: JBIDE-16899
> URL: https://issues.jboss.org/browse/JBIDE-16899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1, L64 (Fedora 19), OpenJDK 1.7
> Reporter: Jiri Peterka
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> {code}
> org.hibernate.MappingException: Could not get constructor for org.hibernate.persister.entity.SingleTableEntityPersister
> at org.hibernate.persister.internal.PersisterFactoryImpl.create(PersisterFactoryImpl.java:185)
> at org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:135)
> at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:400)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1857)
> at org.jboss.tools.hibernate4_3.HibernateExtension4_3$3.execute(HibernateExtension4_3.java:118)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.jboss.tools.hibernate4_3.HibernateExtension4_3.execute(HibernateExtension4_3.java:211)
> at org.jboss.tools.hibernate4_3.HibernateExtension4_3.buildSessionFactory(HibernateExtension4_3.java:110)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:283)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:82)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:56)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:60)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4425)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3773)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3393)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.eclipse.ui.internal.views.log.EventDetailsDialog.open(EventDetailsDialog.java:181)
> at org.eclipse.ui.internal.views.log.EventDetailsDialogAction.run(EventDetailsDialogAction.java:98)
> at org.eclipse.ui.internal.views.log.LogView$15.doubleClick(LogView.java:536)
> at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:852)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
> at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:849)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1491)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1261)
> at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:252)
> at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:249)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:311)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4425)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3773)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3393)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:147)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:630)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:574)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:133)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:103)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:378)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:232)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1462)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Caused by: org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer]
> at org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:138)
> at org.hibernate.tuple.entity.EntityTuplizerFactory.constructDefaultTuplizer(EntityTuplizerFactory.java:188)
> at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:403)
> at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:520)
> at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:148)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at org.hibernate.persister.internal.PersisterFactoryImpl.create(PersisterFactoryImpl.java:163)
> ... 62 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:135)
> ... 71 more
> Caused by: java.lang.NoClassDefFoundError: javassist/util/proxy/MethodFilter
> at org.hibernate.bytecode.internal.javassist.BytecodeProviderImpl.getProxyFactoryFactory(BytecodeProviderImpl.java:58)
> at org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactoryInternal(PojoEntityTuplizer.java:244)
> at org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:222)
> at org.hibernate.tuple.entity.AbstractEntityTuplizer.<init>(AbstractEntityTuplizer.java:212)
> at org.hibernate.tuple.entity.PojoEntityTuplizer.<init>(PojoEntityTuplizer.java:80)
> ... 76 more
> Caused by: java.lang.ClassNotFoundException: javassist.util.proxy.MethodFilter cannot be found by osgi.identity; osgi.identity="org.jboss.tools.hibernate4_3"; type="osgi.bundle"; version:Version="1.0.0.Beta1-v20140321-0516-B10"; singleton:="true"
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:416)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:336)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:328)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> ... 81 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-16265) JPA validation reports Strategy class "uuid2" could not be found
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16265?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-16265:
------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> JPA validation reports Strategy class "uuid2" could not be found
> ----------------------------------------------------------------
>
> Key: JBIDE-16265
> URL: https://issues.jboss.org/browse/JBIDE-16265
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.1.1.CR1
> Reporter: Jim Boettcher
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> An Entity class with the following:
> @Id
> @GeneratedValue(generator = "system-uuid")
> @GenericGenerator(name = "system-uuid", strategy = "uuid2")
> @Column(name = "id", unique = true)
> private UUID id;
>
> gives the error:
> Strategy class "uuid2" could not be found
> changing the strategy to "uuid" will clear the error.
>
> My Project Facet has JPA 2.0
> The JPA configuration has:
> Platform: Hibernate (JPA 2.0)
> JPA implementation:
> Disable Library Configuration
> the Hibernate jars are on the project classpath
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-17735) JAX-RS Application wizard: double comments in generated class
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17735?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-17735:
----------------------------------
Component/s: upstream
> JAX-RS Application wizard: double comments in generated class
> -------------------------------------------------------------
>
> Key: JBIDE-17735
> URL: https://issues.jboss.org/browse/JBIDE-17735
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> JAX-RS Application class looks quite unusual, when is generated using JAX-RS Application wizard with option generate comments into default package.
> {code}
> @ApplicationPath("/rest")
> /**
> *
> */
> /**
> * @author rrabara
> *
> */
> public class App extends Application {
> }
> {code}
> When it is generated into user defined package, then there is just one java doc comment:
> {code}
> @ApplicationPath("/rest")
> /**
> * @author rrabara
> *
> */
> public class App extends Application {
> }
> {code}
> However, shouldn't the comment be above the annotation? It seems that it's the preferred way (e.g. see examples http://docs.oracle.com/javase/tutorial/java/annotations/predefined.html)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-15174) Improved work with datatools connection profiles for various projects using hibernate/jpa
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15174?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-15174:
------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Improved work with datatools connection profiles for various projects using hibernate/jpa
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-15174
> URL: https://issues.jboss.org/browse/JBIDE-15174
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 4.1.0.Beta2
> Reporter: Jiri Peterka
> Fix For: 4.2.0.CR1
>
>
> When working with JPA projects or examples from Central it's necessary to create JPA connection profile. I assume I already have some kind of configuration - either hibernate configuration, or connection directly defined in persistence.xml or defined data source. Still hibernate tooling and eclipse.datatools is complaining that it needs to define connection profile. You have to create a connection configuration again for connection profile to have working tooling. It leads to multiple configurations or you have to reconfigure a project to use eclipse.datatools connection profiles.
> What I would like to see is some mechanism howto easily create connection profiles:
> * the seamless way would be some support for our examples to generate connection profiles when they are imported (or at least to help with that)
> * and some support for hibernate configuration, persistence.xml and ds when creating connection profiles.
> Both features might need some eclipse.datatools contributions. But currently these two worlds (hibernate/jpa tooling and datatools are not very well integrated each other).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-16219) Errors about Hibernate console configuration, with no easy way to resolve
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16219?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-16219:
------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Errors about Hibernate console configuration, with no easy way to resolve
> -------------------------------------------------------------------------
>
> Key: JBIDE-16219
> URL: https://issues.jboss.org/browse/JBIDE-16219
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Environment: JBDS 7.0.1.GA
> Reporter: Pete Muir
> Fix For: 4.2.0.CR1
>
> Attachments: kitchensink-angularjs-bad.zip, kitchensink-angularjs-good.zip
>
>
> In my case, this appears to be caused by existing dot-files (which were created by a previous version of JBDS, on Maven Import...). Removing those files and reimporting fixes the problem.
> I haven't tested whether newer dot-files will cause the problem, or not.
> Attached are two projects, one which shows the problem, and one that doesn't (clean dot-files generated).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-17693) Forge addon classifier extension should be included in Forge Tools by default
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17693?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-17693:
------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Forge addon classifier extension should be included in Forge Tools by default
> -----------------------------------------------------------------------------
>
> Key: JBIDE-17693
> URL: https://issues.jboss.org/browse/JBIDE-17693
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: forge
> Affects Versions: 4.2.0.Beta2
> Reporter: Lincoln Baxter III
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: Screen Shot 2014-06-25 at 7.06.28 PM.png
>
>
> The current JBoss Tools Forge does not include the forge classifier support, which means that anyone doing forge addon development will suffer from the problem where m2 Eclipse does not properly resolve classifiers for forge-addon projects.
> This needs to be included in JBT Beta3: See screenshot.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBDS-3072) Cannot update from JBDS 8.0.0.Beta1 to Beta2
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3072?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3072:
--------------------------------------
I tried to remove the 4 lines you suggested but it didn't help. What is the purpose of the first 15 lines of this file? I'd be glad if we could get rid of them.
> Cannot update from JBDS 8.0.0.Beta1 to Beta2
> --------------------------------------------
>
> Key: JBDS-3072
> URL: https://issues.jboss.org/browse/JBDS-3072
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build
> Affects Versions: 8.0.0.Beta2
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 8.0.0.Beta3
>
> Attachments: beta2c-site-added.png, update-beta1-to-beta2c.png
>
>
> {code}
> Your original request has been modified.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Maven Seam Integration" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Mobile Browser Simulator" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Portlet" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "Maven Integration for Eclipse JDT APT" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration (Experimental)" is already installed, so an update will be performed instead.
> "JBoss OpenShift Tools" is already installed, so an update will be performed instead.
> "JBoss Runtime Seam Detector" is already installed, so an update will be performed instead.
> "Seam 3 Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Developer Studio (Core Features) 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta2-v20140613-0252-B130)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.package 8.0.0.Beta1-v20140408-2350-B93)
> Only one of the following can be installed at once:
> JBoss Developer Studio Project Examples 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.project.examples 8.0.0.Beta1-v20140408-2350-B93)
> JBoss Developer Studio Project Examples 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.project.examples 8.0.0.Beta2-v20140613-0252-B130)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta1-v20140408-2350-B93)
> To: com.jboss.devstudio.core.project.examples [8.0.0.Beta1-v20140408-2350-B93]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta2-v20140613-0252-B130)
> To: com.jboss.devstudio.core.project.examples [8.0.0.Beta2-v20140613-0252-B130]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.package 8.0.0.Beta1-v20140408-2350-B93)
> To: com.jboss.devstudio.core.feature.feature.group [8.0.0.Beta1-v20140408-2350-B93]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months