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

Koen Aers (JIRA) jira-events at lists.jboss.org
Fri Nov 7 11:29:36 EST 2008


    [ https://jira.jboss.org/jira/browse/JBIDE-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12437484#action_12437484 ] 

Koen Aers commented on JBIDE-2981:
----------------------------------

It is due to the fact that the processdefinition and the graphical info have to be next to one another. They are found either by looking for a special name (process-definition.xml and gpd.xml) or else by looking for a particular naming scheme (.myprocess.gpd and myprocess.jpdl). Files can be created only according to the former pattern, so if we really want to solve this the latter pattern has to be added... 

Anyway, in jpdl 4 the graphical info will be in the process file an this problem will not exist ;-)

> 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
>            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

        



More information about the jbosstools-issues mailing list