February 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-349) Integration tests for switchyard services provider

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-349?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-349: ----------------------------- Summary: Integration tests for switchyard services provider (was: Integration tests for situations provider and switchyard services provider) > Integration tests for switchyard services provider > -------------------------------------------------- > > Key: RTGOV-349 > URL: https://issues.jboss.org/browse/RTGOV-349 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Setup an integration test structure, using arquillian, to test the rtgov situations provider and the switchyard services provider. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-350) JMX based switchyard service provider in rtgov UI

by Gary Brown (JIRA)

Gary Brown created RTGOV-350: -------------------------------- Summary: JMX based switchyard service provider in rtgov UI Key: RTGOV-350 URL: https://issues.jboss.org/browse/RTGOV-350 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Current DMR approach will not be portable across switchyard deployments (e.g. EAP and Fuse), so need to switch to JMX. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-333) Enable user to filter situations based on allocation status

by Michael Clay (JIRA)

[ https://issues.jboss.org/browse/RTGOV-333?page=com.atlassian.jira.plugin.... ] Work on RTGOV-333 stopped by Michael Clay. > Enable user to filter situations based on allocation status > ----------------------------------------------------------- > > Key: RTGOV-333 > URL: https://issues.jboss.org/browse/RTGOV-333 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > The list of situations shown on the main page can be filtered using criteria on the left panel. > Add a new criteria to enable the list of situations to be filtered on the allocation status of: All, Assigned to me, Unassigned. > The server side should be updated to implement this new filtering criteria. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-330) Allow situations to be allocated/assigned to individual

by Michael Clay (JIRA)

[ https://issues.jboss.org/browse/RTGOV-330?page=com.atlassian.jira.plugin.... ] Michael Clay reassigned RTGOV-330: ---------------------------------- Assignee: Michael Clay (was: Gary Brown) > Allow situations to be allocated/assigned to individual > ------------------------------------------------------- > > Key: RTGOV-330 > URL: https://issues.jboss.org/browse/RTGOV-330 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Allow a situation to be assigned to a user. To avoid maintaining list of users (for now), we will use a ‘take’ approach, so the currently logged in user can ‘take’ responsibility for a situation (if not already associated with another user). This will result in their username being associated with a property on the situation, and the situation being recorded back to the db. > Once the user is responsible for the situation, they should have the ability to set its status. Current status values will be Unresolved (default value upon a situation being assigned) and Resolved. > To avoid the scenario where a situation remains associated with a user while no action is being taken, it should be possible for a more privileged user to be able to 'take' it from another assigned user. This may only happen if this user has a 'management' role - to be discussed further. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-333) Enable user to filter situations based on allocation status

by Michael Clay (JIRA)

[ https://issues.jboss.org/browse/RTGOV-333?page=com.atlassian.jira.plugin.... ] Work on RTGOV-333 started by Michael Clay. > Enable user to filter situations based on allocation status > ----------------------------------------------------------- > > Key: RTGOV-333 > URL: https://issues.jboss.org/browse/RTGOV-333 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > The list of situations shown on the main page can be filtered using criteria on the left panel. > Add a new criteria to enable the list of situations to be filtered on the allocation status of: All, Assigned to me, Unassigned. > The server side should be updated to implement this new filtering criteria. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-331) Enable user to filter situations based on their resolution status

by Michael Clay (JIRA)

[ https://issues.jboss.org/browse/RTGOV-331?page=com.atlassian.jira.plugin.... ] Work on RTGOV-331 started by Michael Clay. > Enable user to filter situations based on their resolution status > ----------------------------------------------------------------- > > Key: RTGOV-331 > URL: https://issues.jboss.org/browse/RTGOV-331 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > On the main situations page, where it presents a list of situations, there is a filter panel on the left. In additional to the current filter criteria, add the ability to select the specific status value of interest, or All (default value). > Update the server side to use the filter value in its evaluation of the list of situations to be returned. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-331) Enable user to filter situations based on their resolution status

by Michael Clay (JIRA)

[ https://issues.jboss.org/browse/RTGOV-331?page=com.atlassian.jira.plugin.... ] Michael Clay resolved RTGOV-331. -------------------------------- Resolution: Done sent pull-request for RTGOV-331 > Enable user to filter situations based on their resolution status > ----------------------------------------------------------------- > > Key: RTGOV-331 > URL: https://issues.jboss.org/browse/RTGOV-331 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > On the main situations page, where it presents a list of situations, there is a filter panel on the left. In additional to the current filter criteria, add the ability to select the specific status value of interest, or All (default value). > Update the server side to use the filter value in its evaluation of the list of situations to be returned. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-231) SwitchYard XML deriver missing 'requires' attribute on component services

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-231?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-231: ----------------------------------------------- Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 996943|https://bugzilla.redhat.com/show_bug.cgi?id=996943] from VERIFIED to CLOSED > SwitchYard XML deriver missing 'requires' attribute on component services > ------------------------------------------------------------------------- > > Key: SRAMP-231 > URL: https://issues.jboss.org/browse/SRAMP-231 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > This SwitchYard deriver is just exploring implementation.bean tag for the 'requires' attribute but security policies are defined in service tag[0] so security/custom policies are just ignored. > [0] https://github.com/jboss-switchyard/quickstarts/blob/master/demos/policy-... -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-311) Switchyard Exchange Validator needs to change to use ExchangeInterceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-311?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-311: ----------------------------------------------- Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 1026698|https://bugzilla.redhat.com/show_bug.cgi?id=1026698] from VERIFIED to CLOSED > Switchyard Exchange Validator needs to change to use ExchangeInterceptor > ------------------------------------------------------------------------ > > Key: RTGOV-311 > URL: https://issues.jboss.org/browse/RTGOV-311 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the switchyard exchange validator mechanism uses the Auditor mechanism to detect and analyse the exchanges. However this mechanism directly operates on the camel exchange, retrieving the security context as a property. > The problem with this is that the security context could be sealed, and the only way to deal with this requires the SecurityDomain, which is not accessible from the auditor. > Following discussion with Keith, it appears that the newer ExchangeInterceptors mechanism would be more appropriate - it is higher level abstraction that operates on switchyard exchanges, and therefore will be possible to use the SecurityContextManager to deal with whether or not the SecurityContext is sealed. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-244) Kie and Teiid expanders not working from the S-RAMP-UI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-244?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-244: ----------------------------------------------- Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 1015251|https://bugzilla.redhat.com/show_bug.cgi?id=1015251] from VERIFIED to CLOSED > Kie and Teiid expanders not working from the S-RAMP-UI > ------------------------------------------------------ > > Key: SRAMP-244 > URL: https://issues.jboss.org/browse/SRAMP-244 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > > These integrations are missing dependencies that need to be added so they can discovered by the servicelocator. -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues February 2014