November 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-3052) Generate Entities tells me Hibernate Dialect not set when it is

by Max Rydahl Andersen (JIRA)

Generate Entities tells me Hibernate Dialect not set when it is --------------------------------------------------------------- Key: JBIDE-3052 URL: https://jira.jboss.org/jira/browse/JBIDE-3052 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Reporter: Max Rydahl Andersen Assignee: Dima Geraskov Fix For: 3.0.0.beta1 I've set hibernate dialect in the persistence.xml but when I use Generate Entities the wizard tells me "Hibernate dialect is not set" (without any further explanation. Why is it not picking up the persistence.xml when generating entities ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1921) Hibernate Tools User Guide

by Denis Golovin (JIRA)

Hibernate Tools User Guide -------------------------- Key: JBIDE-1921 URL: http://jira.jboss.com/jira/browse/JBIDE-1921 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 2.0.1, 2.1 Reporter: Denis Golovin Fix For: 2.1 There is hibernatetools-ref-guide in https://svn.jboss.org/repos/jbosstools/trunk/hibernatetools/docs/reference that should be available as org.hibernate.user.doc in JBossTools. It should be used for context help in hiberbnate related GUI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-2286) view id selection shows "weird" dialog

by Max Rydahl Andersen (JIRA)

view id selection shows "weird" dialog -------------------------------------- Key: JBIDE-2286 URL: http://jira.jboss.com/jira/browse/JBIDE-2286 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Reporter: Max Rydahl Andersen Fix For: 3.0.x Not sure if this is a bug or feature request, but here it goes. The dialog for selecting view-id contains "weird things" 1) the root node is the same as project name 2) the project is shown below the root node with all folders/files below it 3) there are other folders shown below it that seem to be non-related. ...what I would have expected was a list of existing view-id's used in the pages.xml, list of whatever page resources that is found inside any view/webcontent folder according to WTP project and finally a "Other" node which would allow me to browse the full project. Maybe this should be a dialog with various options instead of a pure tree to make it simpler for the user ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-447) jsf_tools_ref_guide concluding part is required

by Svetlana mukhina (JIRA)

jsf_tools_ref_guide concluding part is required ----------------------------------------------- Key: JBDS-447 URL: https://jira.jboss.org/jira/browse/JBDS-447 Project: Developer Studio Issue Type: Sub-task Components: Doc - JSFTools Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.0.beta1 jsf_tools_ref_guide concluding part is required -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-3115) Ensure that correct provider name appears for plug-ins

by John Graham (JIRA)

Ensure that correct provider name appears for plug-ins ------------------------------------------------------ Key: JBIDE-3115 URL: https://jira.jboss.org/jira/browse/JBIDE-3115 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk Reporter: John Graham Assignee: Denny Xu Fix For: 3.0.0.cr1 Make sure that the plug-in provider is "JBoss, a division of Red Hat" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-3114) ESB project wizard allows for invalid content and source folder names

by John Graham (JIRA)

ESB project wizard allows for invalid content and source folder names --------------------------------------------------------------------- Key: JBIDE-3114 URL: https://jira.jboss.org/jira/browse/JBIDE-3114 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk Reporter: John Graham Assignee: Denny Xu Priority: Critical Fix For: 3.0.0.cr1 In the ESB project wizard, the "Content Directory" and "Java Source Directory" can be given invalid values (for example, just "." on Linux). Selecting finish with an invalid value in either of these fields makes the project creation fail. The ESB wizard should filter these values to allow only platform valid choices (the first page of the wizard does this for project name). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3142) Add WST XML editor into Smooks multipageeditor

by Xue Peng (JIRA)

Add WST XML editor into Smooks multipageeditor ---------------------------------------------- Key: JBIDE-3142 URL: https://jira.jboss.org/jira/browse/JBIDE-3142 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: smooks Affects Versions: 3.0.0.cr1 Reporter: Xue Peng Assignee: Xue Peng -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-3141) CLONE -Cannot create process definition in root project folder

by Koen Aers (JIRA)

CLONE -Cannot create process definition in root project folder -------------------------------------------------------------- Key: JBIDE-3141 URL: https://jira.jboss.org/jira/browse/JBIDE-3141 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Environment: jBPM designer: 3.1.5Beta1-N200810230806 Reporter: Koen Aers Assignee: Koen Aers Priority: Critical Fix For: 3.0.0.cr1 Tried to create a process definition in the top level of a project (that is, I selected a project as the destination folder, not a subfolder within the project). The following exception appears repeatedly while typing the process name in the wizard, and the Finish button is not enabled. If I select a subfolder, the wizard completes without error. ------------------------------- java.lang.IllegalArgumentException: Path must include project and resource name: /test_jbpm at org.eclipse.core.runtime.Assert.isLegal(Assert.java:64) at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1628) at org.eclipse.core.internal.resources.Container.getFolder(Container.java:137) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.checkContainerPathValid(Unknown Source) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.verifyContentsValid(Unknown Source) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.access$0(Unknown Source) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage$3.modifyText(Unknown Source) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:253) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) 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.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) 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:386) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-2981) Cannot create process definition in root project folder

by John Graham (JIRA)

Cannot create process definition in root project folder ------------------------------------------------------- Key: JBIDE-2981 URL: https://jira.jboss.org/jira/browse/JBIDE-2981 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Environment: jBPM designer: 3.1.5Beta1-N200810230806 Reporter: John Graham Tried to create a process definition in the top level of a project (that is, I selected a project as the destination folder, not a subfolder within the project). The following exception appears repeatedly while typing the process name in the wizard, and the Finish button is not enabled. If I select a subfolder, the wizard completes without error. ------------------------------- java.lang.IllegalArgumentException: Path must include project and resource name: /test_jbpm at org.eclipse.core.runtime.Assert.isLegal(Assert.java:64) at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1628) at org.eclipse.core.internal.resources.Container.getFolder(Container.java:137) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.checkContainerPathValid(Unknown Source) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.verifyContentsValid(Unknown Source) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.access$0(Unknown Source) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage$3.modifyText(Unknown Source) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:253) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) 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.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) 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:386) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2669) Seam packager should include mvel*.jar, not just mvel14.jar from ${seam.home}/lib

by Pete Muir (JIRA)

Seam packager should include mvel*.jar, not just mvel14.jar from ${seam.home}/lib --------------------------------------------------------------------------------- Key: JBIDE-2669 URL: https://jira.jboss.org/jira/browse/JBIDE-2669 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Pete Muir Assignee: Max Rydahl Andersen Priority: Critical Older Seam packaged mvel as mvel14.jar - subsequently the jar name was changed to mvel.jar (which is a better name, as mvel14.jar includes version info in the jar name which is bad) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

4
9
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 November 2008