March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10414) Enable Hibernate 3 support title in Project Properties even when Hibernate 4 can be used

by Jiri Peterka (Created) (JIRA)

Enable Hibernate 3 support title in Project Properties even when Hibernate 4 can be used ---------------------------------------------------------------------------------------- Key: JBIDE-10414 URL: https://issues.jboss.org/browse/JBIDE-10414 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M5 Environment: JBT 3.3.0.trunk (pre-M5), Linux 64 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Priority: Minor Fix For: 3.3.0.Beta1 See Hibernate Setting under Project, there is Enable Hibernate 3 support. From M5 there is support also for Hibernate 4 so this should be changed for example just to Enable Hibernate support or Enable Hibernate 3/4 support -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10770) ClassNotFoundException while running hibernate code generation configuration

by Ivo Bek (JIRA)

Ivo Bek created JBIDE-10770: ------------------------------- Summary: ClassNotFoundException while running hibernate code generation configuration Key: JBIDE-10770 URL: https://issues.jboss.org/browse/JBIDE-10770 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M5 Environment: Linux 64b, HSQLDB 1.8, JBDS 5.0.0.M5 Reporter: Ivo Bek Assignee: Dmitry Geraskov Follow the steps for catch exception. I received 2 different ClassNotFoundExceptions net.sf.cglib.core.KeyFactory and org.hibernate.cfg.reveng.OverrideRepository. I think that from hibernate tools, the classes should be there. This is from error log: {code:title=Error log|borderStyle=solid} eclipse.buildId=unknown java.version=1.6.0_26 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product com.jboss.jbds.product.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.jbds.product.product Error Wed Feb 01 10:43:11 CET 2012 org.hibernate.console.HibernateConsoleRuntimeException: Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class org.hibernate.console.HibernateConsoleRuntimeException: Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.launchExporters(ConsoleExtension4_0.java:135) at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.launch(CodeGenerationLaunchDelegate.java:268) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:928) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1132) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.cfg.reveng.OverrideRepository at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0$3.execute(ConsoleExtension4_0.java:234) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.jboss.tools.hibernate4_0.HibernateExtension4_0.execute(HibernateExtension4_0.java:248) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.buildConfiguration(ConsoleExtension4_0.java:224) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.runExporters(ConsoleExtension4_0.java:154) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.launchExporters(ConsoleExtension4_0.java:118) ... 6 more {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-10811) NPE while using Contet Assist in

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-10811: ------------------------------------ Summary: NPE while using Contet Assist in Key: JBIDE-10811 URL: https://issues.jboss.org/browse/JBIDE-10811 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M5 Environment: JBDS 5.0.0.M5, L64 Reporter: Jiri Peterka Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta1 java.lang.NullPointerException at org.jboss.tools.ws.jaxrs.ui.contentassist.PathParamAnnotationValueCompletionProposalComputer.computeCompletionProposals(PathParamAnnotationValueCompletionProposalComputer.java:84) at org.eclipse.jdt.internal.ui.text.java.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:318) at org.eclipse.jdt.internal.ui.text.java.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:267) at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:283) at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:243) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1830) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:556) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:553) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:488) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482) at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1656) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor$AdaptedSourceViewer.doOperation(CompilationUnitEditor.java:183) at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1531) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1257) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1294) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:730) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3019) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:734) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1743) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5016) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4408) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8422) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1245) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2276) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:344) 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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-10501) NPE without stacktrace when trying M5a

by Juergen Zimmermann (Created) (JIRA)

NPE without stacktrace when trying M5a -------------------------------------- Key: JBIDE-10501 URL: https://issues.jboss.org/browse/JBIDE-10501 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M5 Reporter: Juergen Zimmermann Assignee: Dmitry Geraskov I tried JBossTools M5a from http://download.jboss.org/jbosstools/builds/development/3.3.0.M5a.core/20... using Hibernate 4 and got a NPE. I'll provide a screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

8
8
0 / 0

[JBoss JIRA] (JBDS-1977) Bar menu on MacOSX says jbdevstudio instead of "JBoss Developer Studio"

by Denis Golovin (Created) (JIRA)

Bar menu on MacOSX says jbdevstudio instead of "JBoss Developer Studio" ----------------------------------------------------------------------- Key: JBDS-1977 URL: https://issues.jboss.org/browse/JBDS-1977 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.M5 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 5.0.0.Beta1 should be configured inside product definition file as vm parameter for MacOSX -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
4
0 / 0

[JBoss JIRA] (JBDS-1973) uni-installer does not rename jbdevstudio.app to JBoss Developer Studio.app on osx

by Max Rydahl Andersen (Created) (JIRA)

uni-installer does not rename jbdevstudio.app to JBoss Developer Studio.app on osx ---------------------------------------------------------------------------------- Key: JBDS-1973 URL: https://issues.jboss.org/browse/JBDS-1973 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Reporter: Max Rydahl Andersen Fix For: 5.0.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10508) query editor looks bad on mac

by Max Rydahl Andersen (Created) (JIRA)

query editor looks bad on mac ----------------------------- Key: JBIDE-10508 URL: https://issues.jboss.org/browse/JBIDE-10508 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Reporter: Max Rydahl Andersen Assignee: Dmitry Geraskov Priority: Critical Fix For: 3.3.0.Beta1 see attached. This have always been a problem btw. it just was not *this* bad previously. Something about the combobox messing up the layout. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
6
0 / 0

[JBoss JIRA] (JBIDE-10485) Hook up WS Tester to the Common Navigator similar to Web Service Explorer

by Brian Fitzpatrick (Created) (JIRA)

Hook up WS Tester to the Common Navigator similar to Web Service Explorer ------------------------------------------------------------------------- Key: JBIDE-10485 URL: https://issues.jboss.org/browse/JBIDE-10485 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.3.0.M5 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta1 Two different presentations today proved that there need to be more integration points to simplify access to the JBoss WS Tester. Currently in Eclipse with WTP installed, if you right-click on a WSDL file, you see "web services->test with web services explorer" We need to do the same thing for the JBT WS tester. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
5
0 / 0

[JBoss JIRA] (JBIDE-11113) Adding CDI support takes too much time

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11113: ----------------------------------------- Summary: Adding CDI support takes too much time Key: JBIDE-11113 URL: https://issues.jboss.org/browse/JBIDE-11113 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.Beta1 Reporter: Jaroslav Jankovič Assignee: Alexey Kazakov Priority: Critical Fix For: 3.3.0.Beta1 Adding CDI support to some project (for example Dynamic Web Project) takes too much time in my opinion. After this "first" adding both CDI related operations (add/remove) are quite instant. I would like to know if the "first" CDI support adding could be instant as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-10913) Command execution interrupted: Execution context is null

by Dmitry Geraskov (JIRA)

Dmitry Geraskov created JBIDE-10913: --------------------------------------- Summary: Command execution interrupted: Execution context is null Key: JBIDE-10913 URL: https://issues.jboss.org/browse/JBIDE-10913 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M4 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 org.hibernate.console.HibernateConsoleRuntimeException: Command execution interrupted: Execution context is null, 'Hibernate3.5' console configuration is closed. at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:75) at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:41) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) The reason is: One process is building Configuration (through ConsoleConfiguration#execute(Command)) Another process clears execution context. Need to synchronize the methods. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2012