[JBoss JIRA] (RTGOV-249) Missing values from BPM activity events
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-249?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-249:
-----------------------------
Description:
When reporting activity events from the BPM component within SwitchYard:
ProcessCompleted event currently does not record the status of the process instance. This is available by navigating to the process instance.
The ProcessVariableSet component is missing the variable type.
was:
ProcessCompleted event currently does not record the status of the process instance. This is available by navigating to the process instance.
The ProcessVariableSet component is missing the variable type.
> Missing values from BPM activity events
> ---------------------------------------
>
> Key: RTGOV-249
> URL: https://issues.jboss.org/browse/RTGOV-249
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.1.0.Final
>
>
> When reporting activity events from the BPM component within SwitchYard:
> ProcessCompleted event currently does not record the status of the process instance. This is available by navigating to the process instance.
> The ProcessVariableSet component is missing the variable type.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (RTGOV-249) Missing values from BPM activity events
by Gary Brown (JIRA)
Gary Brown created RTGOV-249:
--------------------------------
Summary: Missing values from BPM activity events
Key: RTGOV-249
URL: https://issues.jboss.org/browse/RTGOV-249
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.1.0.Final
ProcessCompleted event currently does not record the status of the process instance. This is available by navigating to the process instance.
The ProcessVariableSet component is missing the variable type.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (SRAMP-197) Auditing: re-implement *not* using JCR observer pattern
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-197?page=com.atlassian.jira.plugin.... ]
Work on SRAMP-197 started by Eric Wittmann.
> Auditing: re-implement *not* using JCR observer pattern
> -------------------------------------------------------
>
> Key: SRAMP-197
> URL: https://issues.jboss.org/browse/SRAMP-197
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: 0.2.0 - Security & S-RAMP-1.0
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> Re-write the core auditing to no longer use the JCR observer pattern. The JCR observer pattern introduces a number of challenges, including:
> 1) async processing of auditing information. this is problematic in a number of ways, but most importantly is that data may be lost due to slower processing of the auditing information than the information on the artifact itself. Since the JCR observation events don't contain before and/or after values for changes, we have to go after the data directly. If changes happen quickly (before the observer has a crack at it) then data may be lost.
> 2) multi-phase processing of artifact adds/updates in the jcrpersistence impl
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months