January 2011 - jboss-jira - Jboss List Archives

[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

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

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
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

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2498) Support multiple palette "drawers" for work items

by Edward Staub (JIRA)

Support multiple palette "drawers" for work items ------------------------------------------------- Key: JBRULES-2498 URL: https://jira.jboss.org/jira/browse/JBRULES-2498 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Affects Versions: 5.0.1.FINAL Reporter: Edward Staub Assignee: Mark Proctor In contexts where there are many workitem definitions, the palette will be much friendlier if workitems can be split into separate categories that can be pinned or closed individually. I'd suggest an optional drawer name at the top level of the workitem .conf file, and mapping each such .conf file to a separate drawer - but there are many good alternatives. -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1770) IndexOutOfBoundsException with subflows while removing listener from RuleFlowEventSupport

by Richard bedard (JIRA)

IndexOutOfBoundsException with subflows while removing listener from RuleFlowEventSupport ----------------------------------------------------------------------------------------- Key: JBRULES-1770 URL: https://jira.jboss.org/jira/browse/JBRULES-1770 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Rule Flow Affects Versions: 4.0.7 Environment: MyEclipse Blue, Windows XP, Reporter: Richard bedard Assignee: Mark Proctor I have 9 ruleFlows, A, B and C and 6 others A is the main one that include B as a subflow and 6 others, B include C as a subflow When RuleFlowEventSupport.fireRuleFlowProcessCompleted is called, the listeners list contains 8 elements, 1 per sub ruleflow. The size of the list is set in a variable "i" for performance i guess: for ( int i = 0, size = this.listeners.size(); i < size; i++ ) { But somehow, i didn't check the reason, the method removeEventListener is called and the list size is now 7, so im having an java.lang.IndexOutOfBoundsException. This appen when the subflow C isn't changing the working memory(no insert, modify or remove), when an object is inserted, there is no error... I've tried with and without shadow fact "setShadowProxy( false/true );" Object removed: listener RuleFlowProcessInstanceImpl (id=7454) id 2 nodeInstances ArrayList<E> (id=7749) process RuleFlowProcessImpl (id=7750) state 2 workingMemory ReteooStatefulSession (id=7444) Stack that show the object removing while iterating on the list: RuleFlowEventSupport.removeEventListener(RuleFlowEventListener) line: 48 <----- A listerner is removed here ReteooStatefulSession(AbstractWorkingMemory).removeEventListener(RuleFlowEventListener) line: 306 RuleFlowProcessInstanceImpl.setState(int) line: 184 EndNodeInstanceImpl.trigger(RuleFlowNodeInstance) line: 30 RuleFlowJoinInstanceImpl.triggerCompleted() line: 89 RuleFlowJoinInstanceImpl.checkActivation() line: 85 RuleFlowJoinInstanceImpl.trigger(RuleFlowNodeInstance) line: 59 SubFlowNodeInstanceImpl.triggerCompleted() line: 51 RuleFlowProcessInstanceImpl.ruleFlowCompleted(RuleFlowCompletedEvent, WorkingMemory) line: 262 RuleFlowEventSupport.fireRuleFlowProcessCompleted(RuleFlowProcessInstance, InternalWorkingMemory) line: 86 <--- Iterating on the listeners list here RuleFlowProcessInstanceImpl.setState(int) line: 185 EndNodeInstanceImpl.trigger(RuleFlowNodeInstance) line: 30 RuleFlowJoinInstanceImpl.triggerCompleted() line: 89 RuleFlowJoinInstanceImpl.checkActivation() line: 85 RuleFlowJoinInstanceImpl.trigger(RuleFlowNodeInstance) line: 59 RuleFlowGroupImpl(RuleFlowSequenceNodeInstanceImpl).triggerCompleted() line: 38 RuleFlowGroupImpl.setActive(boolean) line: 103 RuleFlowGroupImpl$DeactivateCallback.execute(InternalWorkingMemory) line: 211 ReteooStatefulSession(AbstractWorkingMemory).executeQueuedActions() line: 1312 ReteooStatefulSession(AbstractWorkingMemory).fireAllRules(AgendaFilter, int) line: 467 ReteooStatefulSession(AbstractWorkingMemory).fireAllRules() line: 439 DroolsStdImpl.executeRulesEngine(List<Object>, String) line: 100 -- 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

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-2859) DataAssociations dont interpret assignments/transformation from bpmn specification

by Anurag Aggarwal (JIRA)

DataAssociations dont interpret assignments/transformation from bpmn specification ---------------------------------------------------------------------------------- Key: JBRULES-2859 URL: https://issues.jboss.org/browse/JBRULES-2859 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (flow) Reporter: Anurag Aggarwal Assignee: Mark Proctor assignments are implemented incorrectly, and transformations seem to be entirely missing WorkItemNode defines private Map<String, String> inMapping = new HashMap<String, String>(); where as bpmn spec has {sorceRef*, targetRef, assignments*, transformation ?} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2802) Propagate process events to subprocess

by Jan Lisse (JIRA)

Propagate process events to subprocess -------------------------------------- Key: JBRULES-2802 URL: https://jira.jboss.org/browse/JBRULES-2802 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (flow) Affects Versions: 5.1.1.FINAL Reporter: Jan Lisse Assignee: Mark Proctor Currently events that are externally triggered using ProcessInstance.signalEvent() do not get propagated to subprocesses. For now i have to call session.getProcessInstances() iterate over the returned list of ProcessInstances and filter my subprocess from that list and finally call signalEvent() on the subprocess. It would be nice having automatical event propagation to subprocesses implemented. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1791) Parenthesis required for 'exist' rule in Split constraint editor

by Roger Lefebvre (JIRA)

Parenthesis required for 'exist' rule in Split constraint editor ---------------------------------------------------------------- Key: JBRULES-1791 URL: https://jira.jboss.org/jira/browse/JBRULES-1791 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Rule Flow Affects Versions: 4.0.7 Environment: Fedora 5, tomcat 6, drools 4.0.7 Reporter: Roger Lefebvre Assignee: Mark Proctor Priority: Minor A rule such as: exists Item() throws InvalidRulePackage "Unexpected token exists ..." when doing performing ruleBase.addPackage(builder.getPackage()). Adding parenthesis resolves the problem. e.g. exists (Item()) Similar applies to not and other qualifiers/functions. -- 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

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8149) default HSQL jta-data-source is not found in context

by Marek Novotny (JIRA)

default HSQL jta-data-source is not found in context ---------------------------------------------------- Key: JBAS-8149 URL: https://jira.jboss.org/browse/JBAS-8149 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: 6.0.0.M3, 6.0.0.M2, 6.0.0.M1 Environment: Build SVNTag:JBoss_6.0.0.20100429-M3 date: 20100502, Seam 2.2.1.CR1 Reporter: Marek Novotny Assignee: Carlo de Wolf Seam jee5 booking example at http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2/examples/... can't get connection from java:/DefaultDS due to wrong setup of CONNECTION_PROVIDER in org.hibernate.ejb.Ejb3Configuration. This is caused by jtaDataSource = null in org.jboss.jpa.impl.deployment.PersistenceUnitInfoImpl.jtaDataSource. >From quick debugging - PersistentUnitMetaData has got these properties: PersistenceUnitMetaData(a)c6d08c4{provider=org.hibernate.ejb.HibernatePersistence, jta-data-source=java:/DefaultDS, non-jta-data-source=null, non-jta-data-source=null, excludeUnlistedClasses=false, properties={hibernate.cache.provider_class=org.hibernate.cache.HashtableCacheProvider, hibernate.hbm2ddl.auto=create-drop, hibernate.transaction.flush_before_completion=true, hibernate.show_sql=true, hibernate.dialect=org.hibernate.dialect.HSQLDialect}, name=bookingDatabase, transactionType=null} but when jtaDataSource should be set, it is not found in a context and it is set null value to org.jboss.jpa.impl.deployment.PersistenceUnitInfoImpl.jtaDataSource : if (metaData.getJtaDataSource() != null) { this.setJtaDataSource((javax.sql.DataSource) ctx.lookup(metaData.getJtaDataSource())); } -- 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
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 January 2011