January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2714) Drools Persistence Should Not Rely on an Existing Named Query in "META-INF/orm.xml"

by Anatoly Polinsky (JIRA)

Drools Persistence Should Not Rely on an Existing Named Query in "META-INF/orm.xml" ----------------------------------------------------------------------------------- Key: JBRULES-2714 URL: https://jira.jboss.org/browse/JBRULES-2714 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor There is a named query "ProcessInstancesWaitingForEvent" that lives in a drools persistence jar under "META-INF/orm.xml". The problem is not even that the query is wrong ( org.hibernate.QueryException: cannot dereference scalar collection element.. ), but that majority of applications that sit on top of JPA rely on its own mappings, and hence this query either: 1. Lost, since the custom "persistence.xml" will redefine the path to other mapping files 2. Will result in "Duplicate query mapping" exception if defined in a custom mapping file ( http://opensource.atlassian.com/projects/hibernate/browse/HHH-4152 ) Would be more logical not to depend that everyone knows to look inside "drools persistence jar", and to have an extensive documentation explaining "ProcessInstancesWaitingForEvent". It maybe hardcoded through @NamedQuery or just be available as an OPTIONAL file to use by Drools clients: e.g. "<mapping-file>META-INF/persistence/mapping/drools/drools-named-queries.xml</mapping-file>" ( and again: documented.. ) /Anatoly -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2798) Allow extraction / injection of constraints in processes

by Kris Verlaenen (JIRA)

Allow extraction / injection of constraints in processes -------------------------------------------------------- Key: JBRULES-2798 URL: https://jira.jboss.org/browse/JBRULES-2798 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kris Verlaenen Assignee: Kris Verlaenen -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2732) ProcessInstancesWaitingForEvent Query is Extremely Inefficient Should Be Simplified

by Anatoly Polinsky (JIRA)

ProcessInstancesWaitingForEvent Query is Extremely Inefficient Should Be Simplified ----------------------------------------------------------------------------------- Key: JBRULES-2732 URL: https://jira.jboss.org/browse/JBRULES-2732 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.1.FINAL Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor "ProcessInstancesWaitingForEvent" query that is used after each process / subprocess ends is extremely inefficient, and since there is no way to force an INDEX without being coupled with JPA provider, this query execution time increase exponentially as the number of processes goes up. Currently with only 20000 processes, the query takes 18(!!!) seconds to execute: <named-query name="ProcessInstancesWaitingForEvent"> <query> SELECT processInstanceInfo.processInstanceId FROM ProcessInstanceInfo processInstanceInfo WHERE :type in elements ( processInstanceInfo.eventTypes ) </query> </named-query> It is inefficient not only because there is no INDEX enforced, but because it goes into the sub query for no good reason. The better/correct query is: SELECT processInstanceInfo.processInstanceId FROM ProcessInstanceInfo processInstanceInfo, EventTypes eventTypes WHERE eventTypes.element = :type AND processInstanceInfo.processInstanceId = eventTypes.processInstanceId In order to get to this "better" query, since it is a JPA one, an EventType/s entity should be created ( it does not currently exist in 5.1.1 ). /Anatoly -- 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

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2827) Migrate Drools Flow to jBPM5

by Kris Verlaenen (JIRA)

Migrate Drools Flow to jBPM5 ---------------------------- Key: JBRULES-2827 URL: https://issues.jboss.org/browse/JBRULES-2827 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kris Verlaenen Assignee: Kris Verlaenen -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[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

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