-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 13 posts ] 
Author Message
 Post subject: Eclipse install error: Invalid Menu Extension?
PostPosted: Thu Jun 08, 2006 2:40 pm 
Newbie

Joined: Sun Jun 04, 2006 7:02 am
Posts: 7
Location: Hoboken
I just installed the Hibernate Tools plug-in 3.1.0.beta5 into Eclipse Version: 3.1.2 Build id: M20060118-1600.
After launching Eclipse, I receive the following error in the Error Log:

Invalid Menu Extension (Path is invalid): org.hibernate.eclipse.launch.LaunchMenuDelegateMenu

I think it may be a configuration error in C:\eclipse\plugins\org.hibernate.eclipse.console_3.1.0.beta5\plug-in.xml, because I find the "missing" class in C:\eclipse\plugins\org.hibernate.eclipse.console_3.1.0.beta5\org.hibernate.eclipse.console.jar

But I'm relatively new to Eclipse plug-ins and this is just a guess.

Any suggestions?

TIA,
Ed


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jun 08, 2006 11:36 pm 
Newbie

Joined: Sun Jun 04, 2006 7:02 am
Posts: 7
Location: Hoboken
Follow-up info:
I altered plugin.xml to change the menu path of the action from
Code:
menubarPath="org.eclipse.ui.run/HibernateToolsGroup"
to
Code:
menubarPath="HibernateToolsGroup"
. This eliminates the error and placed the action in the main menu bar. However, now when I attempt to create a new code generation configuration, I get the following error:

Code:
java.lang.NoSuchMethodError: java.lang.Boolean.parseBoolean(Ljava/lang/String;)Z
at org.hibernate.eclipse.console.model.impl.ExporterDefinition.createProperties(ExporterDefinition.java:70)
at org.hibernate.eclipse.console.model.impl.ExporterDefinition.<init>(ExporterDefinition.java:50)
at org.hibernate.eclipse.console.ExtensionManager.findExporterDefinitions(ExtensionManager.java:54)
at org.hibernate.eclipse.launch.ExporterSettings.createControl(ExporterSettings.java:80)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showTabsFor(LaunchConfigurationTabGroupViewer.java:720)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:639)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:519)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$5.run(LaunchConfigurationTabGroupViewer.java:471)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:488)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:452)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:789)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:601)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:763)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
at org.eclipse.core.runtime.Platform.run(Platform.java:783)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:761)
at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1453)
at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:379)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.handleConfigurationAdded(LaunchConfigurationView.java:270)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.launchConfigurationAdded(LaunchConfigurationView.java:251)
at org.eclipse.debug.internal.core.LaunchManager$ConfigurationNotifier.run(LaunchManager.java:1581)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
at org.eclipse.core.runtime.Platform.run(Platform.java:783)
at org.eclipse.debug.internal.core.LaunchManager$ConfigurationNotifier.notify(LaunchManager.java:1605)
at org.eclipse.debug.internal.core.LaunchManager.launchConfigurationAdded(LaunchManager.java:806)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.writeNewFile(LaunchConfigurationWorkingCopy.java:278)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave0(LaunchConfigurationWorkingCopy.java:233)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave(LaunchConfigurationWorkingCopy.java:174)
at org.eclipse.debug.internal.ui.launchConfigurations.CreateLaunchConfigurationAction.performAction(CreateLaunchConfigurationAction.java:75)
at org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAction$1.run(AbstractLaunchConfigurationAction.java:103)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAction.run(AbstractLaunchConfigurationAction.java:106)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$ButtonActionNew.run(LaunchConfigurationsDialog.java:1461)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$1.widgetSelected(LaunchConfigurationsDialog.java:1430)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
at org.eclipse.jface.window.Window.open(Window.java:787)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:439)
at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:356)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:360)
at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:302)
at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:80)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
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:843)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
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:324)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)


Has anyone encountered this?


Top
 Profile  
 
 Post subject:
PostPosted: Fri Jun 09, 2006 12:06 am 
Newbie

Joined: Sun Jun 04, 2006 7:02 am
Posts: 7
Location: Hoboken
Follow-up:
I found the post, "Beta5 Problems invoking: "org.eclipse.jface".", and learned that the Tools code is currently dependent on jdk1.5. When I re-configured eclipse for 1.5, everything is working. As long as the generated code is 1.4 compliant, this shouldn't be a problem (my target environment is Websphere).

-Ed


Top
 Profile  
 
 Post subject:
PostPosted: Fri Jun 09, 2006 2:59 am 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
the tools in jboss ide 1.6 is not dependent on 1.5 and the nightly builds is also not dependent on 1.5.

_________________
Max
Don't forget to rate


Top
 Profile  
 
 Post subject: Still got the error!!!
PostPosted: Sun Jun 11, 2006 12:38 pm 
Newbie

Joined: Sun Jun 11, 2006 12:22 pm
Posts: 2
Version: 3.1.2
Build id: M20060118-1600

I still get this error:
Error 2006-06-11 18:34:55.171 Invalid Menu Extension (Path is invalid): org.hibernate.eclipse.launch.LaunchMenuDelegateMenu


I've tried to change the path as suggested above and I've used 1.5 and 1.4.2_09

But I still get the same error finally I've also tried with eclipse 3.1.1....


I get contact to the database and is going to make a generate and then I get the errror


Top
 Profile  
 
 Post subject:
PostPosted: Sun Jun 11, 2006 12:45 pm 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
do you get the menu path error when do reveng ? never seen that.

_________________
Max
Don't forget to rate


Top
 Profile  
 
 Post subject:
PostPosted: Sun Jun 11, 2006 3:26 pm 
Newbie

Joined: Sun Jun 11, 2006 12:22 pm
Posts: 2
well accordingly to the PDF "hibernate_tools.pdf" page 8 in the bottom


"When you click on "Hibernate Code Generation" the standard Eclipse launcher dialog will appear. In this dialog you can create, edit and delete named Hibernate code generation "launchers"."

But when the launcer is not there and when trying add it through commands (to click it active) I get this error...

I've tried with 3.1.2 and 3.1.1 to different jdk and the tip above...


Top
 Profile  
 
 Post subject:
PostPosted: Sun Jun 11, 2006 4:54 pm 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
ok got it.

_________________
Max
Don't forget to rate


Top
 Profile  
 
 Post subject: Been having same problem
PostPosted: Tue Jun 13, 2006 2:49 pm 
Newbie

Joined: Tue Jun 13, 2006 2:45 pm
Posts: 4
I was having the identical problem. I was running Eclipse with JDK 1.4.2.

What worked for me was that I installed the 1.5.0_07 JDK, switched the engine in Eclipse. I was still getting the same problem afterwards. Once I deleted the Hibernate configuration and started from scratch, the exceptions all went away.

_________________
John


Top
 Profile  
 
 Post subject: Menu missing
PostPosted: Tue Jun 13, 2006 3:03 pm 
Newbie

Joined: Tue Jun 13, 2006 2:45 pm
Posts: 4
I have been hunting for the Code Generation Menu but it appears to be missing for my installation (as well). At least there are no exceptions...

_________________
John


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jun 14, 2006 4:05 am 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
get the latest version from jbosside 1.6 it should not have this issue.

_________________
Max
Don't forget to rate


Top
 Profile  
 
 Post subject: Invalid Menu Extension (Path is invalid): org.hibernate.ecli
PostPosted: Thu Jan 25, 2007 1:10 pm 
Newbie

Joined: Tue Jan 23, 2007 12:49 pm
Posts: 1
!ENTRY org.eclipse.ui 4 4 2007-01-25 11:53:39.470
!MESSAGE Invalid Menu Extension (Path is invalid): org.hibernate.eclipse.launch.LaunchMenuDelegateMenu

The problem persists! I am using the latest nightly build form jBoss!

The problem is NOT org.hibernate.eclipse.launch.LaunchMenuDelegateMenu
Nor has it to do with any JDK issues.

It is this line in the plugin.xml:
menubarPath="org.eclipse.ui.run/HibernateToolsGroup"

The menubarPath "org.eclipse.ui.run" is not found at this time of point when
eclipse starts.
But the menu item will be created later on when eclipse actullay builds up the UI components.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jan 25, 2007 1:16 pm 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
yeah is eclipse dev not great...the problem were gone for 4 releases and without changing anything on that menu delegate it is back again.

Apparently some other extension point have changed the "startup" sequence of plugins....hurray (not).

Anyone who wants to chip in a provide a patch that are deterministic is more than welcome.

_________________
Max
Don't forget to rate


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 13 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.