[jBPM] - Simple process with WorkItemHandler doesn't end
by Jim B
Jim B [https://community.jboss.org/people/jamesbeam] created the discussion
"Simple process with WorkItemHandler doesn't end"
To view the discussion, visit: https://community.jboss.org/message/810118#810118
--------------------------------------------------------------
Using jBPM 5.4 with persistence (Hibernate 4, and JPA2) I have a 4 node process:
*start*->*MyWorkItemHandler*->*Script* (System.out.println("done") ->(terminating) *end*.
The only thing my workItemhandler does is complete the workitem. workItemManager.completeWorkItem(workItem.getId(),null);
The process starts, and the workitem handler completes. I get the "done" printed on the screen. I see in the NodeInstanceLog that my terminating end node is reached and completed (type=1). I also set up a ProcessEventlistener and see that the afterProcessCompleted() gets called with the processID I'm expecting.
HOWEVER, my process is never marked as completed in the ProcessInstanceLog (Status = 0);
Has anyone seen this? Does anyone have any thoughts as to what is going on? A bug?
Thanks,
-J
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/810118#810118]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[JBoss Web Services] - NullPointerException while converting AXIS client to JBOSSWS client
by roopachakra
roopachakra [https://community.jboss.org/people/roopachakra] created the discussion
"NullPointerException while converting AXIS client to JBOSSWS client"
To view the discussion, visit: https://community.jboss.org/message/810829#810829
--------------------------------------------------------------
Hello,
We are trying to convert existing AXIS webservice client to JBOSS WS client. I tried installing Jboss tools to eclipse Juno. Set the JBOSS WS runtime like below.
Window->Preferences->Web Services->JBossWS Preferences->Add. Then provide a name (eg. jboss-eap-5.1.0), Home Folder: $JBOSS_HOME (which is the jboss-as folder)
While converting existing WSDL to webservice client I get below exception. Even though I set runtime location properly it still doesn't find the location.
Was wondering if anyone come across such error and resolved it.
IWAB0014E Unexpected exception occurred.
java.lang.NullPointerException
at org.jboss.tools.ws.creation.core.utils.JBossWSCreationUtils.getJBossWSRuntimeLocation(JBossWSCreationUtils.java:296)
at org.jboss.tools.ws.creation.core.commands.InitialClientCommand.execute(InitialClientCommand.java:62)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:908)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
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.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
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(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:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)"
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/810829#810829]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[jBPM] - afterProcessCompleted() not firing when last workflow task is business rule
by cold gin
cold gin [https://community.jboss.org/people/cold_gin] created the discussion
"afterProcessCompleted() not firing when last workflow task is business rule"
To view the discussion, visit: https://community.jboss.org/message/810546#810546
--------------------------------------------------------------
Hello. I have a workflow that contains a business rule as the last task, and exists on the flow just prior to a terminal (stop) task (jBPM 5.4.0). When this business rule task is present on the workflow definition, the afterProcessCompleted() event never fires on the DefaultProcessEventListener that I am attaching to my knowledge session. If I remove the business rule task in designer and re-execute the workflow, the event does fire on the DefaultProcessEventListener.
I do not have any special configuration anywhere else in my setup that relates to this business rule task, as I was given this workflow by a third party. The code for the business rule from designer is as follows:
<bpmn2:businessRuleTask xmlns:bpmn2=" http://www.omg.org/spec/BPMN/20100524/MODEL http://www.omg.org/spec/BPMN/20100524/MODEL" id="_51E71516-F613-4F75-BC82-88975FD75864" drools:selectable="true" xmlns:drools=" http://www.jboss.org/drools http://www.jboss.org/drools" drools:ruleFlowGroup="Retract" name="Retract_Object">
<bpmn2:incoming>_ABC4091E-50C7-4B41-88D9-C4592DF259E3</bpmn2:incoming>
<bpmn2:outgoing>_D86BD4F5-5151-4D67-863B-5AAE9D56E08E</bpmn2:outgoing>
</bpmn2:businessRuleTask>
The workflow basically goes like this:
start => human task => script task => business rule task => stop [afterProcessCompleted() does not fire]
start => human task => script task => stop [afterProcessCompleted() fires as expected]
I am new to jBPM and drools, and I was wondering if anybody can explain this behavior, and how to get the afterProcessCompleted() event to fire? Thanks in advance for any insight.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/810546#810546]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[JBoss Tools] - JBoss Tools Reloaded
by Max Rydahl Andersen
Max Rydahl Andersen [https://community.jboss.org/people/maxandersen] modified the blog post:
"JBoss Tools Reloaded"
To view the blog post, visit: https://community.jboss.org/community/tools/blog/2013/04/29/jboss-tools-r...
--------------------------------------------------------------
Today it is time for Alpha 2 of JBoss Tools 4.1 with a great set of new improvements which I'll cover after the jump...
h3. JBoss Tools 4.1 Alpha 2
+Reloaded+
Developer Studio: [ http://devstudio.jboss.com/earlyaccess Download] | Tools: [ http://www.jboss.org/tools/download Download] [ http://download.jboss.org/jbosstools/updates/development/kepler/ Update Site] | [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exists for JBoss and related technologies in the default Eclipse distribution.
JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes the majority of JBoss Tools but also all its needed dependencies and 3rd party plugins, allowing for an easy one-click and no-fuss installation.
If you are into doing your own bleeding edge eclipse plugin assembly, JBoss Tools is for you; if you are more into having something that "Just Works" then JBoss Developer Studio is the way to go.
h1. Installation
This release is still an alpha and is built against http://www.eclipse.org/downloads/index-developer.php Kepler M6 (Eclipse 4.3M6), and as such things can and will still change before the final Kepler release.
Use the http://download.jboss.org/jbosstools/updates/development/kepler/ Update Site from within Kepler M6 or http://devstudio.jboss.com/earlyaccess Download Developer Studio and be sure to have the exact correct Eclipse base (note: in Alpha2 the live reload feature is only in JBoss Tools, it will arrive in Developer Studio in the next release)
h1. Improvements
In this round our main highlight is the introduction of LiveReload support in Eclipse, but a few other extra items are also to be found if you continue reading...
h2. Live reload in Eclipse
Our new Live reload feature allows you to have your browser automatically refresh when you save your html, javascript and css files. No need to press refresh manually anymore - you can just focus on content and functionallity and instantly see and use the changes in your browser.
If it is hard to imagine how it works, Xavier Coulon made the following video showing how to activate and use it:
It might not look at much, but when you first start to use it you get rather hooked at it because of the nice instant feedback. Especially if this is the first time you tried using something like live reload with your browser.
It is important to note that to use this you should install a livereload plugin/extension into your browser as documented in our http://docs.jboss.org/tools/whatsnew/livereload/livereload-news-1.0.0.Alp... What’s New and Noteworthy.
In this first release of livereload support we focused on making resources loaded from the local file system supereasy to do and use; we also focused on using the existing http://feedback.livereload.com/knowledgebase/articles/86174-livereload-pr... defacto protocol usd by LiveReload and related plugins meaning any browser, script and tool that works with live reload today should work with our Eclipse implementation of it.
In upcoming release of JBoss Tools the live reload feature will also be part of Developer Studio, require even less setup (today you need to “add the server”, next it will be setup automatically and we’ll ask if you want to start it), we will support live reload of content deployed via server adapters (localhost and remote servers and not just limited to JBoss AS/EAP servers) and finally we will also provide a proxied server to allow you to do easy testing on any browser, including mobile devices without installing any browser plugins.
But for now, enjoy having automatic reload of file based URLs, super nice for HTML5/JS based applications.
h2. JQuery Mobile Palette
To support HTML5 and mobile client development we’ve added a new HTML palette with initial support for JQuery Mobile.
This palette will show up when you edit HTML5 files (files with <!DOCTYPE HTML> doc type). If it does not show up, it is probably using HTML4 or XHTML content types.
The JQuery Mobile palette features a dialog preview when you click or drag one of the buttons for a component, it lets you see and customize what will be inserted.
The palette looks like this:
http://docs.jboss.org/tools/whatsnew/jst/images/4.1.0.Alpha2/lf.png http://docs.jboss.org/tools/whatsnew/jst/images/4.1.0.Alpha2/lf.png
and Alexey Kazakov r http://www.screenr.com/embed/7M57 ecorded a video to show it in action.
h2. BrowserSim Screenshot
The Browser Simulator now have easy screenshot facility to share your awesome design or nasty bug you want someone to hunt down.
http://docs.jboss.org/tools/whatsnew/browsersim/images/4.1.0.Alpha2/scree... http://docs.jboss.org/tools/whatsnew/browsersim/images/4.1.0.Alpha2/scree...
h2. BrowserSim "Remote" Debugging
In the previous release we added Firebug for easy local debugging but we've now also added Weinre support, allowing you to use any Weinre compatible server to debug/inspect the application running in BrowserSim.
http://docs.jboss.org/tools/whatsnew/browsersim/images/4.1.0.Alpha2/weinr... http://docs.jboss.org/tools/whatsnew/browsersim/images/4.1.0.Alpha2/weinr...
h2. OpenShift Restart
We've started adding more operations to OpenShift Tools to make you less dependent on the OpenShift command line tools (note: the command line tools are great and we are 100% compatible - we just prefer not to be 100% dependent on them).
In this release we've added "Restart" to the UI allowing you to trigger a node restart for your application in case something bad has happened or you changed a configuration that requires a full node restart.
http://docs.jboss.org/tools/whatsnew/openshift/images/restart-application... http://docs.jboss.org/tools/whatsnew/openshift/images/restart-application...
h2. Where is WildFly ?
The JBoss AS project was recently renamed to http://www.wildfly.org WildFly. For now JBoss Tools does not have specific support for WildFly since there have not yet been an actual binary release.
In this release if you are building WildFly from source the JBoss AS 7.1 adapter should work since WildFly still is compatible with AS 7.x.
We will support WildFly specific features/layout it in later releases.
h2. Giving Feedback
There are more news and screenshots in http://docs.jboss.org/tools/whatsnew What's New, and if you got an idea to an improvement or found a bug do not hestiate to open an issue in our https://jira.jboss.org/jira/browse/JBIDE issue tracker.
h2. What's Next ?
Next release is planned to be our first beta which will include the Cordova Mobile tooling, improved live reload support, a few Javascript surprises and general awesomeness.
Follow this blog for more or contact us on our https://community.jboss.org/community/tools?view=discussions forum and irc if you are interested in contributing!
Have fun reloading!
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/community/tools/blog/2013/04/29/jboss-tools-r...]
13 years, 1 month
[jBPM] - how to use localtaskservice
by yayu zhu
yayu zhu [https://community.jboss.org/people/a_alter] created the document:
"how to use localtaskservice"
To view the document, visit: https://community.jboss.org/docs/DOC-48631
--------------------------------------------------------------
i have a question about local taskservice.
will auto create human task info that in process to database when i start a process?
Whether you can use jpa transaction manager?
In my test, i use jpa transaction.
Local Process session
*local task server*
*
*
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.1.xsd">
<bean id="systemEventListener" class="org.drools.SystemEventListenerFactory" factory-method="getSystemEventListener" />
<bean id="internalTaskService" class="org.jbpm.task.service.TaskService">
<property name="systemEventListener" ref="systemEventListener" />
</bean>
<bean id="htTxManager" class="org.drools.container.spring.beans.persistence.HumanTaskSpringTransactionManager">
<constructor-arg ref="transactionManagerTask" />
</bean>
<bean id="springTaskSessionFactory" class="org.jbpm.task.service.persistence.TaskSessionSpringFactoryImpl" init-method="initialize"
depends-on="internalTaskService">
<property name="entityManagerFactory" ref="taskEmf" />
<property name="transactionManager" ref="htTxManager" />
<property name="useJTA" value="false" />
<property name="taskService" ref="internalTaskService" />
</bean>
<bean id="taskService" class="org.jbpm.task.service.local.LocalTaskService" depends-on="springTaskSessionFactory">
<constructor-arg ref="internalTaskService" />
</bean>
</beans>
Unit Test
@Test
public void testHumanTask() {
Map<String, Object> map = new HashMap<String, Object>();
map.put("employee", "a_alter");
LocalHTWorkItemHandler humanTaskHandler = new LocalHTWorkItemHandler(service, session);
humanTaskHandler.connect();
session.getWorkItemManager().registerWorkItemHandler("Human Task", humanTaskHandler);
session.startProcess("com.sample.evaluation", map);
}
i find in startProcess, the human task will open a single session and ltaskservicesession addtask will not commit immidate, but the entitymanagerholder is shared.
at the last it will excute DroolsSpringTransactionManager commit; but the the session about humantask will not commit;
why? I must need use JTA?
==============================
there is another question, I'm not find how to working about Humantask' workitemhandler.
where i can find it?
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-48631]
Create a new document in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
13 years, 1 month
