[JBoss JIRA] (SRAMP-130) cannot add url in taskform
by Kurt Stam (JIRA)
Kurt Stam created SRAMP-130:
-------------------------------
Summary: cannot add url in taskform
Key: SRAMP-130
URL: https://issues.jboss.org/browse/SRAMP-130
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Kurt Stam
Assignee: Kurt Stam
Fix For: Milestone 3 (Workflow and Relationships)
The BPMN taskform rejects URLs with dashes '-', as well as dashes in the uuid. This is a problem.
--
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
12 years
[JBoss JIRA] (SRAMP-129) cleanup stacktraces in the build when running tests
by Kurt Stam (JIRA)
Kurt Stam created SRAMP-129:
-------------------------------
Summary: cleanup stacktraces in the build when running tests
Key: SRAMP-129
URL: https://issues.jboss.org/browse/SRAMP-129
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Kurt Stam
Assignee: Kurt Stam
Fix For: Milestone 3 (Workflow and Relationships)
There are a few stacktraces when running the test. We should change our code to make sure we don't show stack traces if there is no true exception.
--
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
12 years
[JBoss JIRA] (SRAMP-128) remove the -i flag from the client tool
by Kurt Stam (JIRA)
Kurt Stam created SRAMP-128:
-------------------------------
Summary: remove the -i flag from the client tool
Key: SRAMP-128
URL: https://issues.jboss.org/browse/SRAMP-128
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Kurt Stam
Assignee: Kurt Stam
Fix For: Milestone 3 (Workflow and Relationships)
The sramp.sh does no longer support the brms command, so we might as well remove the -i option, as this would be the default now.
--
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
12 years
[JBoss JIRA] (BAM-111) Graphical representation of the current status of a conversation instance
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-111?page=com.atlassian.jira.plugin.sy... ]
Gary Brown reassigned BAM-111:
------------------------------
Assignee: Gary Brown (was: Jeff Yu)
> Graphical representation of the current status of a conversation instance
> -------------------------------------------------------------------------
>
> Key: BAM-111
> URL: https://issues.jboss.org/browse/BAM-111
> Project: Business Activity Monitoring
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M4
>
> Attachments: CommsDiagStyle.gliffy, CommsDiagStyle.png, FlowDiagStyle.gliffy, FlowDiagStyle.png
>
>
> Initially the Savara web console will display a conversation instance as a table of activity events.
> This task will provide a graphical status view of the conversation instance, showing the execution path taken, and if still active, where the instance is currently in its execution.
> Although BPMN2 is the principle choreography representation that will be used, not all choreographies will be defined with a BPMN2 choreography - so we need to consider how this graphical representation will be defined.
> One approach may be to derive a BPMN2 like representation, based on the global Scribble protocol definition, as this will be the canonical representation used for all conversations being monitored. It would also be simpler than the BPMN2 original - just depends whether users would expect to see if based on the original representation.
> The other approach would be to only support graphical representation where a BPMN2 choreography has been defined, and provide a faithful graphical representation of the original choreography.
> To be decided ....
> However the same approach could be used as with RiftSaw - generate SVG images as snapshots of the state, and if the state changes while displaying, then just generate a new image.
--
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
12 years
[JBoss JIRA] (BAM-111) Graphical representation of the current status of a conversation instance
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-111?page=com.atlassian.jira.plugin.sy... ]
Gary Brown moved SAVARA-187 to BAM-111:
---------------------------------------
Project: Business Activity Monitoring (was: Savara)
Key: BAM-111 (was: SAVARA-187)
Component/s: (was: Tooling)
Fix Version/s: 1.0.0.M4
(was: 2.1.0.M3)
> Graphical representation of the current status of a conversation instance
> -------------------------------------------------------------------------
>
> Key: BAM-111
> URL: https://issues.jboss.org/browse/BAM-111
> Project: Business Activity Monitoring
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Jeff Yu
> Fix For: 1.0.0.M4
>
> Attachments: CommsDiagStyle.gliffy, CommsDiagStyle.png, FlowDiagStyle.gliffy, FlowDiagStyle.png
>
>
> Initially the Savara web console will display a conversation instance as a table of activity events.
> This task will provide a graphical status view of the conversation instance, showing the execution path taken, and if still active, where the instance is currently in its execution.
> Although BPMN2 is the principle choreography representation that will be used, not all choreographies will be defined with a BPMN2 choreography - so we need to consider how this graphical representation will be defined.
> One approach may be to derive a BPMN2 like representation, based on the global Scribble protocol definition, as this will be the canonical representation used for all conversations being monitored. It would also be simpler than the BPMN2 original - just depends whether users would expect to see if based on the original representation.
> The other approach would be to only support graphical representation where a BPMN2 choreography has been defined, and provide a faithful graphical representation of the original choreography.
> To be decided ....
> However the same approach could be used as with RiftSaw - generate SVG images as snapshots of the state, and if the state changes while displaying, then just generate a new image.
--
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
12 years
[JBoss JIRA] (BAM-110) Activity event generator
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-110?page=com.atlassian.jira.plugin.sy... ]
Gary Brown moved SAVARA-220 to BAM-110:
---------------------------------------
Project: Business Activity Monitoring (was: Savara)
Key: BAM-110 (was: SAVARA-220)
Fix Version/s: 1.0.0.M4
(was: 2.1.0.M3)
> Activity event generator
> ------------------------
>
> Key: BAM-110
> URL: https://issues.jboss.org/browse/BAM-110
> Project: Business Activity Monitoring
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M4
>
>
> Create an activity event generator that will be driven by a scribble protocol derived from a choreography (WS-CDL or BPMN2).
> The protocol will define the alternate paths that can taken, representing valid executions of the business protocol. Example messages will need to be defined for each interaction, to represent templates for the messages that should be passed. These templates will include tags associated with values that should be replaced.
> One special tag will represent the conversation id that would be used to correlate the events. Although consideration should be given regarding how to support sub-conversations.
> Other tag fields will have values defined in supporting files, and these values will be randomly selected for each instance of a message that is generated. These fields will eventually be used in more advanced queries.
> Need to determine how to generate erronous business transactions, when required. The generator should be configured with a 'factor' that indicates how often an erronous transaction should be generated. Errors could be produced by simply sending a random message, normally associated with the business transaction, but not the type that is expected next (or for simplicity, just send the initial message again).
> Eventually, when SLAs and assertions are defined in the model, we should consider generating nessages/transactions that satisfy and violate those policies.
--
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
12 years
[JBoss JIRA] (BAM-109) Service activity correlation to global model (choreography)
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-109?page=com.atlassian.jira.plugin.sy... ]
Gary Brown moved SAVARA-105 to BAM-109:
---------------------------------------
Project: Business Activity Monitoring (was: Savara)
Key: BAM-109 (was: SAVARA-105)
Component/s: (was: Validator)
Fix Version/s: 1.0.0.M4
(was: 2.1.0.M3)
> Service activity correlation to global model (choreography)
> -----------------------------------------------------------
>
> Key: BAM-109
> URL: https://issues.jboss.org/browse/BAM-109
> Project: Business Activity Monitoring
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M4
>
>
> Based on replayed (or simulated) service activity, correlate this information back to the global model (choreography). This can be used to display a representation of the business transaction in terms of its current position in the global context.
--
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
12 years