May 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-59) Enable security on REST services

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/RTGOV-59?page=com.atlassian.jira.plugin.s... ] Work on RTGOV-59 started by Eric Wittmann. > Enable security on REST services > -------------------------------- > > Key: RTGOV-59 > URL: https://issues.jboss.org/browse/RTGOV-59 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Eric Wittmann > Priority: Critical > Fix For: 1.0.0.Final > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-33) jBPM activity collector

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-33?page=com.atlassian.jira.plugin.s... ] Gary Brown reassigned RTGOV-33: ------------------------------- Assignee: Gary Brown (was: Kevin Conner) > jBPM activity collector > ----------------------- > > Key: RTGOV-33 > URL: https://issues.jboss.org/browse/RTGOV-33 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.Final > > > Create an ActivityCollector to obtain information associated with the execution of a BPMN2 process. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-150) Obtain service availability information from external management systems

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-150?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-150: ----------------------------- Priority: Major (was: Critical) > Obtain service availability information from external management systems > ------------------------------------------------------------------------ > > Key: RTGOV-150 > URL: https://issues.jboss.org/browse/RTGOV-150 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.Final > > > For organizations that wish to perform more complex analysis of service availability, potentially in combination with other service related information (e.g. performance), it would be useful to have availability information supplied as events. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-203) Add context 'type' combo to call trace gadget

by Gary Brown (JIRA)

Gary Brown created RTGOV-203: -------------------------------- Summary: Add context 'type' combo to call trace gadget Key: RTGOV-203 URL: https://issues.jboss.org/browse/RTGOV-203 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Priority: Minor Fix For: 1.0.0.Final Add context 'type' combo box to the call trace gadget. Currently it only supplies the value, and therefore the type defaults to 'conversation', which will generally be the one required. However conversation ids may not always be provided, so users may wish to search for a trace based on a process id etc. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-202) Call trace REST service support retrieving call trace based on Context

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-202?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-202. ------------------------------ Resolution: Done > Call trace REST service support retrieving call trace based on Context > ---------------------------------------------------------------------- > > Key: RTGOV-202 > URL: https://issues.jboss.org/browse/RTGOV-202 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.Final > > > Currently using a GET with query parameter for an identifier, which assumes clients will only be interested in call traces based on conversation ids. > However some traces may not have conversation ids, so will need to use other types of context - so need the REST service and gadget to allow other types of context to be specified. > Could use a POST with the Context supplied, but probably more appropriate to still use a GET, but specify the context type and value as separate query parameters? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-202) Call trace REST service support retrieving call trace based on Context

by Gary Brown (JIRA)

Gary Brown created RTGOV-202: -------------------------------- Summary: Call trace REST service support retrieving call trace based on Context Key: RTGOV-202 URL: https://issues.jboss.org/browse/RTGOV-202 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.Final Currently using a GET with query parameter for an identifier, which assumes clients will only be interested in call traces based on conversation ids. However some traces may not have conversation ids, so will need to use other types of context - so need the REST service and gadget to allow other types of context to be specified. Could use a POST with the Context supplied, but probably more appropriate to still use a GET, but specify the context type and value as separate query parameters? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-200) Call trace builder needs to take timeframe into account when using link context

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-200?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-200. ------------------------------ Resolution: Done > Call trace builder needs to take timeframe into account when using link context > ------------------------------------------------------------------------------- > > Key: RTGOV-200 > URL: https://issues.jboss.org/browse/RTGOV-200 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.Final > > > Use a specified timeframe to locate linked activity events. > Only use the link if considered the 'source', which is where the timeframe has been specified. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-201) Extend the information processor config validation to include the evaluator implementations

by Gary Brown (JIRA)

Gary Brown created RTGOV-201: -------------------------------- Summary: Extend the information processor config validation to include the evaluator implementations Key: RTGOV-201 URL: https://issues.jboss.org/browse/RTGOV-201 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.1 Currently only validates the higher level information. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-200) Call trace builder needs to take timeframe into account when using link context

by Gary Brown (JIRA)

Gary Brown created RTGOV-200: -------------------------------- Summary: Call trace builder needs to take timeframe into account when using link context Key: RTGOV-200 URL: https://issues.jboss.org/browse/RTGOV-200 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.Final Use a specified timeframe to locate linked activity events. Only use the link if considered the 'source', which is where the timeframe has been specified. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-199) Determine if epn, acs or ip validation errors should result in deployment failure

by Gary Brown (JIRA)

Gary Brown created RTGOV-199: -------------------------------- Summary: Determine if epn, acs or ip validation errors should result in deployment failure Key: RTGOV-199 URL: https://issues.jboss.org/browse/RTGOV-199 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.Final If so, then need to throw exception back to AS deployer. -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2013