[Hibernate-JIRA] Commented: (ANN-120) Map, OneToMany, join table or @ManyToMany does not work
by Emmanuel Bernard (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-120?page=co... ]
Emmanuel Bernard commented on ANN-120:
--------------------------------------
It should be fixed now see ANN-414
> Map, OneToMany, join table or @ManyToMany does not work
> -------------------------------------------------------
>
> Key: ANN-120
> URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-120
> Project: Hibernate Annotations
> Type: Improvement
> Components: binder
> Versions: 3.1beta6
> Environment: Hibernate 3.1 RC1, Annotations 3.1b6, Java 1.5.0_05
> Reporter: Mattias Arbin
> Assignee: Emmanuel Bernard
> Fix For: 3.2.0.cr1
> Attachments: KeyValue.java, KeyValue2.java, MyEntity.java, MyEntity2.java, TestKeyValue.java, TestKeyValue2.java
>
>
> Seems like there is a problem with mapping a Map using join table.
> I have a relation like this:
> @OneToMany(cascade=CascadeType.ALL)
> @MapKey(name="name")
> public Map<String, KeyValue> getProps() {
> return props;
> }
> The correct tables are created and inserting data works fine. When loading, however, I get the error below.
> When using a join column, everything works fine:
> @OneToMany(cascade=CascadeType.ALL)
> @MapKey(name="name")
> @JoinColumn(name="myentity_id")
> public Map<String, KeyValue> getProps() {
> return props;
> }
> Attached the two test classes.
> The error:
> ...
> Hibernate: select this_.id as id3_0_ from test_MyEntity this_
> Hibernate: select props0_.MyEntity_id as MyEntity1_1_, props0_.props_id as props2_1_, props0_.name as formula0_1_, keyvalue1_.id as id2_0_, keyvalue1_.val as val2_0_, keyvalue1_.name as name2_0_ from test_MyEntity_KeyValue props0_ left outer join test_KeyValue keyvalue1_ on props0_.props_id=keyvalue1_.id where props0_.MyEntity_id=?
> 15:11:49,078 WARN JDBCExceptionReporter:71 - SQL Error: 1054, SQLState: 42S22
> Exception in thread "main" 15:11:49,078 ERROR JDBCExceptionReporter:72 - null, message from server: "Unknown column 'props0_.name' in 'field list'"
> org.hibernate.exception.SQLGrammarException: could not initialize a collection: [test.data.MyEntity.props#1]
> at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:65)
> at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
> at org.hibernate.loader.Loader.loadCollection(Loader.java:1923)
> at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:71)
> at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520)
> at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60)
> at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1565)
> at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344)
> at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86)
> at org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:161)
> at org.hibernate.collection.PersistentMap.get(PersistentMap.java:127)
> at test.TestKeyValue.test(TestKeyValue.java:43)
> at test.TestKeyValue.main(TestKeyValue.java:57)
> Caused by: java.sql.SQLException: null, message from server: "Unknown column 'props0_.name' in 'field list'"
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1876)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1098)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1192)
> at com.mysql.jdbc.Connection.execSQL(Connection.java:2051)
> at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1496)
> at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:137)
> at org.hibernate.loader.Loader.getResultSet(Loader.java:1676)
> at org.hibernate.loader.Loader.doQuery(Loader.java:662)
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223)
> at org.hibernate.loader.Loader.loadCollection(Loader.java:1916)
> ... 10 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 5 months
[Hibernate-JIRA] Created: (HHH-2004) Get more information about SQL exceptions in batched execution environments
by Claus Schmid (JIRA)
Get more information about SQL exceptions in batched execution environments
---------------------------------------------------------------------------
Key: HHH-2004
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2004
Project: Hibernate3
Type: New Feature
Components: core
Environment: All environments
Reporter: Claus Schmid
When, e.g., performing bulk operations (inserts, updates, deletes) in a batched configuration, the operations are added to the batched statement and then submitted at once (on a batch-per-batch basis). When errors occur, e.g. constraint violations, an exception is thrown. There are situations where it can be extremely helpful to determine which one(s) of the bulk operation(s) failed and to which object(s) the operation(s) pertained.
An example:
In our application, we have a bulk upload function which allows a user to upload data via a web interface. The data is converted to objects and the objects are then persisted. When the transaction is committed (for the whole bulk upload at once) and an error occurs, a single exception is thrown for the whole transaction. It wraps around a java.sql.BatchUpdateException which gives us access to an array of update counts. In this array, we can see for every single one of the batched operations which one failed and which one succeeded.
Let's assume that the while bulk upload contained a single object which duplicates an already existing object in the database, and some alternate key would be violated. In this case, we would get a constraint violation. We could see from the update count array that there was one error and many successful operations. But we would not be able to relate the particular row in the update count array to any of the objects that we persisted. So all we could tell the user was that one of his objects is duplicate, but not which one. Of course, the user now has the arduous task of checking his upload data against database contents, or to use some divide-and-conquer strategy to upload the data part by part, and dividing those parts that failed again.
If, however, one had access to the array of operations in a batch in the order in which they were batched, one could match them against the entries in the update count array, and immediately figure out the "bad" objects. From this information, one could then send a meaningful error message back to the user, identifying the object that caused the exception.
Of course, having such a facility would also help in any other situation where batched execution was used within the guts of Hibernate, in identifying the culprit responsible for the failure.
In many such cases, reverting to a non-batched configuration may not be useful because of performance issues.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 5 months
[Hibernate-JIRA] Commented: (ANN-120) Map, OneToMany, join table or @ManyToMany does not work
by Odd Möller (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-120?page=co... ]
Odd Möller commented on ANN-120:
--------------------------------
Maybe this is a known problem/limitation, but the changes done (to resolve this issue) in revision 9894 to the createFormulatedValue method (line 271) of the org.hibernate.cfg.annotations.MapBinder class, seperates conditions (when multiple collection columns exist) in the where clause with a comma (',') instead of 'and'. This results in a malformed SQL syntax exception (at least with HSQLDB). When I change the ',' to 'and' the exception does not occur.
> Map, OneToMany, join table or @ManyToMany does not work
> -------------------------------------------------------
>
> Key: ANN-120
> URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-120
> Project: Hibernate Annotations
> Type: Improvement
> Components: binder
> Versions: 3.1beta6
> Environment: Hibernate 3.1 RC1, Annotations 3.1b6, Java 1.5.0_05
> Reporter: Mattias Arbin
> Assignee: Emmanuel Bernard
> Fix For: 3.2.0.cr1
> Attachments: KeyValue.java, KeyValue2.java, MyEntity.java, MyEntity2.java, TestKeyValue.java, TestKeyValue2.java
>
>
> Seems like there is a problem with mapping a Map using join table.
> I have a relation like this:
> @OneToMany(cascade=CascadeType.ALL)
> @MapKey(name="name")
> public Map<String, KeyValue> getProps() {
> return props;
> }
> The correct tables are created and inserting data works fine. When loading, however, I get the error below.
> When using a join column, everything works fine:
> @OneToMany(cascade=CascadeType.ALL)
> @MapKey(name="name")
> @JoinColumn(name="myentity_id")
> public Map<String, KeyValue> getProps() {
> return props;
> }
> Attached the two test classes.
> The error:
> ...
> Hibernate: select this_.id as id3_0_ from test_MyEntity this_
> Hibernate: select props0_.MyEntity_id as MyEntity1_1_, props0_.props_id as props2_1_, props0_.name as formula0_1_, keyvalue1_.id as id2_0_, keyvalue1_.val as val2_0_, keyvalue1_.name as name2_0_ from test_MyEntity_KeyValue props0_ left outer join test_KeyValue keyvalue1_ on props0_.props_id=keyvalue1_.id where props0_.MyEntity_id=?
> 15:11:49,078 WARN JDBCExceptionReporter:71 - SQL Error: 1054, SQLState: 42S22
> Exception in thread "main" 15:11:49,078 ERROR JDBCExceptionReporter:72 - null, message from server: "Unknown column 'props0_.name' in 'field list'"
> org.hibernate.exception.SQLGrammarException: could not initialize a collection: [test.data.MyEntity.props#1]
> at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:65)
> at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
> at org.hibernate.loader.Loader.loadCollection(Loader.java:1923)
> at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:71)
> at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520)
> at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60)
> at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1565)
> at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344)
> at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86)
> at org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:161)
> at org.hibernate.collection.PersistentMap.get(PersistentMap.java:127)
> at test.TestKeyValue.test(TestKeyValue.java:43)
> at test.TestKeyValue.main(TestKeyValue.java:57)
> Caused by: java.sql.SQLException: null, message from server: "Unknown column 'props0_.name' in 'field list'"
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1876)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1098)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1192)
> at com.mysql.jdbc.Connection.execSQL(Connection.java:2051)
> at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1496)
> at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:137)
> at org.hibernate.loader.Loader.getResultSet(Loader.java:1676)
> at org.hibernate.loader.Loader.doQuery(Loader.java:662)
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223)
> at org.hibernate.loader.Loader.loadCollection(Loader.java:1916)
> ... 10 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 5 months
[Hibernate-JIRA] Closed: (HBX-697) NPE when attempting to view entity with null valued, joined properties
by Max Rydahl Andersen (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-697?page=all ]
Max Rydahl Andersen closed HBX-697:
-----------------------------------
Fix Version: 3.2beta7
(was: 3.2LATER)
Resolution: Fixed
> NPE when attempting to view entity with null valued, joined properties
> ----------------------------------------------------------------------
>
> Key: HBX-697
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-697
> Project: Hibernate Tools
> Type: Bug
> Components: eclipse
> Versions: 3.2beta6
> Environment: eclipse.buildId=M20060629-1905
> java.version=1.5.0_07
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Command-line arguments: -os linux -ws gtk -arch x86_64
> Reporter: Jacob L E Blain Christen
> Priority: Minor
> Fix For: 3.2beta7
> Attachments: HibernatePropertySourceProvider.patch, hbtools697.sql, hbtools697.zip
>
>
> I am getting a null pointer exception when attempting to view an entity in the properties view (e.g. clicking on a "Hibernate Query Result" after running some HQL through the console). This isn't a super major bug but it is annoying because I was using hibernate console to get quick feedback on tweaks I make to my mappings while developing and lost a few hours on the assumption that the error was just HB Tools's way of telling me they were bad =(
> This is happening on an object that has some joins to aggregate some optional data. A snippet of the mapping:
> <join optional="true" table="item_instruments">
> <key column="item" unique="true" />
> <many-to-one name="instrumentInfo" column="item" unique="true" insert="false" update="false" />
> </join>
> <join optional="true" table="item_stackables">
> <key column="item" unique="true"/>
> <property name="stackSize" column="stacksize" type="java.lang.Short" />
> </join>
> If any of the properties on the mapped object defined with joins are null, the following NPE occurs and the properties window does nothing (silently ignoring the problem):
> java.lang.NullPointerException
> at org.hibernate.proxy.HibernateProxyHelper.getClassWithoutInitializingProxy(HibernateProxyHelper.java:23)
> at org.hibernate.eclipse.console.views.properties.HibernatePropertySourceProvider.hasMetaData(HibernatePropertySourceProvider.java:47)
> at org.hibernate.eclipse.console.views.properties.HibernatePropertySourceProvider.getPropertySource(HibernatePropertySourceProvider.java:36)
> at org.eclipse.ui.views.properties.PropertySheetEntry.getPropertySource(PropertySheetEntry.java:470)
> at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:759)
> at org.eclipse.ui.views.properties.PropertySheetEntry.refreshValues(PropertySheetEntry.java:622)
> at org.eclipse.ui.views.properties.PropertySheetEntry.refreshChildEntries(PropertySheetEntry.java:575)
> at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:767)
> at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:943)
> at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:473)
> at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:218)
> at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156)
> at org.eclipse.ui.internal.AbstractSelectionService$1.selectionChanged(AbstractSelectionService.java:62)
> at org.hibernate.eclipse.console.views.QueryPageTabView.fireSelectionChangedEvent(QueryPageTabView.java:151)
> at org.hibernate.eclipse.console.views.QueryPageViewer.tableDoubleClicked(QueryPageViewer.java:212)
> at org.hibernate.eclipse.console.views.QueryPageViewer.access$0(QueryPageViewer.java:207)
> at org.hibernate.eclipse.console.views.QueryPageViewer$3.selectionChanged(QueryPageViewer.java:201)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at org.eclipse.core.runtime.Platform.run(Platform.java:843)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:1976)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1128)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1154)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:213)
> at org.eclipse.jface.util.OpenStrategy.access$3(OpenStrategy.java:207)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:374)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3164)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2840)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 5 months
[Hibernate-JIRA] Reopened: (HBX-697) NPE when attempting to view entity with null valued, joined properties
by Max Rydahl Andersen (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-697?page=all ]
Max Rydahl Andersen reopened HBX-697:
-------------------------------------
> NPE when attempting to view entity with null valued, joined properties
> ----------------------------------------------------------------------
>
> Key: HBX-697
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-697
> Project: Hibernate Tools
> Type: Bug
> Components: eclipse
> Versions: 3.2beta6
> Environment: eclipse.buildId=M20060629-1905
> java.version=1.5.0_07
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Command-line arguments: -os linux -ws gtk -arch x86_64
> Reporter: Jacob L E Blain Christen
> Priority: Minor
> Fix For: 3.2LATER
> Attachments: HibernatePropertySourceProvider.patch, hbtools697.sql, hbtools697.zip
>
>
> I am getting a null pointer exception when attempting to view an entity in the properties view (e.g. clicking on a "Hibernate Query Result" after running some HQL through the console). This isn't a super major bug but it is annoying because I was using hibernate console to get quick feedback on tweaks I make to my mappings while developing and lost a few hours on the assumption that the error was just HB Tools's way of telling me they were bad =(
> This is happening on an object that has some joins to aggregate some optional data. A snippet of the mapping:
> <join optional="true" table="item_instruments">
> <key column="item" unique="true" />
> <many-to-one name="instrumentInfo" column="item" unique="true" insert="false" update="false" />
> </join>
> <join optional="true" table="item_stackables">
> <key column="item" unique="true"/>
> <property name="stackSize" column="stacksize" type="java.lang.Short" />
> </join>
> If any of the properties on the mapped object defined with joins are null, the following NPE occurs and the properties window does nothing (silently ignoring the problem):
> java.lang.NullPointerException
> at org.hibernate.proxy.HibernateProxyHelper.getClassWithoutInitializingProxy(HibernateProxyHelper.java:23)
> at org.hibernate.eclipse.console.views.properties.HibernatePropertySourceProvider.hasMetaData(HibernatePropertySourceProvider.java:47)
> at org.hibernate.eclipse.console.views.properties.HibernatePropertySourceProvider.getPropertySource(HibernatePropertySourceProvider.java:36)
> at org.eclipse.ui.views.properties.PropertySheetEntry.getPropertySource(PropertySheetEntry.java:470)
> at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:759)
> at org.eclipse.ui.views.properties.PropertySheetEntry.refreshValues(PropertySheetEntry.java:622)
> at org.eclipse.ui.views.properties.PropertySheetEntry.refreshChildEntries(PropertySheetEntry.java:575)
> at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:767)
> at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:943)
> at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:473)
> at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:218)
> at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156)
> at org.eclipse.ui.internal.AbstractSelectionService$1.selectionChanged(AbstractSelectionService.java:62)
> at org.hibernate.eclipse.console.views.QueryPageTabView.fireSelectionChangedEvent(QueryPageTabView.java:151)
> at org.hibernate.eclipse.console.views.QueryPageViewer.tableDoubleClicked(QueryPageViewer.java:212)
> at org.hibernate.eclipse.console.views.QueryPageViewer.access$0(QueryPageViewer.java:207)
> at org.hibernate.eclipse.console.views.QueryPageViewer$3.selectionChanged(QueryPageViewer.java:201)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at org.eclipse.core.runtime.Platform.run(Platform.java:843)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:1976)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1128)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1154)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:213)
> at org.eclipse.jface.util.OpenStrategy.access$3(OpenStrategy.java:207)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:374)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3164)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2840)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 5 months