[JBoss JIRA] (JBIDE-10515) Mappings in H4 configuration are not built by default
by Dmitry Geraskov (Created) (JIRA)
Mappings in H4 configuration are not built by default
-----------------------------------------------------
Key: JBIDE-10515
URL: https://issues.jboss.org/browse/JBIDE-10515
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.M5
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Priority: Critical
Fix For: 3.3.0.Beta1
When JPA configuration is used we call configure(Properties properties, Map workingVars) method and as a side effect mappings were built earlier.
But in Hibernate 4 this doesn't happen. So we need to call buildMappings evidently.
Test Case:
1. Create JPA Project with hibernate 4 with some mapping
2. Set Console Configuration Hierbante version to 4.0
3. Expand Configuration node in the tree
4. Right click on the mapped class-open in HQL Editor
5. Change query to "from <myPack>.<MyClass> s where s." and press ctrl+space for code completion
6. FAILURE: code completion don't show properties as completion proposals
7. Expands SessionFactory node in the tree
8. Step6 how shows correct completion proposals
--
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, 1 month
[JBoss JIRA] (JBIDE-10506) H4 query code completion throws exception
by Max Rydahl Andersen (Created) (JIRA)
H4 query code completion throws exception
-----------------------------------------
Key: JBIDE-10506
URL: https://issues.jboss.org/browse/JBIDE-10506
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Reporter: Max Rydahl Andersen
Assignee: Dmitry Geraskov
Priority: Critical
Fix For: 3.3.0.Beta1
java.lang.LinkageError: loader constraint violation: when resolving method "org.hibernate.eclipse.console.workbench.HibernateWorkbenchHelper.getImage(Lorg/hibernate/mapping/Property;)Lorg/eclipse/swt/graphics/Image;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/jboss/tools/hibernate4_0/console/EclipseHQLCompletionRequestor, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/hibernate/eclipse/console/workbench/HibernateWorkbenchHelper, have different Class objects for the type org/hibernate/mapping/Property used in the signature
at org.jboss.tools.hibernate4_0.console.EclipseHQLCompletionRequestor.getImage(EclipseHQLCompletionRequestor.java:120)
at org.jboss.tools.hibernate4_0.console.EclipseHQLCompletionRequestor.accept(EclipseHQLCompletionRequestor.java:59)
at org.hibernate.tool.ide.completion.ConfigurationCompletion.addPropertiesToList(ConfigurationCompletion.java:187)
at org.hibernate.tool.ide.completion.ConfigurationCompletion.getMatchingProperties(ConfigurationCompletion.java:80)
at org.hibernate.tool.ide.completion.HQLCodeAssist.codeComplete(HQLCodeAssist.java:66)
at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.hqlCodeComplete(ConsoleExtension4_0.java:93)
at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeProposals(HQLCompletionProcessor.java:122)
at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeCompletionProposals(HQLCompletionProcessor.java:82)
at org.hibernate.eclipse.hqleditor.HQLCompletionProcessor.computeCompletionProposals(HQLCompletionProcessor.java:65)
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.hibernate.eclipse.hqleditor.HQLSourceViewer.doOperation(HQLSourceViewer.java:58)
at org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOperationAction.java:128)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.texteditor.TextOperationAction.run(TextOperationAction.java:126)
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:1069)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4127)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1494)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1490)
at org.eclipse.swt.widgets.Canvas.sendKeyEvent(Canvas.java:463)
at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1051)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5563)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68)
at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:587)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5473)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220)
at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2092)
at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2252)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5535)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989)
at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3610)
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)
--
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, 1 month
[JBoss JIRA] (JBIDE-10463) Regression for JBossAS 7.1: Runtime detection doesn't consider additions to "Default Classpath Entries"
by Juergen Zimmermann (Created) (JIRA)
Regression for JBossAS 7.1: Runtime detection doesn't consider additions to "Default Classpath Entries"
-------------------------------------------------------------------------------------------------------
Key: JBIDE-10463
URL: https://issues.jboss.org/browse/JBIDE-10463
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M4, 3.3.0.M5
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
I tried build 2011-12-12_16-41-07-H58. However, when I invoke Preferences > JBoss Tools > JBoss Tools Runtime Detection the resulting server config doesn't contain JARs that are configured in Preferences > Server > Runtime Environments > Default Classpath Entries. For instance I added:
Name: JBoss EJB3 Extensions
Root Directory: modules/org/jboss/ejb3/main
Includes: **/*.jar
The resulting classpath should contain jboss-ejb3-ext-api-2.0.0-beta-1.jar being located in $JBOSS_HOME/modules/org/jboss/ejb3/main.
I'll attach a screenshot to illustrate the issue.
--
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, 1 month
[JBoss JIRA] Created: (JBIDE-9630) Sometimes getting 'Already publishing' error
by Libor Zoubek (JIRA)
Sometimes getting 'Already publishing' error
--------------------------------------------
Key: JBIDE-9630
URL: https://issues.jboss.org/browse/JBIDE-9630
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Reporter: Libor Zoubek
Assignee: Rob Stryker
Fix For: 3.3.0.M4
I' facing 'Already publishing' error dialog when working on web apps using AS7. I still did not found exact steps to reproduce. Right now I've once reproduced doing following:
Have stated AS7.0.1
Have deployed web app (which currenly caused deployment error on AS)
Imported jboss-as demos (5 projects) using 'Import Existing maven projects'
right after that, I got 'Already publishing'
Another thing I've noticed is that the deployed project is in state : 'Started, Republish' is this state correct? What does it mean?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10347) Invalid menu location for the 'Explore' item
by Xavier Coulon (Created) (JIRA)
Invalid menu location for the 'Explore' item
--------------------------------------------
Key: JBIDE-10347
URL: https://issues.jboss.org/browse/JBIDE-10347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M4
Reporter: Xavier Coulon
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.3.0.Beta1
The following stack trace appears at startup (I already have servers configured in the servers view):
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator".
!STACK 0
java.lang.IllegalArgumentException: can't find ID org.eclipse.wst.server.ui.internal.cnf.serverEtcSectionEnd
at org.eclipse.jface.action.ContributionManager.insertBefore(ContributionManager.java:359)
at org.eclipse.jface.action.ContributionManager.insertBefore(ContributionManager.java:350)
at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.fillContextMenu(ExploreActionProvider.java:123)
at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:221)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:216)
at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:173)
at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:260)
at org.eclipse.ui.navigator.CommonNavigatorManager$4.menuAboutToShow(CommonNavigatorManager.java:275)
at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:342)
at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:473)
at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:469)
at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:495)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:247)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1461)
at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:805)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5525)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:73)
at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:277)
at org.eclipse.swt.widgets.Display.runPopups(Display.java:4051)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3606)
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, 1 month
[JBoss JIRA] (JBIDE-10194) Exception after changing view-id attribute of page tag in pages.xml file
by Daniel Azarov (Created) (JIRA)
Exception after changing view-id attribute of page tag in pages.xml file
------------------------------------------------------------------------
Key: JBIDE-10194
URL: https://issues.jboss.org/browse/JBIDE-10194
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 3.3.0.M4
Reporter: Daniel Azarov
Assignee: Alexey Kazakov
Test Case:
EXECUTE:
1. Import jboss-seam-jpa project.
2. Open pages.xml file
3. Change view-id="/confirm.xhtml" to view-id="/coirm.xhtml"
4. Save file
5. Change view-id="/coirm.xhtml" to view-id="/confirm.xhtml"
6. Save file
FAIL:
Exception:
org.eclipse.core.runtime.AssertionFailedException: null argument:The dialog should be created in UI thread
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
at org.eclipse.jface.dialogs.IconAndMessageDialog.getSWTImage(IconAndMessageDialog.java:282)
at org.eclipse.jface.dialogs.IconAndMessageDialog.getErrorImage(IconAndMessageDialog.java:233)
at org.eclipse.jface.dialogs.MessageDialog.<init>(MessageDialog.java:179)
at org.jboss.tools.common.model.ui.wizards.one.ServiceDialogImpl.showDialog(ServiceDialogImpl.java:62)
at org.jboss.tools.common.model.impl.RegularObjectImpl.elementExists(RegularObjectImpl.java:151)
at org.jboss.tools.common.model.impl.RegularObjectImpl.set(RegularObjectImpl.java:134)
at org.jboss.tools.seam.pages.xml.model.impl.ReferenceObjectImpl.set(ReferenceObjectImpl.java:98)
at org.jboss.tools.common.meta.impl.adapters.XAdapterModelElement.setProperty(XAdapterModelElement.java:26)
at org.jboss.tools.common.model.impl.XModelObjectImpl.set_0(XModelObjectImpl.java:162)
at org.jboss.tools.common.model.impl.XModelObjectImpl.setAttributeValue(XModelObjectImpl.java:188)
at org.jboss.tools.seam.pages.xml.model.helpers.SeamPagesDiagramHelper.updateDiagram0(SeamPagesDiagramHelper.java:96)
at org.jboss.tools.seam.pages.xml.model.helpers.SeamPagesDiagramHelper.updateDiagram(SeamPagesDiagramHelper.java:68)
at org.jboss.tools.seam.pages.xml.model.FileSeamPagesImpl.mergeAll(FileSeamPagesImpl.java:47)
at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.edit(AbstractExtendedXMLFileImpl.java:261)
at org.jboss.tools.jst.web.model.AbstractWebDiagramLoader.update(AbstractWebDiagramLoader.java:57)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.reload(FolderImpl.java:686)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:597)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateAuxiliary(FolderImpl.java:557)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:381)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:582)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:405)
at org.jboss.tools.common.model.filesystems.impl.FileSystemFolderLoader.update(FileSystemFolderLoader.java:28)
at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoader.update(FileSystemsLoader.java:68)
at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.doUpdate(FileSystemsImpl.java:343)
at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.access$4(FileSystemsImpl.java:337)
at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl$UpdateRunnable.run(FileSystemsImpl.java:326)
at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:178)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
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, 1 month