[jjastrow]

I am having trouble with the Scaffold CRUD wizard. I cannot connect to the database using the wizard to view the schema with version 8.6.1. With the previous version 8.6.0 I am able to connect but the wizard fails to create any generated files. My coworker (on 8.6.0 can generate an app with this wizard. I’ve compared our configs and they look the same. I can connect okay with the Database Explorer using a Microsoft or JTDS driver. I get the following error when I run the wizard:

org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:3884)
at org.eclipse.swt.SWT.error(SWT.java:3799)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.skyway.core.generate.ui.wizard.WizardUserInterface.show(WizardUserInterface.java:50)
at org.skyway.core.generate.execute.GenerationInvoker.invokeUserInterface(GenerationInvoker.java:58)
at org.skyway.core.generate.execute.GenerationInvoker.invoke(GenerationInvoker.java:46)
at org.skyway.core.generate.execute.CustomizationAwareGenerationInvoker.invoke(CustomizationAwareGenerationInvoker.java:53)
at com.skyway.scaffolding.crud.action.GenerateCrudApplicationAction.invoke(GenerateCrudApplicationAction.java:31)
at org.skyway.core.generate.ui.action.GenerationObjectActionDelegate.run(GenerationObjectActionDelegate.java:40)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: java.lang.NullPointerException
at com.skyway.myeclipseforspring.persistence.MyEclipseConnectionProfile.getDefaultSchemaName(MyEclipseConnectionProfile.java:261)
at org.skyway.integration.data.persistence.ui.controls.SourceTargetTableSelectionComposite.populateSchemaCombo(SourceTargetTableSelectionComposite.java:389)
at org.skyway.integration.data.persistence.ui.controls.SourceTargetTableSelectionComposite.handleCatalogChange(SourceTargetTableSelectionComposite.java:270)
at org.skyway.integration.data.persistence.ui.controls.SourceTargetTableSelectionComposite.populate(SourceTargetTableSelectionComposite.java:231)
at org.skyway.integration.data.persistence.ui.controls.SourceTargetTableSelectionComposite.setInput(SourceTargetTableSelectionComposite.java:201)
at org.skyway.integration.data.persistence.ui.datatype.wizards.SourceTargetTableSelectionWizardPage$4.run(SourceTargetTableSelectionWizardPage.java:96)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
… 38 more

[jjastrow]

I did try to switch workspaces to the one I had used in 8.6.0 and that let the wizard see my database. However, it still did not generate any files in the generated folder. I ran the app in Tomcat but it just shows the message “This is my JSP page”. Nothing in the Error Log or the Console after the wizard ran. I did see this message in the console after launching Tomcat:

No properties path set – looking for transactions.properties in classpath…
transactions.properties not found – looking for jta.properties in classpath…
Using init file: /C:/javaEnv/apache-tomcat-6.0.29/webapps/SpringTest05/WEB-INF/classes/jta.properties

[jkennedy]

Can you give us a few additional details:

1. Database Vendor and Version
2. Driver and version
3. DB Connect String and User
4. Are you selecting which Schema are visible to the connection on the second panel of the Database connection wizard
5. What is the Database dialect that is being selected in the scaffolding wizard
6. If possible, can you post the DDL for the tables you are scaffolding from

Thanks,
Jack

[jjastrow]

1) Microsoft Sqlserver 2005
2) JTDS version 1.2.5 and also I tried the MS SQL JDBC driver from Microsoft.com (msutil.jar, msbase.jar, & mssqlserver.jar)
3) jdbc:jtds:sqlserver://LWSQLDev:1433/lwPDAS01 and jdbc:microsoft:sqlserver://lwSQLDev:1433 respectively
database username is PDAS_DEV
4) yes, I tried with and without selecting a specific schema
5) that box is grey’d out and disabled
6) no, sorry (this schema has been read successfully by my co-worker so we know it is not an issue with the database, right?)

[jayperkins]

Hi,

I was not able to reproduce this problem in 8.6.1 with the JTDS 1.2.5 driver. I tried it without a database after the port, with a database after the port, but a different username and same database/username.

I was not able to find the 3 jar files that you tried from microsoft. I think those may be Microsoft Sqlserver 2000 jar files, but I’m not sure. I did try it with the latest microsoft driver (see link below) and it worked with the above scenarios (the url is different, of course).

http://msdn.microsoft.com/en-us/data/aa937724.aspx

Please try the latest microsoft driver and let me know if you still have problems. If you would prefer to use the jtds driver, then it may be easier for us to communicate directly so I can get screenshots, etc to determine where it is failing.

Thanks,
Jay

[jjastrow]

I do prefer to use the jtds driver. Please tell me what I can send you that will help you analyze my problem.

[jayperkins]

Please provide a screenshot of your connection profile properties (Select the connection in the database explorer perspective, db browser view, right click your connection profile, select Edit…).
Disconnect all connections for that profile.
Clear out your error log.
Scaffold, selecting that database profile.
Send a screenshot of the “Select Database Tables” wizard page when you first navigate to it.
Note if an error shows up in the error log.
If you perform other steps from this point, please peform each step and then provide a description of that step and a screenshot of the result and any errors that may show in the error log after that step. For example, if you change catalogs or something like that, provide that information.
It is my understanding that you get an error on this screen so you don’t have to continue any further past this screen. Unless you are actually getting an error later on in your process then we will need to discuss that aspect.

[Author]

Posts