[amattas]

org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:3374)
at org.eclipse.swt.SWT.error(SWT.java:3297)
at org.eclipse.swt.SWT.error(SWT.java:3268)
at org.eclipse.swt.widgets.Widget.error(Widget.java:435)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:331)
at org.eclipse.swt.widgets.Widget.checkParent(Widget.java:269)
at org.eclipse.swt.widgets.Widget.<init>(Widget.java:141)
at org.eclipse.swt.widgets.Control.<init>(Control.java:96)
at org.eclipse.swt.widgets.Scrollable.<init>(Scrollable.java:72)
at org.eclipse.swt.widgets.Composite.<init>(Composite.java:93)
at org.eclipse.ui.internal.PartPane.createControl(PartPane.java:136)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:402)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214)
at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:395)
at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:373)
at org.eclipse.ui.internal.WorkbenchPage.findEditor(WorkbenchPage.java:1914)
at com.genuitec.eclipse.springhibernate.configuration.SpringBeansConfigFile.getXMLModelFromOpenEditors(SpringBeansConfigFile.java:125)
at com.genuitec.eclipse.springhibernate.configuration.SpringBeansConfigFile.configureModel(SpringBeansConfigFile.java:68)
at com.genuitec.eclipse.springhibernate.configuration.SpringBeansConfigFile.<init>(SpringBeansConfigFile.java:58)
at com.genuitec.eclipse.hibernate.util.PersistenceFile.<init>(PersistenceFile.java:31)
at com.genuitec.eclipse.hibernate.wizards.GenerateArtifactsJob$3.execute(GenerateArtifactsJob.java:436)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:56)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:89)
at com.genuitec.eclipse.hibernate.wizards.GenerateArtifactsJob.run(GenerateArtifactsJob.java:388)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

[Riyad Kalla]

This can happen on Linux when you have MyEclipse installed as a separate user than the base Eclipse platform and are trying to run it during the trial period.

The workaround is to install Eclipse and MyEclipse all as the same user.

[amattas]

This is on a Windows system, when I am trying to reverse engineer a database for EJB3, only occurs when I create the Facade class. That database ia laid out as follows.

[Table:Users]
username [var char, pk]
password [var char]

[Table:Groups]
id [serial, pk]
username [var char, fk:users]
groupname [var char]

Database is running on Postgresql, and is using the latest version of the driver.

[Riyad Kalla]

Can you go to MyEclipse > Installation SUmmary > Installation Details and paste the information here for me to look at?

[amattas]

*** Date:
Tuesday, June 19, 2007 1:46:35 PM EDT

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.6.0_01

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 5.5.1 GA
Build id: 20070521-5.5.1-GA

*** Eclipse details:
Eclipse SDK

Version: 3.2.2
Build id: M20070212-1330

Eclipse Project SDK

Version: 3.2.2.r322_v20070104-dCGKm0Ln38lm-8s
Build id: M20070212-1330

Eclipse Platform

Version: 3.2.2.r322_v20070119-RQghndJN8IM0MsK
Build id: M20070212-1330

Eclipse RCP

Version: 3.2.2.r322_v20070104-8pcviKVqd8J7C1U
Build id: M20070212-1330

Eclipse Plug-in Development Environment

Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20070212-1330

Eclipse Java Development Tools

Version: 3.2.2.r322_v20070104-R4CR0Znkvtfjv9-
Build id: M20070212-1330

Eclipse Graphical Editing Framework

Version: 3.2.2.v20070208
Build id: 20070208-1315

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\java\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
874_7c
-vm
C:\WINDOWS\system32\javaw.exe

[Riyad Kalla]

Do you have a 1.5.0_08 or later JRE installed that you can run MyEclipse with? Using Java 6 breaks some things, and while we aren’t aware of issues with the DB Explorer, I’m just curious if that would fix it… another thing to try would be a different version of the PostgreSQL JDBC driver to see if that changes the behavior. One of our devs worked with Post a lot and doesn’t report any issues.

[amattas]

I will try it with a J5 JDK and report back.

[amattas]

I actually have traced down the Problem, it occured when I refactor->renamed the enterprise bean, I named it back to the original and renamed it again and it seems to have fixed the problem.

[Riyad Kalla]

Great catch, I’m glad it’s working now.

[Author]

Posts