Forum Stats

  • 3,826,763 Users
  • 2,260,705 Discussions


Eclipse Photon / WebLogic server - exception on 'Open launch configuration'

3746158 Member Posts: 4
edited Mar 18, 2019 5:26AM in Enterprise Pack for Eclipse

After upgrading to Eclipse Photon, double clicking on an existing WebLogic server and clicking the 'Open launch configuration' link fails with an exception, the user is not able to edit the configuration.

Issue submitted via the Eclipse error reporter. In the mean time, is there any way to edit the configuration behind the scenes?



  • dvohra21
    dvohra21 Member Posts: 14,576 Gold Crown
    edited Jul 22, 2018 4:58PM

    What is the WebLogic server version? May not be suppoted.

  • 3746158
    3746158 Member Posts: 4
    edited Jul 23, 2018 4:02AM, so a minor patch level or so behind.

  • dvohra21
    dvohra21 Member Posts: 14,576 Gold Crown
    edited Jul 23, 2018 1:48PM

    For Photon use Oracle Enterprise Pack for Eclipse 12c (

    "This release also includes changes to allow OEPE to install on Eclipse 4.8 (Photon) release "

  • User_QN72I
    User_QN72I Member Posts: 2 Green Ribbon
    edited Jul 26, 2018 10:31AM (default) didn't work and then I installed but again, nothing happens when I try and open 'open launch configuration'.

    There's no obvious work-around.

  • dvohra21
    dvohra21 Member Posts: 14,576 Gold Crown
    edited Jul 28, 2018 7:30PM

    Oracle Enterprise Pack for Eclipse ( and  are both supported versions. What seems to be the issue with OEPE? Are supported platforms used? In addition to capabilities provided by Eclipse and Web tools platform, OEPE

    provides premium Oracle WebLogic Server support.

    Seems like some supported system requirement is not used. Please refer System Requirements section

  • User_QN72I
    User_QN72I Member Posts: 2 Green Ribbon
    edited Jul 30, 2018 5:51AM

    However, at this link:

    it says OEPE works with Eclipse 4.8 (Photon):

    What's New in Oracle Enterprise Pack for Eclipse 12c (

    • Oracle Enterprise Pack for Eclipse (OEPE) provides new feature support for creating dedicated connection to Oracle Developer Cloud Service in Oracle Cloud View.
    • This release also includes changes to allow OEPE to install on Eclipse 4.8 (Photon) release along with existing support for latest Eclipse 4.7 release(Oxygen 3a).
    • Eclipse 4.8 (Photon) users can install OEPE through update site.
  • SpecialAgent
    SpecialAgent Member Posts: 7
    edited Jul 31, 2018 4:40AM

    I do have the same problem after I upgraded Eclipse from Oxygen to Photon and installed OEPE from

    Open launch configuration globally and then clicking on "Oracle WebLogic Server" and creating a new one, Im getting the following error in Eclipse Error Log:

    eclipse.buildId=4.8.0.I20180611-0500java.version=1.8.0_172java.vendor=Oracle CorporationBootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DEFramework arguments:  -product org.eclipse.epp.package.jee.productCommand-line arguments:  -os win32 -ws win32 -arch x86_64 -clean -product org.eclipse.epp.package.jee.productorg.eclipse.jfaceErrorTue Jul 31 10:18:45 CEST 2018Problems occurred when invoking code from plug-in: "org.eclipse.jface".java.lang.NoClassDefFoundError: org/eclipse/ui/help/WorkbenchHelp    at$WeblogicServerLaunchConfigurationTab.createControl(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$    at org.eclipse.swt.custom.BusyIndicator.showWhile(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$4.selectionChanged(    at org.eclipse.jface.viewers.StructuredViewer$    at    at org.eclipse.ui.internal.JFaceUtil.lambda$0(    at    at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(    at org.eclipse.jface.viewers.StructuredViewer.setSelection(    at org.eclipse.jface.viewers.TreeViewer.setSelection(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.handleConfigurationAdded(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.access$1(    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView$    at    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(    at org.eclipse.swt.widgets.Display.runAsyncMessages(    at org.eclipse.swt.widgets.Display.readAndDispatch(    at org.eclipse.jface.window.Window.runEventLoop(    at    at    at org.eclipse.debug.ui.DebugUITools$    at org.eclipse.swt.custom.BusyIndicator.showWhile(    at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(    at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(    at    at org.eclipse.jface.action.Action.runWithEvent(    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(    at org.eclipse.jface.action.ActionContributionItem.lambda$4(    at org.eclipse.swt.widgets.EventTable.sendEvent(    at org.eclipse.swt.widgets.Display.sendEvent(    at org.eclipse.swt.widgets.Widget.sendEvent(    at org.eclipse.swt.widgets.Display.runDeferredEvents(    at org.eclipse.swt.widgets.Display.readAndDispatch(    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$    at org.eclipse.core.databinding.observable.Realm.runWithDefault(    at    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(    at org.eclipse.ui.internal.Workbench.lambda$3(    at org.eclipse.core.databinding.observable.Realm.runWithDefault(    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(    at org.eclipse.ui.internal.ide.application.IDEApplication.start(    at    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(    at    at    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    at sun.reflect.NativeMethodAccessorImpl.invoke(    at sun.reflect.DelegatingMethodAccessorImpl.invoke(    at java.lang.reflect.Method.invoke(    at org.eclipse.equinox.launcher.Main.invokeFramework(    at org.eclipse.equinox.launcher.Main.basicRun(    at    at org.eclipse.equinox.launcher.Main.main(
  • SpecialAgent
    SpecialAgent Member Posts: 7
    edited Jul 31, 2018 6:49AM

    I found the poblem:

    In 4.8.0 Photon WorkbenchHelp has been removed, since it is declared as deprecated since 2002. Current OEPE in the area of launch configuration seems to use this class.... please fix this problem and release an update!

    see :

    4. IContextComputer and related classes

    The class and dependent classes, i.e.,, DialogPageContextComputer and ViewContextComputer have been deleted. They were deprecated since 2002.

    For further details or to provide feedback on this change, see bug 442961.

    or here, which has the same problem in Texclipse:

  • dvohra21
    dvohra21 Member Posts: 14,576 Gold Crown
    edited Aug 1, 2018 9:30PM

    Instead of upgrading start with Photon and add the OEPE from the Update site. Issue seems to happen if version is upgraded.

  • 3746158
    3746158 Member Posts: 4
    edited Aug 8, 2018 7:23AM

    Starting with Photon and adding OEPE from the update site is the route I took and it fails. Given what @SpecialAgent has found I don't see how the way it is installed would make any difference. It's a fundamental problem that the Oracle maintainers need to fix and issue an update for. Use of a feature that's been deprecated for 16 years with no attempt to remove it is rather shocking.

This discussion has been closed.