March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-705) Provide monitoring for standalone applications

by Ryan Campbell (JIRA)

Provide monitoring for standalone applications ---------------------------------------------- Key: JBPM-705 URL: http://jira.jboss.com/jira/browse/JBPM-705 Project: JBoss jBPM Issue Type: Feature Request Reporter: Ryan Campbell Assigned To: Tom Baeyens Fix For: jBPM 3.2 Provide jmx interfaces for monitor processes not in a webapp. Or can you point the monitoring webapp at a jBPM datastore? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (HIBERNATE-58) Support for full-text search

by Yves Martin (JIRA)

Support for full-text search ---------------------------- Key: HIBERNATE-58 URL: http://jira.jboss.com/jira/browse/HIBERNATE-58 Project: Hibernate Issue Type: Feature Request Environment: MySQL Reporter: Yves Martin Assigned To: Steve Ebersole Priority: Minor MySQL databases support full text search with specific indexes. Is it possible to support the match operator and full text indexes for MySQL ? I may extend the MySQL dialect to support it if there is no technical limitation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-607) add description-subelement to schema of all major elements

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-607?page=all ] Tom Baeyens closed JBPM-607. ---------------------------- Resolution: Done see DescriptionDbTest > add description-subelement to schema of all major elements > ---------------------------------------------------------- > > Key: JBPM-607 > URL: http://jira.jboss.com/jira/browse/JBPM-607 > Project: JBoss jBPM > Issue Type: Sub-task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-742) Reimplement JbpmThreadsServlet as a ServletContextListener

by Alejandro Guizar (JIRA)

Reimplement JbpmThreadsServlet as a ServletContextListener ---------------------------------------------------------- Key: JBPM-742 URL: http://jira.jboss.com/jira/browse/JBPM-742 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.1 Reporter: Alejandro Guizar ServletContextListeners are a viable alternative to servlets for management of the jBPM scheduler/command threads. From the Servlet 2.4 spec, section 10.2: >>> Servlet event listeners support event notifications for state changes in the ServletContext, HttpSession and ServletRequest objects. Servlet context listeners are used to **manage resources** or state held at a JVM level for the application. <<< Their intent definitely seems to match our purposes. Further below: >>> There may be multiple listener classes listening to each event type. <<< We could have separate listeners for the scheduler and command executor so that applications may remove either of them in case the related service is not used. Section 10.2.2 provides an example. When the application starts up, the listener creates a connection to the database and stores it in the servlet context. Servlets access the connection from the context as needed. When the application shuts down, the listener closes the connection. Our listener could start the thread and store it in the servlet context, then stop it using the mechanisms provided by JBPM-741. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

4
12
0 / 0

[JBoss JIRA] Closed: (JBPM-540) Standard VariableResolverImpl should search for transient variables

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-540?page=all ] Tom Baeyens closed JBPM-540. ---------------------------- Resolution: Done > Standard VariableResolverImpl should search for transient variables > ------------------------------------------------------------------- > > Key: JBPM-540 > URL: http://jira.jboss.com/jira/browse/JBPM-540 > Project: JBoss jBPM > Issue Type: Feature Request > Reporter: James Depoorter > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2 > > > The jbpm implementation of the VariableResolver should also try to resolve transient variables. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-392) cancel taskInstances, messages and timers when process instance ends

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-392?page=all ] Tom Baeyens updated JBPM-392: ----------------------------- Fix Version/s: jBPM jPDL 3.2.1 (was: jBPM jPDL 3.2) > cancel taskInstances, messages and timers when process instance ends > -------------------------------------------------------------------- > > Key: JBPM-392 > URL: http://jira.jboss.com/jira/browse/JBPM-392 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.1 > > > when a process instance ends, we should have an option to remove or cancel all open taskInstance, messages and timers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-653) make the process parent classloader configurable

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-653?page=all ] Tom Baeyens updated JBPM-653: ----------------------------- Fix Version/s: jBPM jPDL 3.2.1 (was: jBPM jPDL 3.2) > make the process parent classloader configurable > ------------------------------------------------ > > Key: JBPM-653 > URL: http://jira.jboss.com/jira/browse/JBPM-653 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.1 > > > now, always the jBPM classloader is taken as a parent for the process classloaders. this should be made configurable. at least one other possibility should be to configure the context classloader. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-811) sorted task lists

by Gavin King (JIRA)

sorted task lists ----------------- Key: JBPM-811 URL: http://jira.jboss.com/jira/browse/JBPM-811 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Gavin King Assigned To: Tom Baeyens JbpmContext.getTaskList() should allow sorting and filtering of the task list, by either priority, creation date, or type Something like Hibernate Criteria API makes sense: ctx.createTaskLiskQuery().orderByPriority().filterByType("approve document").getTaskList() Same facility should also exist for querying process definitions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

3
3
0 / 0

[JBoss JIRA] Updated: (JBPM-511) use service directly

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-511?page=all ] Tom Baeyens updated JBPM-511: ----------------------------- Fix Version/s: jBPM 3.3 (was: jBPM jPDL 3.2) postponed > use service directly > -------------------- > > Key: JBPM-511 > URL: http://jira.jboss.com/jira/browse/JBPM-511 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Trivial > Fix For: jBPM 3.3 > > > services are now used indirectly. meaning that the non-persisted data members in the instances are used to store service operations. during the jbpmContext.save, all this data is interpreted and the services are invoked. > most of those service invocations should be done directly. this implies that a large part of the POJO test suite will have to be revised to accomodate this. probably a common base class will be sufficient. > regards, tom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-820) free choice of initial node type

by Tom Baeyens (JIRA)

free choice of initial node type -------------------------------- Key: JBPM-820 URL: http://jira.jboss.com/jira/browse/JBPM-820 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM 3.2 currently, you are forced to have a start-state to mark the initial node in your process-definition. i think it is a good idea to expand this so that any type of node could be the first node in the process. we already did this with SEAM. IMO, the most elegant way to achieve this is by adding an optional attribute 'initial' to the process-definition. the value must be a node name. when the initial node is specified as an attribute, the process should not have a start-state. the result is that with the initial attribute on the process-definition, any node type can be used as the start state. we would have to update the core engine new ProcessInstance(processDefinition) method. after creating the process instance and positioning the token in the initial node, the initial node has to be executed. now that is not the case. the initial node is not executed. because the start-state now has an empty implementation, this will be backwards compatible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

3
2
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 March 2007