Hi everyone! I’m writing this post to introduce the jBPM Console NG project which will provide a new integrated workbench for handling process related activities. We are now in a very initial stage of development and we are looking for contributors. We know that there are a lot of companies out there implementing their own solutions and at this point we encourage you all to give us feedback about the direction that we are picking for the BPM tooling. As usual, this tooling will be integrated with all the Drools and Guvnor Tooling to provide an integrated Knowledge Development Environment.
Introduction
As always, we are developing the jBPM Console NG in a public github repository: https://github.com/droolsjbpm/jbpm-console-ng
You can clone this repository, build the source code and deploy the jBPM Console NG in your own container following the next steps:
1) git clone https://github.com/droolsjbpm/jbpm-console-ng.git
2) cd jbpm-console-ng
3) mvn clean install
4) cd jbpm-console-ng-showcase
5) mvn gwt:run -> This will display the GWT Development Mode console which will give you an URL to access via your Browser (for development purposes you need to use Firefox which provides a Development GWT Plugin that allows us to Debug the application)
Technology
The application is being developed using Uberfire which is based on GWT (Google Web Toolkit), Errai and CDI. This mix of technologies gives us the ultimate environment to build flexible applications using a rock solid component model. I will be posting some examples showing how to get started to create new panels and add customizations to the existing code base shortly, but feel free to clone/fork the repository to take a look at the current status.
Goals
The main goal behind the application is to provide an integrated environment to discover, design, deploy, execute, monitor and improve our business processes. In order to provide all this functionality we have started the development integrating our existing components inside the Uberfire infrastructure.
There is an ongoing effort to integrate the jBPM Process Designer inside this platform, but I’ve started working on the Process Runtime Panels and in the Task Lists with the help of Maciej.
The following screenshots shows the current status of the application:
Home Screen
The home screen shows us important information about the things that the user is enabled to do. The jBPM Lifecycle chart allows the use to select in which phase he/she wants to work. Right now I’m focused on improving the “Work” stage as it’s being shown in the following screenshots.
The home screen also contains a suggestion box that allows you to quickly type different “Commands” to access the different sections of the application. In order to return to the Home Screen, we can use the shortcut CTRL+H.
Tasks List
The Tasks List screen will allows us to interact with the tasks assigned to us or to the groups where we are included. As you can notice in the previous screen, my user (salaboy) was included inside the [Writer] group. This means that all the Tasks associated to the Writer group will appear in my personal task list. Notice that for each row inside the list we will have a set of actions to interact with each task. The following screenshot shows the Start button inside the Actions column, we can also edit/view the Task Details and we can also access to work on that particular task via it associated Task Form.
Quick Tasks Creation
Clicking in the Create New Task button, we will be able to create a new Task for us or for other person inside the organization. The task will be created assigned to us, but we can forward the task later. Notice that we can also create a Quick Task, this means that the task will be automatically started and can be used as a simple TODO task. No matter where we are in the application we can use the shortcut CTRL+T to create a new task.
Task Details
The Task Details popup allows us to see the most important information about the a particular task. If we want to access to a more detailed view about that particular task we can click the Full button which will open more panels related with that task. Notice that This task is not associated with any business processes, but for those variables which are associated with a business process instance, we can access to see the process instance details using the “Process Instance Details” button on the bottom.
Forms
The current version allows us to interact with tasks via Task Forms which are dynamically generated based on the task content and the expected outputs. This task is already in progress, and for that reason you can see the Complete button on the bottom of the form. If the task is in a different state, different buttons will be displayed. As you can see the Save button will allow the user to store intermediate steps of the information that is being filled up inside the form. The Full button can be used to see the form with more contextual data, like for example Task Attachments or Task Comments.
Process Management
The Process Management panels will allows us to see all the available Process Definitions and it will allows us to create new Process Instances. As you can see in the following screenshot, you will be able to inspect the Process Definition Details to see the process diagram and relevant information about each process.
Process Instance Details
Inside the Process Instance Details you will be able to see the current status of the Process Variables, the activities that are being executed and also the Log for that particular instance.
Signaling Events
From the Process Instance List you will be able to signal events. The Events List will be retrieved based on the process definition and the Signal Ref suggestion box list you all the events related with the selected Process Instance.
Roadmap
During the following months we will be working on polishing the current panels and services behind the application to provide an error free environment that allows you to execute your business processes and interact with the Human Task Services. During this initial phase of development we are looking forward to improve the user experience, and for this reason we encourage you to try the latest source code and let us know what you think. This initial version can also be deployed in the cloud, like for example OpenShift. We believe that this will help a lot new users that want to try out an existing installation.
There a lot of things that needs to be done, so take a look at the following section because if you want to get involved with the development of an open source tooling this is a very good opportunity to learn and to join the project.
Contributions
The following list is a set of things that can be done by Java Developers and doesn’t require any advanced knowledge about the technology that we are using. You will see that the technology stack that we are using is extremely simple and agile:
- Task Comments Panels
- Task Attachments Panels
- Shortcuts Mappings Panels
- Notifications Panels
- Avatar and Meta information about users and groups Administration Panels
- Domain Specific Suggestions Phrases Administration Panels
- I18N Translations (We already have Spanish (es_AR) and English, so if you are a native speaker of a different language feel free to drop us a line)
- Extending the GWT DataGrid component to support prioritized lists (Knowledge about GWT is required)
- Create a Custom GWT Calendar Component to display the pending tasks in a Calendar. (Knowledge about GWT required)
- Experiment with m-gwt (http://www.m-gwt.com/) (Knowledge about GWT and motivation to learn m-gwt is required)
- Any idea that you may have and want to propose
Drop us a line with your ideas/requirements, we are very open to guide all the interested in doing contributions to learn what they need in order to get started. I will be posting some videos about how to create a simple panel and about how the internal services are working on the next few days, but feel free to ask questions if you are interested in this development. You already know where to find me 🙂
Thanks Salaboy, This seems to be a great work!
If you support RTL direction, I can translate it to Persian and Arabic.
I think it should be easy, because GWT already supports RTL.
LikeLike
Hi Heidarzadeh,
That sounds great, but you can help me to support RTL, I was not planning to do that in the near future, but I guess that if you know a little of GWT you can help me with that, do you think that it will be possible for you to contribute?
Cheers
LikeLike
I think I could be able to do that.
I have done some GWT projects about two years ago. I will check the code, if you have separated all styles into css files, it will be easy to make it RTL.
Of course I don’t know a lot about Errai, but I know CDI well.
Continue developing these great stuff… 😉
By the way I saw your answer about JBPM and swing integration that I’ve asked in Linkedin, I’m currently checking the source code and will give feedback in Linkedin.
Cheers
LikeLike
Cool, thanks a lot for your feedback, You will not have any problems with Errai, if you know CDI and GWT you will be more than fine. Errai makes our life easier, but for the RTL thing you will not need to know anything specific about Errai. If you check the source code, take a look at the *Perspective classes which are the ones which defines layouts with multiple panels. There are also two styles files: main.css and skin.css.
Let me know if you have questions.
Cheers
LikeLike
The application looks great; but I can’t find a version working (with the instructions given in introduction). May you indicate what to checkout?
Natsumme
LikeLike
I coorect the typo: May you indicate what to checkout?
LikeLike
I correct the typo: May you indicate what hash to checkout?
LikeLike
Where? Can you elaborate?
LikeLike
I’m working on that application so it’s working. What kind of problems do you have?
You need to following these steps to get it working dev mode (if you plan to change it):
1) Clone using git: git clone https://github.com/droolsjbpm/jbpm-console-ng.git
2) cd jbpm-console-ng
3) mvn clean install
4) cd jbpm-console-ng-showcase
5) mvn clean install
6) mvn gwt:run (inside the jbpm-console-ng-showcase dir)
This will run the app in dev mode. It will open a GWT window which will deploy the app and it has a button to copy the application link to your clipboard. Then paste the url from your clipboard in Firefox (it needs to be firefox for now, we use it to test the app in development).
The app should show the login screen. Use salaboy/salaboy to log in and tets the app.
Please let me know if you have problems.
Cheers
LikeLike
Thanks a lot for your reply.
Here is the error I get while typing mvn clean install:
C:\Documents and Settings\natsumme\workspace\jbpm-console-ng>mvn clean install
[INFO] Scanning for projects…
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.jbpm:jbpm-console-ng:6.0.0-SNAPSHOT (C:\Documents and Settings\natsumme\workspace\jbpm-console-ng\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact org.drools:drools jbpm-parent:pom:6.0.0-SNAPSHOT and ‘parent.relativePath’ points at wrong local POM @ line 19, column 11 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Natsumme
LikeLike
Hmm… that could be related to the drools and jbpm parent pom not being exposed by nexus. Try the following and let me know if the problem is solved:
1) git clone https://github.com/droolsjbpm/droolsjbpm-build-bootstrap.git
2) cd droolsjbpm-build-bootstrap
3) mvn clean install
and then try to follow once again the steps to compile the jbpm console ng.
Cheers
LikeLike
Now, it compiles and ‘runs’ but
A)
I get the two following warnings on the console (after typing mvn gwt:run):
1)
[WARNING] Some problems were encountered while building the effective model for
org.jbpm:jbpm-console-ng-showcase:war:6.0.0-SNAPSHOT
[WARNING] ‘build.plugins.plugin.version’ for org.jboss.errai:jacoco-gwt-maven-plugin is missing. @ line 348, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
2)
[WARNING] Your POM does not match your hosted webapp WEB-INF/classes folder for GWT Hosted browser to see your classes.
B)It crashes in firefox just after logging kris/kris with the following message:
onModuleLoad() threw an exception
Exception while loading module org.jboss.errai.ioc.client.Container. See Development Mode for details.
java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:406) at com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:200) at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:526) at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.RuntimeException: critical error in IOC container bootstrap at org.jboss.errai.ioc.client.Container.bootstrapContainer(Container.java:69) at org.jboss.errai.ioc.client.Container.onModuleLoad(Container.java:34) … 9 more Caused by: java.lang.RuntimeException: Deferred binding failed for ‘org.jboss.errai.ioc.client.Bootstrapper’ (did you forget to inherit a required module?) at com.google.gwt.dev.shell.GWTBridgeImpl.create(GWTBridgeImpl.java:53) at com.google.gwt.core.shared.GWT.create(GWT.java:57) at com.google.gwt.core.client.GWT.create(GWT.java:85) at org.jboss.errai.ioc.client.Container.bootstrapContainer(Container.java:55) … 10 more Caused by: com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries) at com.google.gwt.dev.shell.ModuleSpace.rebindAndCreate(ModuleSpace.java:513) at com.google.gwt.dev.shell.GWTBridgeImpl.create(GWTBridgeImpl.java:49) … 13 more
LikeLike
Use, salaboy/salaboy as user and password. If you open the GWT Window, the last tab (which should say FF or Firefox will highlight you a red line with the original exception), can you please copy that exception here? Cheers
LikeLike
In the last tab (called jBPM/FF) there are four errors:
1) 00:00:50,999 [ERROR] Uncaught exception escaped
2) 00:00:50,999 [ERROR] Failed to create an instance of ‘org.jboss.errai.ioc.client.Bootstrapper’ via deferred binding
3) 00:00:51,015 [ERROR] Unable to load module entry point class org.jboss.errai.ioc.client.Container (see associated exception for details)
4) 00:00:51,015 [ERROR] Failed to load module ‘org.jbpm.console.ng.jBPMShowcase’ from user agent ‘Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/20100101 Firefox/18.0’ at 3dns.adobe.com:4576
Here are the details of the first one:
java.lang.IllegalArgumentException: Something other than a Java object was returned from JSNI method ‘@com.google.gwt.core.client.impl.Impl::apply(Ljava/lang/Object;Ljava/lang/Object;Ljava/lang/Object;)’: JS value of type boolean, expected java.lang.Object at com.google.gwt.dev.shell.JsValueGlue.get(JsValueGlue.java:178) at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:281) at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91) at com.google.gwt.core.client.impl.Impl.apply(Impl.java) at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:242) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71) at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172) at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:338) at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:219) at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136) at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:571) at com.google.gwt.dev.shell.ModuleSpace.invokeNativeBoolean(ModuleSpace.java:194) at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeBoolean(JavaScriptHost.java:35) at org.jboss.errai.common.client.util.LogUtil.isNativeJavaScriptLoggerSupported(LogUtil.java) at org.jboss.errai.common.client.util.LogUtil.log(LogUtil.java:29) at org.jboss.errai.common.client.api.extension.InitVotes.waitFor(InitVotes.java:113) at org.jboss.errai.common.client.api.extension.InitVotes.waitFor(InitVotes.java:106) at org.jboss.errai.databinding.client.DataBindingModuleBootstrapper.run(DataBindingModuleBootstrapper.java:34) at org.jboss.errai.ioc.client.BootstrapperImpl.(BootstrapperImpl.java:392) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.google.gwt.dev.shell.ModuleSpace.rebindAndCreate(ModuleSpace.java:475) at com.google.gwt.dev.shell.GWTBridgeImpl.create(GWTBridgeImpl.java:49) at com.google.gwt.core.shared.GWT.create(GWT.java:57) at com.google.gwt.core.client.GWT.create(GWT.java:85) at org.jboss.errai.ioc.client.Container.bootstrapContainer(Container.java:55) at org.jboss.errai.ioc.client.Container.onModuleLoad(Container.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:406) at com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:200) at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:526) at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364) at java.lang.Thread.run(Thread.java:722)
LikeLike
That’s a strange error in the GWT FF plugin and the JDK version. I didn’t manage to solve that problem yet. it seems only related with GWT and a specific combination of the JDK and the Operating System. If you try chrome you will see that it works perfectly.
LikeLike
Salaboy, I am really sorry: It works great!
I realized that i get another web server running on my PC;
when I stopped it, it worked on FF.
The installation process is also super easy (it just prequisite a droolsjbpm-build-bootstrap git clone)
I ll start using it and I let you know
Natsumme
LikeLike
Thanks! I’m working to make it easier. I need to notify the drools team that the parent poms for some reason are not being published. droolsjbpm-build-bootstrap shouldn’t be a requirement.
Cheers
LikeLike
Thanks salaboy! I appreciate your work. I am looking forward to use console ng for a customer project and maybe to contribute to its further developement. Now, I need your help. When building jbpm-console-ng-showcase I get some warnings and an error:
[INFO] ————————————————————————
[INFO] Building jBPM Console NG – Showcase 6.0.0-SNAPSHOT
[INFO] ————————————————————————
[WARNING] The POM for jbpt:jbpt:jar:0.1.0 is missing, no dependency information available
[WARNING] The POM for org.supercsv:SuperCSV:jar:1.52 is missing, no dependency information available
[INFO] — gwt-maven-plugin:2.5.0:compile (gwt-compile) @ jbpm-console-ng-showcase —
[WARNING] Declared compileSourcesArtifact was not found in project dependencies org.kie.guvnor:guvnor-common-ui:jar
[WARNING] Declared compileSourcesArtifact was not found in project dependencies org.kie.guvnor:guvnor-project-client:jar
[ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.5.0:compile (gwt-compile) on project jbpm-console-ng-showcase: Failed to execute command line :
… (classpath, all dependencies and parameters are listed)…, org.jbpm.console.ng.FastCompiledjBPMShowcase]: Error while executing
process. Cannot run program “C:\Program Files (x86)\Java\jdk1.6.0_41\jre\bin\java”: CreateProcess error=206, The filename or extension is too long
Any suggestion how I can fix the error? I’m very grateful for your help.
LikeLike
Hmm that’s a Window$ issue, I’m afraid that with the little information that you are showing here it’s impossible to help you. Which version of Maven do you have? can you compile another maven projects?
We need to find out which command execution is causing issues with Window$
Cheers
LikeLike
I am using the version 3.0.5. I can compile all other projects up to showcase. Here is some more information:
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to execute command line :
[-Xmx1024m, -XX:MaxPermSize=256m, -classpath, C:\Users\IT1\.m2\repository\com\google\gwt\gwt-user\2.5.0\gwt-user-2.5.0.jar;…
… (all other dependencies are listed here)…
…com.google.gwt.dev.Compiler, -logLevel, INFO, -style, OBF, -war, C:\Users\IT1\Desktop\jBPM-Projekt\github\jbpm-console-ng\jbpm-console-ng-showcase\target\jbpm-console-ng-showcase-6.0.0-SNAPSHOT, -localWorkers, 4, -Xfra
gmentCount, -1, -gen, C:\Users\IT1\Desktop\jBPM-Projekt\github\jbpm-console-ng\jbpm-console-ng-showcase\target\.generated, org.jbpm.console.ng.FastCompiledjBPMShowcase]
at org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo$JavaCommand.execute(AbstractGwtShellMojo.java:500)
at org.codehaus.mojo.gwt.shell.CompileMojo.compile(CompileMojo.java:365)
at org.codehaus.mojo.gwt.shell.CompileMojo.doExecute(CompileMojo.java:280)
at org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo.execute(AbstractGwtShellMojo.java:172)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
… 19 more
Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while executing process.
at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:656)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:144)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:107)
at org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo$JavaCommand.execute(AbstractGwtShellMojo.java:480)
… 24 more
Caused by: java.io.IOException: Cannot run program “C:\Program Files (x86)\Java\jdk1.6.0_41\jre\bin\java”: CreateProcess error=206, Der Dateiname oder die Erweiterung ist zu lang
at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
at java.lang.Runtime.exec(Runtime.java:593)
at java.lang.Runtime.exec(Runtime.java:509)
at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:636)
… 27 more
Caused by: java.io.IOException: CreateProcess error=206, Der Dateiname oder die Erweiterung ist zu lang
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
… 30 more
LikeLike
Pasting the stack trace here doesn’t help at all. You should use pastebin and just paste the link here.
Can you check your PATH variable in window$ to see if has the appropriate “quoutes” I’m guessing that window$ is not clever enough to identify which is the executable and which are the paremeters. This is a generic maven/Window$ issue, it’s not related with the console itself, can you please try to google it to see if we can find a solution?
Cheers
LikeLike
Something that I noticed in the stack trace is that you are pointing to a JRE instead of a JDK, can you please make sure that you have correctly configured the JDK in your environment?
Cheers
LikeLike
Thanks for your response! I solved the problem by shortening the class path (Alternative solutions can be found here: http://code.google.com/p/gwt-maven/issues/detail?id=88). Now I am having a problem when starting the application on jetty. I would be grateful if you could have a look at the stack trace: http://pastebin.com/GdT75RkA
Thanks
LikeLike
Hi Fabo,
How are you running the console? from where?
Cheers
LikeLike
Hi Fabo,
I am also facing the issue “CreateProcess error=206, The filename or extension is too long”. Whats are the exact steps you followed to solve this problem. I am using Windows 7 64bit.
Thanks
LikeLike
Hi Salaboy,
sorry, but I don’t quite get what you are trying to ask. Do you mean the OS, browser, or something else?
LikeLike
How are you running the application? Can you describe the steps? If you are running the app in dev mode, you need to use Firefox or chrome to test it.
LikeLike
Hi Mauricio, I follow instructions for build form source, but a get the next output
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.jbpm:jbpm-console-ng-showcase:6.0.0-SNAPSHOT (/home/jlgranda/glue/workspace/droolsjbpm/jbpm-console-ng/jbpm-console-ng-showcase/pom.xml) has 1 error
[ERROR] ‘dependencies.dependency.version’ for org.apache.felix:org.osgi.core:jar is missing. @ line 266, column 17
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
Please any suggestion for solve this.
LikeLike
Hi,
We are under heavy refactoring right now, I’m fighting to stabilize the situation in the master. The error that you are getting is because there is a missing version in an artifact in the jbpm-console-ng-showcase project. If you add the version to it it will work. I will write a new version of this post this week.
Cheers
LikeLike
Thak you. I managed to compile, indicating the version 1.4.0
org.apache.felix
org.osgi.core
1.4.0
I wait for new post.
LikeLike
HI
Trying to configure NG with postgresql but it cant create tables in postgresql.
So any scripts like jbpm5.4 Schema or some way i can configure so that it can fire the scripts.?
Thanks
Naman Shah
LikeLike
Hi Naman,
Are you using the Console NG with postgresql? or 5.4? because the console uses 6.0.0-SNAPSHOT. For the console, the only thing that you need to do is to configure the jboss data source to work with postgresql, for that you will need to provide the driver. If you go inside the app and look for the persistence.xml file you will be able to set hibernate to create the tables for you.
Cheers
LikeLike
I had cloned the console-ng.git and just try to run the show case.
yeah I did the things and it worked well.
1) Configured jboss
2)Persistence
Thanks
Trying to get more into uber fire and CDI for using it perfectly the show case doing.
M just trying to shift myself from jbpm 5.4 to 6.
Cheers
LikeLike
Hi Naman,
That sounds good! Let me know if you have troubles with the console or if you want to see something else or something improved there.
I’m looking forward for contributors, so feel free to let us know if you are interested in help us.
Cheers
LikeLike
Yeah Sure!
Targeting a week for handson with uberfire and jbpm 6, Will surely let you know.
Some Videos or tutorials will be good for startup!
Documentation helps a lot thanks for that 🙂
LikeLike
great issues altogether, you just received a new
reader. What could you recommend in regards to your put up
that you simply made some days ago? Any certain?
LikeLike
You can use Long Path Tool to solve problem of error-206 .it is very helpful for long filename or extension problem
LikeLike