February 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2837) StatefulKnowledgeSession.startProcess not thread-safe

by Maxence Dewil (JIRA)

StatefulKnowledgeSession.startProcess not thread-safe ----------------------------------------------------- Key: JBRULES-2837 URL: https://issues.jboss.org/browse/JBRULES-2837 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.0.M2 Reporter: Maxence Dewil Assignee: Mark Proctor See http://drools-java-rules-engine.46999.n3.nabble.com/StatefulKnowledgeSess... and http://drools-java-rules-engine.46999.n3.nabble.com/Weird-Problem-WorkIte... The documentation does specify anything about thread-safety (https://hudson.jboss.org/hudson/job/jBPM5/lastSuccessfulBuild/artifact/ta...) The classes org.drools.process.instance.impl.DefaultProcessInstanceManager and org.drools.process.instance.impl.DefaultWorkItemManager are not synchronized. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
9
0 / 0

[JBoss JIRA] Created: (JBRULES-2876) Table names specified in hibernate annotations are too long for oracle.

by michael visee (JIRA)

Table names specified in hibernate annotations are too long for oracle. ----------------------------------------------------------------------- Key: JBRULES-2876 URL: https://issues.jboss.org/browse/JBRULES-2876 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-process-task Affects Versions: 5.1.1.FINAL Reporter: michael visee Assignee: Mark Proctor Many table names specified in the hibernate annotations of the org.drools.task package are too long. This prevents us to deploy the task service database on oracle because oracle table names must be 30 characters long at most. A few example are the following: PeopleAssignments_PotentialOwners, PeopleAssignments_ExcludedOwners, PeopleAssignments_TaskStakeholders, PeopleAssignments_BusinessAdministrators, PeopleAssignments_Recipients in the PeopleAssignments class -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2354) service integration with flow

by Mark Proctor (JIRA)

service integration with flow ----------------------------- Key: JBRULES-2354 URL: https://jira.jboss.org/jira/browse/JBRULES-2354 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-process Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.1.0.M2 Make sure that Drools Flow has work items for the various service/endpoint interactions and invocations. As often this involves sending a script, it could involve a little script builder. that allows you to add commands and arguments (literal or variable). -- 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

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2711) Could not connect task client

by José Manuel García Rivas (JIRA)

Could not connect task client ----------------------------- Key: JBRULES-2711 URL: https://jira.jboss.org/browse/JBRULES-2711 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-process-task Affects Versions: 5.1.1.FINAL Environment: JBoss 4.2.3-GA JDK 6u14 Windows Reporter: José Manuel García Rivas Assignee: Mark Proctor Fix For: 5.2.0.M1 Just after logging in the BPM console, it sends me to http://localhost:8080/gwt-console/app.html#errai_ToolSet_Tasks;none and shows a "Could not connect task client" error and a stacktrace. * URL: 'http://localhost:8080/gwt-console-server/rs/tasks/admin' * Action: 'org.jboss.bpm.console.client.task.LoadTasksAction' * Exception: 'class com.google.gwt.http.client.RequestException' HTTP 500: Estado HTTP 500 - type Informe de Excepción mensaje descripción El servidor encontró un error interno () que hizo que no pudiera rellenar este requerimiento. (The server encountered an internal error that prevented it to fulfiill this requirement) excepción org.jboss.resteasy.spi.UnhandledException: java.lang.IllegalArgumentException: Could not connect task client org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319) org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230) org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) causa raíz java.lang.IllegalArgumentException: Could not connect task client org.drools.integration.console.DroolsFlowTaskManagement.connect(DroolsFlowTaskManagement.java:59) org.drools.integration.console.DroolsFlowTaskManagement.getAssignedTasks(DroolsFlowTaskManagement.java:128) org.jboss.bpm.console.server.TaskListFacade.getTasksForIdRef(TaskListFacade.java:99) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1968) Eclipse ruleflow editor cut, copy and paste operations appear to be allowed but do not work

by Shahad Ahmed (JIRA)

Eclipse ruleflow editor cut, copy and paste operations appear to be allowed but do not work ------------------------------------------------------------------------------------------- Key: JBRULES-1968 URL: https://jira.jboss.org/jira/browse/JBRULES-1968 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse, drools-eclipse (expert), drools-eclipse (flow) Affects Versions: 5.0.0.M5 Reporter: Shahad Ahmed Assignee: Mark Proctor The Edit menu in the drools eclipse plugin contains options to Cut, Copy and Paste nodes for a ruleflow editor. However, these operations do not work in the editor and cause exceptions to be reported in the eclipse log. For example, if you attempt to copy a ruleflow node then you get the following error on the eclipse log: !ENTRY org.eclipse.ui 4 4 2009-02-12 13:40:16.843 !MESSAGE Failed to execute item copy !STACK 0 org.eclipse.core.commands.NotHandledException: There is no handler to execute for command org.eclipse.ui.edit.copy I assume the Ruleflow editor is not intended to support cut, copy and paste of nodes as was the case in Drools 4, and that this is simply a minor bug to do with the cut, copy and paste menu options not being greyed out, as in drools v4 plugin. Of course, it would be nice to have cut, copy and paste for ruleflow nodes, so perhaps this JIRA could be reclassified as a feature request, if appropriate. -- 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

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2489) Flow editor should use namespace in file content type checking

by Robert (Bob) Brodt (JIRA)

Flow editor should use namespace in file content type checking -------------------------------------------------------------- Key: JBRULES-2489 URL: https://jira.jboss.org/jira/browse/JBRULES-2489 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Affects Versions: 5.1.0.M1, 5.0.1.FINAL Reporter: Robert (Bob) Brodt Assignee: Mark Proctor Priority: Optional The root element of a *.rf file is "process" which conflicts with BPEL files, so content type checking in the flow editor should be enhanced to include the root element's namespace, "http://drools.org/drools-5.0/process" -- 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

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2497) Work items listed in palette in reverse order from .conf file.

by Edward Staub (JIRA)

Work items listed in palette in reverse order from .conf file. -------------------------------------------------------------- Key: JBRULES-2497 URL: https://jira.jboss.org/jira/browse/JBRULES-2497 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Affects Versions: 5.0.1.FINAL Reporter: Edward Staub Assignee: Mark Proctor Priority: Minor The flow editor palette lists work items in the opposite order from the order in the .conf file. Similarly, when there are multiple .conf files, the work items are in opposite order. -- 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

15 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2879) Exception when type empty in Convering Gateway

by Matias Rivera (JIRA)

Exception when type empty in Convering Gateway ---------------------------------------------- Key: JBRULES-2879 URL: https://issues.jboss.org/browse/JBRULES-2879 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Affects Versions: 5.2.0.M2 Environment: Windows Vista 7 Eclipse Version: Helios Service Release 1 Build id: 20100917-0705 Reporter: Matias Rivera Assignee: Mark Proctor If you are creating a process or editing an existing one and you add a Gateway [converge] from the components Pallete and do not set a Type, the next time you open the bpmn process in the "BPMN2 Process Editor" it throws the following exception java.lang.IllegalArgumentException: Unknown gateway direction: Converging at org.jbpm.bpmn2.xml.ComplexGatewayHandler.createNode(ComplexGatewayHandler.java:37) at org.jbpm.bpmn2.xml.AbstractNodeHandler.start(AbstractNodeHandler.java:64) at org.drools.xml.ExtensibleXmlParser.startElement(ExtensibleXmlParser.java:384) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.emptyElement(XMLSchemaValidator.java:739) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2755) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at org.drools.xml.ExtensibleXmlParser.read(ExtensibleXmlParser.java:295) at org.drools.xml.ExtensibleXmlParser.read(ExtensibleXmlParser.java:174) at org.jbpm.compiler.xml.XmlProcessReader.read(XmlProcessReader.java:44) at org.drools.eclipse.flow.bpmn2.editor.BPMNModelEditor.createModel(BPMNModelEditor.java:210) at org.drools.eclipse.flow.common.editor.GenericModelEditor.setInput(GenericModelEditor.java:286) at org.drools.eclipse.flow.bpmn2.editor.BPMNModelEditor.setInput(BPMNModelEditor.java:96) at org.eclipse.gef.ui.parts.GraphicalEditor.init(GraphicalEditor.java:346) at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:647) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2863) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2682) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:651) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:610) at org.eclipse.ui.actions.OpenFileAction.openFile(OpenFileAction.java:99) at org.eclipse.ui.actions.OpenSystemEditorAction.run(OpenSystemEditorAction.java:99) at org.eclipse.ui.views.navigator.OpenActionGroup.runDefaultAction(OpenActionGroup.java:133) at org.eclipse.ui.views.navigator.MainActionGroup.runDefaultAction(MainActionGroup.java:330) at org.eclipse.ui.views.navigator.ResourceNavigator.handleOpen(ResourceNavigator.java:787) at org.eclipse.ui.views.navigator.ResourceNavigator$6.open(ResourceNavigator.java:499) at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:845) 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:843) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1131) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1235) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:264) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:258) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:298) 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:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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:369) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) I think the problem resides in the node. The empty gateway node type is <complexGateway name="Gateway" gatewayDirection="Converging" /> While the gateway with type is <exclusiveGateway name="Gateway" gatewayDirection="Converging" /> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

6
9
0 / 0

[JBoss JIRA] Created: (JBRULES-2828) can not delete variables mapping from parameter mapping screen of human task in drools flow

by shashi mhatre (JIRA)

can not delete variables mapping from parameter mapping screen of human task in drools flow ------------------------------------------------------------------------------------------- Key: JBRULES-2828 URL: https://issues.jboss.org/browse/JBRULES-2828 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Affects Versions: 5.2.0.M1 Environment: eclipse 3.6 java 1.6 windows platform Reporter: shashi mhatre Assignee: Mark Proctor i have created a simple workflow with one human task in it. i am passing one variable to main process flow and then passing same variable to human task. now when i went to delete the parameter mapping of main process flow and human task variable, remove button in parameter mapping is disabled, i can add new parameter mapping but can not remove the old entries. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2472) Suppport composite nodes when debugging

by Kris Verlaenen (JIRA)

Suppport composite nodes when debugging --------------------------------------- Key: JBRULES-2472 URL: https://jira.jboss.org/jira/browse/JBRULES-2472 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.1.0.M2 The debugger only shows the composite node as active, not which node instances inside the composite node are active. -- 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

15 years, 2 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2011