Consultor Eletrônico



Kbase P131605: Outline view empty after importing existing project from 10.1B into 10.1C
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   02/12/2008
Status: Verified

SYMPTOM(s):

Outline view empty after importing existing project from 10.1B into 10.1C

Colorization not working after importing project from earlier release

Syntax recognition not working in editor after erroneous database connection information is added

Delays occur after typing temp-table name in editor

java.lang.NullPointerException

com.openedge.pdt.text.connection.DatabaseConnectionManager.loadDatabase

java.lang.NullPointerException
at com.openedge.pdt.text.connection.DatabaseConnectionManager.loadDatabase(DatabaseConnectionManager.java:1327)
at com.openedge.pdt.text.help.OEDataword.getDatabases(OEDataword.java:257)
at com.openedge.pdt.text.help.OEDataword.searchDatawordTables(OEDataword.java:91)
at com.openedge.pdt.text.help.OEWord.searchDataWords(OEWord.java:105)
at com.openedge.pdt.text.help.OEWord.getColorToken(OEWord.java:252)
at com.openedge.pdt.text.editor.rules.CasedWordRule.evaluate(CasedWordRule.java:89)
at org.eclipse.jface.text.rules.RuleBasedScanner.nextToken(RuleBasedScanner.java:155)
at org.eclipse.jface.text.rules.DefaultDamagerRepairer.createPresentation(DefaultDamagerRepairer.java:168)
at org.eclipse.jface.text.presentation.PresentationReconciler.createPresentation(PresentationReconciler.java:448)
at org.eclipse.jface.text.presentation.PresentationReconciler.processDamage(PresentationReconciler.java:560)
at org.eclipse.jface.text.presentation.PresentationReconciler.access$3(PresentationReconciler.java:558)
at org.eclipse.jface.text.presentation.PresentationReconciler$InternalListener.textChanged(PresentationReconciler.java:224)
at org.eclipse.jface.text.TextViewer.updateTextListeners(TextViewer.java:2396)
at org.eclipse.jface.text.TextViewer.invalidateTextPresentation(TextViewer.java:3048)
at org.eclipse.jface.text.source.projection.ProjectionViewer.executeProjectionCommands(ProjectionViewer.java:1035)
at org.eclipse.jface.text.source.projection.ProjectionViewer.catchupWithProjectionAnnotationModel(ProjectionViewer.java:1007)
at org.eclipse.jface.text.source.projection.ProjectionViewer.access$5(ProjectionViewer.java:949)
at org.eclipse.jface.text.source.projection.ProjectionViewer$1.run(ProjectionViewer.java:907)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:156)
at org.eclipse.ui.internal.ide.actions.ProjectPropertyDialogAction.run(ProjectPropertyDialogAction.java:77)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
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(E.clipseAppLauncher.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).

FACT(s) (Environment):

Windows 32 Intel
OpenEdge 10.1x
OpenEdge 10.1C

CAUSE:

Bug# OE00163251

CAUSE:

There is a known issue which may happen in a number of scenarios but primarily it occurs when there is an error configuring/connecting databases through JDBC. In some cases because the database location or configuration changed, some when using an improper JDBC driver to connect to the database and still others after importing existing project settings from an earlier release fails and offsets the settings.
The primary evidence that you may be running into this issue would include the presence of errors in the loadDatabase method and you are having problems viewing resources that would use the database schema, including the AST build, which feeds underlining, colorization, outlining and other features in the Architect editor. Another way to determine if you're hitting this issue is to look in the <WorkspaceDir>\.metadata\.plugins\com.openedge.pdt.text directory for files named "<GUID>.txt" (GUID being a long alpha-numeric string) and verify that they are empty.

FIX:

Upgrade to OpenEdge Release 10.1C01 or higher

FIX:

To workaround this issue fix the incorrect database connection or jdbc driver information then delete the <GUID>.txt file.