plexiti / camunda-grails-plugin Goto Github PK

I think it is worth to have simple task list application based on the plugin.
It is hard to start using the camunda without it (how to render bpm forms and start process workflow)

I hope you have something around.

Following the tutorial, I am getting the following error when trying to access the embedded form:

XMLHttpRequest cannot load app:camunda/test/sampleForm. Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource. camunda-bpm-sdk-angular.js:457 Uncaught TypeError: Cannot read property 'body' of undefined angular.js:9778 Error: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'app:camunda/test/sampleForm'. at Error (native) at f.28.f.end (http://localhost:8080/camunda/app/tasklist/scripts/deps.js:10:567) at 5.s.load (http://localhost:8080/camunda/app/tasklist/scripts/deps.js:9:1191) at r.t.factory.n.forEach.r.(anonymous function) [as load] (http://localhost:8080/camunda/app/tasklist/scripts/camunda-tasklist-ui.js:1:16976) at 19.CamundaForm.initialize (http://localhost:8080/camunda/app/tasklist/scripts/deps.js:9:13779) at CamundaForm (http://localhost:8080/camunda/app/tasklist/scripts/deps.js:9:12869) at new 17.r.extend.n (http://localhost:8080/camunda/app/tasklist/scripts/deps.js:9:10921) at l (http://localhost:8080/camunda/app/tasklist/scripts/camunda-tasklist-ui.js:5:12580) at Object.fn (http://localhost:8080/camunda/app/tasklist/scripts/camunda-tasklist-ui.js:5:12700) at l.$get.l.$digest (http://localhost:8080/camunda/app/tasklist/scripts/deps.js:5:30649)

Related to tomcat work directory beneath target folder.

create simple dmn decision definition
create simple spock test case

tell user, when camunda version used is < 7.4.0-alpha[?]*

• create simple cmmn case definition
• create simple spock test case

tell user, when camunda version used is < 7.2.0-alpha*

Hello,

With Intellij IDEA:
grails run-war
camunda libraries in war exist
grails war
camunda libraries in war not exist

How to fix it?

I have GGTS (juno) (64bit) 3.5.1 installed and created a grails project using grails 2.3.7

project created fine. edite buildConfig to add camunda plugin. Rebuild. plugin downloads and installs

ran create-process myproc successfuly, and process folder is created in grails-app, along with the bpmn file.

i then got my eclipse build to download the Camunda graphical editor plugin from the camunda site. This seemed to download ok - and the process file in the grails project now has an icon.

when i double click the process file i get an error

An error has occurred. See error log for more details.
org.eclipse.graphiti.ui.services.IImageService.getImageDescriptorForId(Ljava/lang/String;)Lorg/eclipse/jface/resource/ImageDescriptor;

from the log i found this

!ENTRY org.eclipse.ui.workbench 4 2 2014-05-15 23:08:06.851
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
!STACK 0
java.lang.NoSuchMethodError: org.eclipse.graphiti.ui.services.IImageService.getImageDescriptorForId(Ljava/lang/String;)Lorg/eclipse/jface/resource/ImageDescriptor;
at org.camunda.bpm.modeler.ui.Images.getDescriptorById(Images.java:311)
at org.camunda.bpm.modeler.ui.Images.getDescriptorById(Images.java:299)
at org.camunda.bpm.modeler.ui.views.outline.Bpmn2EditorOutlinePage.createOutlineViewer(Bpmn2EditorOutlinePage.java:271)
at org.camunda.bpm.modeler.ui.views.outline.Bpmn2EditorOutlinePage.createControl(Bpmn2EditorOutlinePage.java:171)
at org.eclipse.ui.views.contentoutline.ContentOutline.doCreatePage(ContentOutline.java:137)
at org.eclipse.ui.part.PageBookView.createPage(PageBookView.java:412)
at org.eclipse.ui.part.PageBookView.partActivated(PageBookView.java:753)
at org.eclipse.ui.part.PageBookView$4.partActivated(PageBookView.java:1055)
at org.eclipse.ui.internal.WorkbenchPage$15.run(WorkbenchPage.java:4794)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4792)
at org.eclipse.ui.internal.WorkbenchPage.access$16(WorkbenchPage.java:4772)
at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:194)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$2.run(PartServiceImpl.java:192)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:190)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:609)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:553)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:542)
at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:875)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3073)
at org.eclipse.ui.internal.WorkbenchPage.access$21(WorkbenchPage.java:3034)
at org.eclipse.ui.internal.WorkbenchPage$8.run(WorkbenchPage.java:3016)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3012)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2976)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2967)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:534)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:493)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:360)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:167)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:268)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:233)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251)
at org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:50)
at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:221)
at org.eclipse.ui.navigator.CommonNavigatorManager$3.open(CommonNavigatorManager.java:185)
at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:47)
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:866)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:864)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1152)
at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:462)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1256)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:275)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:269)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:309)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
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:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
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:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)

and i cant open the file and view it

Whats wrong and how do i fix it ?

Thank you for your nice work, two quick questions:

1. I couldn't find out how to configure camunda cockpit, etc. to run in my grails app
2. How can we hot reload ProcessEngine/RuntimeService when .bpmn changes in processes directory.

The note should specifically state the camunda BPM version used by default.

Hi,
I generated a standard app.war file with settings in DataSource.groovy:
production {
dataSource {
pooled = true
dbCreate = "update"
url = "jdbc:mysql://server/db"
driverClassName = "com.mysql.jdbc.Driver"
username = "user"
password = "password"
}
dataSource_camunda {
pooled = true
dbCreate = "update"
url = "jdbc:mysql://server/db_camunda"
driverClassName = "com.mysql.jdbc.Driver"
username = "user"
password = "password"
}
}

Config.groovy:
environments {
production {
grails.logging.jul.usebridge = false
.
.

    camunda {
        engine {
            configuration {
                dataSource = "dataSource_camunda"
                jobExecutorActivate = true
            }
        }
    }
}

The problem is, that the first start of application doesn't create a schema in camunda db. If I try the same config in development environment, schema is on the same server created/updated successfully. The problem is just in production environment.

Any ideas? Have you tried example and tested in production environment?

Thanks a lot.

Jiri Sojka

Hi, we have a problem with generate new changelog after install camunda plugin. The error is:
DbmGenerateChangelog: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'camundaProcessEngineBean': FactoryBean threw exception on object creation; nested exception is org.camunda.bpm.engine.ProcessEngineException: Cannot register service org.camunda.bpm.platform.process-engine:type=default with MBeans Container, service with same name already registered.

We don't know if it is camunda or migration plugin problem... Any idea?

Thanks a lot

• Support legacy *.bpmn20.xml as well as scripts, images and other resources
• Prepare for cmmn support

it seems something goes wrong when using grails commands, deleting repository caches, grails blocks at
Downloading: org/grails/plugins/camunda/0.3.0-SNAPSHOT/maven-metadata.xml

Camunda can't find a process definition in this case:

grails.project.fork = [
    // configure settings for compilation JVM, note that if you alter the Groovy version forked compilation is required
    //  compile: [maxMemory: 256, minMemory: 64, debug: false, maxPerm: 256, daemon:true],

    // configure settings for the test-app JVM, uses the daemon by default
    test: false
}

Hi Martin,

Any tentative date of the release? Especially the fix is required to resolve the compilation issue in grails 2.4 and above. Thanks in advance.

FilterService is new starting from camunda 7.2

Need to add it to CamundaPluginSupport.groovy

  camundaRuntimeServiceBean(camundaProcessEngineBean: 'getRuntimeService')
            camundaRepositoryServiceBean(camundaProcessEngineBean: 'getRepositoryService')
            camundaTaskServiceBean(camundaProcessEngineBean: 'getTaskService')
            camundaManagementServiceBean(camundaProcessEngineBean: 'getManagementService')
            camundaIdentityServiceBean(camundaProcessEngineBean: 'getIdentityService')
            camundaAuthorizationServiceBean(camundaProcessEngineBean: 'getAuthorizationService')
            camundaHistoryServiceBean(camundaProcessEngineBean: 'getHistoryService')
            camundaFormServiceBean(camundaProcessEngineBean: 'getFormService')
            camundaFilterServiceBean(camundaProcessEngineBean: 'getFilterService') /// <---- TO ADD

Hi,

Thank you for the great plugin.
Do you plan to create grails 3 version in future

Regards

Creating a clean project (Grails 2.5.0) and only adding the camunda plugin, it cannot run the app, bcause the new compiler (groovy 2.4.3) didn't allow to have static and non static methods with the same signature, concretely in the class : src/groovy/grails/plugin/camunda/Configuration.groovy

Stacktrace (2 errors) :

| Compiling 125 source files.
| Error Compilation error: startup failed:
/test-camunda/target/work/plugins/camunda-0.4.0/src/groovy/grails/plugin/camunda/Configuration.groovy: 193: Method 'getProperty' is already defined in class 'grails.plugin.camunda.Configuration'. You cannot have both a static and a non static method with the same signature
@ line 193, column 3.
static Object getProperty(String property) {
^
/test-camunda/target/work/plugins/camunda-0.4.0/src/groovy/grails/plugin/camunda/Configuration.groovy: 200: Method 'setProperty' is already defined in class 'grails.plugin.camunda.Configuration'. You cannot have both a static and a non static method with the same signature
@ line 200, column 3.
static void setProperty(String property, Object value) {
^

Look into http://stackoverflow.com/questions/30958109/how-to-trigger-table-changes-in-camunda-using-grails

The opportunity to integrate Camunda to Grails through a plugin is amazing. However the integration of it's provided services with Grails application is not fully clear. Usually other plugins such as Spring Security Core, are used in projects. I didn't found in the docs information about how to integrate IdentityService with the authentication provider available in the Grails application (either the Spring Security or other).

This integration exists natively in the camunda plugin? If not, it would be relevant to point the way to how to implement it

When creating processes with the same name in different packages, we end up with name clashes concerning the internal process id. This is not a real problem, since the camunda deployment will complain about that while deploying. However, we might want to warn the user the moment such a duplicate process is created via the 'create-process' command.

My start timer events are not being executed... I was unable to check if Job Executor is started by grails plugin, or where could be my problem!?
My createJobQuery().list() returns

[TimerEntity[repeatR/2014-09-08T01:00:00/PT24H, id=16008, revision=1, duedate=Mon Sep 15 01:00:00 IRDT 2014, lockOwner=null, lockExpirationTime=null, executionId=null, processInstanceId=null, isExclusive=true, retries=3, jobHandlerType=timer-start-event, jobHandlerConfiguration=nightlyBill, exceptionByteArray=null, exceptionByteArrayId=null, exceptionMessage=null, deploymentId=null], TimerEntity[repeat0 53 12 * * ?, id=16022, revision=1, duedate=Sun Sep 14 12:53:00 IRDT 2014, lockOwner=null, lockExpirationTime=null, executionId=null, processInstanceId=null, isExclusive=true, retries=3, jobHandlerType=timer-start-event, jobHandlerConfiguration=testProcess, exceptionByteArray=null, exceptionByteArrayId=null, exceptionMessage=null, deploymentId=null]]

• service task with delegateExpression, JavaDelegate as in #54 and unit or integration test class for it
• user task with assignee/group

I would like to disable the job execution in our application server (tomcat).
So what we did is to set jobExecutorActivate to false in Config.groovy:

camunda {
engine {
deployment.scenario = "embedded"
configuration {
databaseType = "postgres"
dataSource = new RuntimeBeanReference("dataSource_camunda")
databaseSchemaUpdate = false
jobExecutorActivate = false
deploymentResources = ['....']
history = "full"
}
}

However, when we start the tomcat, I can still see the start up messages like this:

Apr 24, 2015 4:02:18 PM org.camunda.bpm.engine.impl.jobexecutor.JobExecutor start
INFO: Starting up the JobExecutor[org.camunda.bpm.engine.impl.jobexecutor.RuntimeContainerJobExecutor].
Apr 24, 2015 4:02:18 PM org.camunda.bpm.engine.impl.jobexecutor.SequentialJobAcquisitionRunnable run
INFO: JobExecutor[org.camunda.bpm.engine.impl.jobexecutor.RuntimeContainerJobExecutor] starting to acquire jobs
Apr 24, 2015 4:06:33 PM org.camunda.bpm.engine.impl.ProcessEngineImpl
INFO: ProcessEngine default created

The result is it will still execute the jobs.
May I know if there is anything missed in my configuration or there is other proper way to handle this so that the job executor can be stopped.

Thanks!
Jeff

Besides other good stuff this avoids clashes with grails service artifacts (as seen e.g. in Grails 2.3.0)