[JBoss JIRA] Created: (JBPM-2106) jpdl 3 feature coverage
by Tom Baeyens (JIRA)
jpdl 3 feature coverage
-----------------------
Key: JBPM-2106
URL: https://jira.jboss.org/jira/browse/JBPM-2106
Project: JBoss jBPM
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Fix For: jBPM 4.0.0.GA
this issue lists features that were not prioritized in jpdl 4. for each feature, we should evaluate whether we actually want to include this to support migration. and if we do, whether this should be part of the user guide or of the developers guide (deprecate it)
* Advanced task properties:
<task subtask-synchronization="first, last, unsynchronized, never">
<task blocking="true">
* Assignment expression language
* Config types for user code
--
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 months
[JBoss JIRA] Created: (JBPM-1934) Console API integration: Failed to retrieve token
by Heiko Braun (JIRA)
Console API integration: Failed to retrieve token
-------------------------------------------------
Key: JBPM-1934
URL: https://jira.jboss.org/jira/browse/JBPM-1934
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: GWT Console 1.0.0 Beta3
Caused by: java.lang.IllegalStateException: Cannot obtain associated token
at org.jbpm.integration.spec.task.TaskInstanceImpl.getCorrelationKey(TaskInstanceImpl.java:144)
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:585)
at org.jbpm.integration.spec.runtime.InvocationProxy.invoke(InvocationProxy.java:107)
at $Proxy101.getCorrelationKey(Unknown Source)
This does slip through the test coverage.
--
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 months
[JBoss JIRA] Created: (JBPM-1948) Report server config doesn't work across databases
by Heiko Braun (JIRA)
Report server config doesn't work across databases
--------------------------------------------------
Key: JBPM-1948
URL: https://jira.jboss.org/jira/browse/JBPM-1948
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: GWT Console 1.0.0 Beta3
"If your report design contains a JDBC data source defined with both JDBC Driver URL and JNDI name, then JNDI service will be used first and JDBC driver will be used as fallback. The username and password properties, if specified, are used in both cases. "
Even when using the datasource, BIRT reconfigures the credentials. That means you cannot simply point the JBPM datasource to a different database, which uses other credentials.
--
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 months