Skip to main content


Eclipse Community Forums

      Home
Home » Eclipse Projects » BPMN 2.0 Modeler » how to enable customTasks in collaboration palette?
how to enable customTasks in collaboration palette? [message #1087375] Thu, 15 August 2013 10:51 Go to next message
Eclipse UserFriend
Hello,

I've several custom Tasks that appear without any problem in the process type diagrams palette. However, i've tried using the same modelEnablement switching the enable properties from:
object: default
feature: Process

to:
object: default
feature: Collaboration
but it didn't work.

I've been searching for a way to this but i didn't find one.

What do i need to add a customTask to the palette in a collaboration diagram?

Thanks,
Regards
Marco Roque
Re: how to enable customTasks in collaboration palette? [message #1087436 is a reply to message #1087375] Thu, 15 August 2013 12:31 Go to previous messageGo to next message
Eclipse UserFriend
Huh...funny thing. I just went through the code in BpmnToolBehaviourFeature and it looks like Custom Tasks are only added to the toolpalette for Process Diagrams - sorry about that!

Please file a bugzilla report for this, so I can get a fix out to you ASAP.

Thanks!
Bob

EDIT: You'll still have to create a <modelEnablement> section in your plugin.xml for Collaboration diagrams, similar to what you've (probably) already got for Process diagrams. Something like this:


      <modelEnablement
            runtimeId="my.runtime.id"
            type="Collaboration" profile="Default Collaboration">
			<disable object="all"/>
			<!-- copy the enablements from "Collaboration" diagram type as defined in the "None" Target Runtime -->
			<enable object="default" feature="Collaboration"/>

			<!-- select the model extension features to be displayed in the Property Tabs -->
			<enable object="Task" feature="taskConfig"/>
			<enable object="TaskConfig"/>
			<enable object="Parameter"/>
			<enable object="BoundaryEvent" feature="isEnabled"/>
			<enable object="MyEventDefinition" feature="value"/>
			
      </modelEnablement>

[Updated on: Thu, 15 August 2013 12:37] by Moderator

Re: how to enable customTasks in collaboration palette? [message #1087560 is a reply to message #1087436] Thu, 15 August 2013 16:53 Go to previous messageGo to next message
Eclipse UserFriend
Hi Marco,

This was relatively simple, so I just created a BZ report and committed a fix for this bug.
Re: how to enable customTasks in collaboration palette? [message #1087598 is a reply to message #1087375] Thu, 15 August 2013 18:09 Go to previous messageGo to next message
Eclipse UserFriend
Hi Bob,

It was really fast! thanks a lot.

Do you know when will this fix be available in a stable release?

Regards,
Marco Roque
Re: how to enable customTasks in collaboration palette? [message #1087618 is a reply to message #1087598] Thu, 15 August 2013 18:40 Go to previous messageGo to next message
Eclipse UserFriend
You could try the nightly builds available here:

http://download.eclipse.org/bpmn2-modeler/updates/nightly/kepler/

or here:

http://download.eclipse.org/bpmn2-modeler/updates/nightly/juno/

Regards,
Bob
Re: how to enable customTasks in collaboration palette? [message #1089369 is a reply to message #1087618] Sun, 18 August 2013 12:31 Go to previous messageGo to next message
Eclipse UserFriend
Hi Bob,

I installed the nightly build but now i can't open the diagrams.
I'm getting the following exception:

org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
	at org.eclipse.swt.SWT.error(SWT.java:4361)
	at org.eclipse.swt.SWT.error(SWT.java:4276)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388)
	at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
	at org.eclipse.bpmn2.modeler.ui.wizards.BPMN2DiagramWizard.performFinish(BPMN2DiagramWizard.java:83)
	at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
	at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
	at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
	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:259)
	at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
	at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
	at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:76)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:131)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:171)
	at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:515)
	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:1053)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	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:353)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
Caused by: java.lang.NullPointerException
	at org.eclipse.bpmn2.modeler.ui.editor.BPMN2EditorMatchingStrategy.matches(BPMN2EditorMatchingStrategy.java:24)
	at org.eclipse.ui.internal.WorkbenchPage.checkEditor(WorkbenchPage.java:2225)
	at org.eclipse.ui.internal.WorkbenchPage.findEditors(WorkbenchPage.java:2194)
	at org.eclipse.ui.internal.WorkbenchPage.findEditor(WorkbenchPage.java:2176)
	at org.eclipse.bpmn2.modeler.ui.wizards.BPMN2DiagramCreator$1.run(BPMN2DiagramCreator.java:74)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)


Regards,
Marco Roque
Re: how to enable customTasks in collaboration palette? [message #1090799 is a reply to message #1089369] Tue, 20 August 2013 12:59 Go to previous message
Eclipse UserFriend
Yikes! Sorry about that. Am I correct in assuming you are using the Juno version of the editor? I just tried a "smoke test" with that platform and found the problem was caused by a bad code merge. I'm usually pretty good at testing these things before publishing a nightly build, but this one just slipped past me Wink

I'll have a new build by end of today that you can test with.

Thanks for testing!
Bob
Previous Topic:Reloading the bpmn2 diagram
Next Topic:Delete unused MessageFlows ?
Goto Forum:
  


Current Time: Sun Jul 13 05:54:48 EDT 2025

Powered by FUDForum. Page generated in 0.06010 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly