user provided hibernate session
-------------------------------
Key: JBPM-2038
URL: https://jira.jboss.org/jira/browse/JBPM-2038
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Fix For: jBPM 4.0.0.Beta1
make sure that jbpm can work with a hibernate session or a jdbc connection that is provided by the client.
--
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
add extensibility to jpdl schema
--------------------------------
Key: JBPM-2166
URL: https://jira.jboss.org/jira/browse/JBPM-2166
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Fix For: jBPM 4.0.0.CR1
Add activity pluggability. (add the proper any's and anyAttributes)
--
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
review installation of contexts in environment
----------------------------------------------
Key: JBPM-2401
URL: https://jira.jboss.org/jira/browse/JBPM-2401
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.1
currently the execution context is set in the performAtomicOperation, and the task context is set in only in the MailListener.
that should be revisited.
--
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
change swimlane assignee memory
-------------------------------
Key: JBPM-2341
URL: https://jira.jboss.org/jira/browse/JBPM-2341
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.1
now a swimlane will remember the actual assignee and use that for subsequent tasks.
the default should be switched to *not* remembering the assignee. and reassign every task from scratch. e.g. to the group.
an attribute should be introduced to activate remembering if the assignee that took on a task that was assigned to a group.
--
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
consider deprecating language attributes that are related to expr attributes
----------------------------------------------------------------------------
Key: JBPM-2686
URL: https://jira.jboss.org/jira/browse/JBPM-2686
Project: jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.3
investigate if language still makes sense if we switch to unified el in the cdi context.
i expect that language then doesn't make sense.
so we should deprecate those attributes now so that in the next release we can remove them.
--
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
put non xa jms resources in transaction context
-----------------------------------------------
Key: JBPM-2705
URL: https://jira.jboss.org/jira/browse/JBPM-2705
Project: jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.4
--
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
refactor expressions from jsf 223 to el for seam integration
------------------------------------------------------------
Key: JBPM-2653
URL: https://jira.jboss.org/jira/browse/JBPM-2653
Project: jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.3
Notes from the meeting with SEAM team at Devoxx, nov 2009:
expression resolving needs to be switched from jsr 223 to unified EL
scripts should remain with jsr 223
we need to make the ExpressionFactory lookup pluggable. in Seam context it needs to be fetched from JNDI.
we can use the el-api from Sun. @see sun glassfish maven repo
http://download.java.net/maven/2/javax/el/el-api/
CDI -> planned for JBoss 6 (5.2)
!!! jBPM integration is with CDI, not with Seam
http://docs.jboss.org/cdi/http://repo2.maven.org/maven2/javax/enterprise/cdi-api/1.0/
--
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
add test chapter to userguid
----------------------------
Key: JBPM-2700
URL: https://jira.jboss.org/jira/browse/JBPM-2700
Project: jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.4
discuss testing in full.
make clear which part of the test apis are part of the public api and which are part of the private api.
clearly document diff between JbpmTestCase and AbstractTransactionSpringJbpmTestCase and add pointer to our spring docs where that is mentioned.
--
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
clean up libs
-------------
Key: JBPM-2620
URL: https://jira.jboss.org/jira/browse/JBPM-2620
Project: jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Priority: Optional
Fix For: jBPM 4.3
1) identify the minimal set of libs needed for jbpm runtime execution and make sure the rest of the libs is removedfrom the distribution
2) add the version to the filenames (as defined in the mvn dependencies) of the libraries that we distribute
--
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