[JBoss JIRA] Created: (JBIDE-6623) [Designer] Using New Metadata Modeling Model Project wizard throws exception if not run in Designer perspective
by Brian Fitzpatrick (JIRA)
[Designer] Using New Metadata Modeling Model Project wizard throws exception if not run in Designer perspective
---------------------------------------------------------------------------------------------------------------
Key: JBIDE-6623
URL: https://jira.jboss.org/browse/JBIDE-6623
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: teiid
Affects Versions: 3.2.0.M1
Reporter: Brian Fitzpatrick
Assignee: Barry LaFond
Fix For: 3.2.x
When I created a new Model Project in a perspective other than the Designer perspective, I get an error in the new project wizard in a clean workspace. I was able to cancel out of the project wizard, manually select Open Project on the popup, and open the project to continue, but it would be good if we didn't automatically throw an issue if the wizard is available in other perspectives. Or perhaps pop up a dialog suggesting the user should pop into the Designer perspective for additional functionality (kind of like when Eclipse flips into the Debug perspective when it goes into Debug mode and offers the choice).
!ENTRY org.teiid.designer.ui 4 0 2010-07-15 09:56:16.584
!MESSAGE Resource '/MyModelProject' is not open.
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Resource '/MyModelProject' is not open.
at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:137)
at org.eclipse.core.internal.resources.Project.getDescription(Project.java:379)
at com.metamatrix.modeler.ui.wizards.NewModelProjectWizard.performFinish(NewModelProjectWizard.java:94)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:811)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:430)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3552)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171)
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:254)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
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:241)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
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:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3552)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
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:369)
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:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-6093) Eclipse Guvnor Tooling causes validation errors on certain file types
by Jeff DeLong (JIRA)
Eclipse Guvnor Tooling causes validation errors on certain file types
----------------------------------------------------------------------
Key: JBIDE-6093
URL: https://jira.jboss.org/jira/browse/JBIDE-6093
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: drools
Affects Versions: 3.1.0.CR2
Environment: JBoss Tools Nightly Build - Jboss Drools Guvnor 5.1.0.v20100226213N-H20-31764
Reporter: Jeff DeLong
Eclipse Guvnor Tooling creates a new file with the name .filename.ext when a file is added to Guvnor. For xml files (.xml, .xsd, .html, .bpel, etc,) and java files, this causes the validators to report errors. E.g., "Content is not allowed in the prolog" and "Syntax errors on tokens, delete these tokens. This is because these files have the xml or java extension, hence the validator attempts to validate them. I have looking at the Preferences -> Validation, but cannot see a clever way to create a rule to exclude all files with a . at the front of the filename.
Also, Eclipse Guvnor Tooling is not able to add files to the new for Guvnor 5.1 GlobalArea.
--
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
15 years, 4 months