October 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-254) S-RAMP client should have method to release the HTTP connection

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-254?page=com.atlassian.jira.plugin.... ] Work on SRAMP-254 started by Eric Wittmann. > S-RAMP client should have method to release the HTTP connection > --------------------------------------------------------------- > > Key: SRAMP-254 > URL: https://issues.jboss.org/browse/SRAMP-254 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > The S-RAMP client wraps the RestEASY client. The RestEASY client has a response.releaseConnection method which we don't have. I'm worried we are leaking connections. We should make sure we update our code that uses the client so it releases the connection (in DTGov too). -- 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
0
0 / 0

[JBoss JIRA] (SRAMP-255) Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-255?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-255. ------------------------------- > Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps > ------------------------------------------------------------------------------------------------ > > Key: SRAMP-255 > URL: https://issues.jboss.org/browse/SRAMP-255 > 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 is actually an EAP bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1016591 > This JIRA issue tracks the workaround used in Overlord. The workaround is only necessary until the EAP bug is fixed. -- 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
0
0 / 0

[JBoss JIRA] (SRAMP-255) Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-255?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-255. --------------------------------- Resolution: Done > Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps > ------------------------------------------------------------------------------------------------ > > Key: SRAMP-255 > URL: https://issues.jboss.org/browse/SRAMP-255 > 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 is actually an EAP bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1016591 > This JIRA issue tracks the workaround used in Overlord. The workaround is only necessary until the EAP bug is fixed. -- 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
0
0 / 0

[JBoss JIRA] (SRAMP-251) Improve XSLT in overlord commons installer

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-251?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-251. --------------------------------- Resolution: Done > Improve XSLT in overlord commons installer > ------------------------------------------ > > Key: SRAMP-251 > URL: https://issues.jboss.org/browse/SRAMP-251 > 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 > > > The current overlord commons installer XSLT used to add security domains to jboss eap/wildfly has an ambiguous element declaration. When adding the security domain, the xslt has this: > {code} > <security-domains> > <security-domain /> > </security-domains> > {code} > Because the XSLT doesn't declare a default namespace, this is problematic depending on the processor used. Instead, the XSLT should be explicit about the QNames used in any element it creates. > Note that the XSLT is currently designed to work with both EAP and Wildfly, which have different namespaces for the element being created. So we'll likely need multiple templates for multiple versions of the "as" namespace. -- 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
0
0 / 0

[JBoss JIRA] (SRAMP-251) Improve XSLT in overlord commons installer

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-251?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-251. ------------------------------- > Improve XSLT in overlord commons installer > ------------------------------------------ > > Key: SRAMP-251 > URL: https://issues.jboss.org/browse/SRAMP-251 > 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 > > > The current overlord commons installer XSLT used to add security domains to jboss eap/wildfly has an ambiguous element declaration. When adding the security domain, the xslt has this: > {code} > <security-domains> > <security-domain /> > </security-domains> > {code} > Because the XSLT doesn't declare a default namespace, this is problematic depending on the processor used. Instead, the XSLT should be explicit about the QNames used in any element it creates. > Note that the XSLT is currently designed to work with both EAP and Wildfly, which have different namespaces for the element being created. So we'll likely need multiple templates for multiple versions of the "as" namespace. -- 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
0
0 / 0

[JBoss JIRA] (SRAMP-251) Improve XSLT in overlord commons installer

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-251?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-251: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/37 > Improve XSLT in overlord commons installer > ------------------------------------------ > > Key: SRAMP-251 > URL: https://issues.jboss.org/browse/SRAMP-251 > 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 > > > The current overlord commons installer XSLT used to add security domains to jboss eap/wildfly has an ambiguous element declaration. When adding the security domain, the xslt has this: > {code} > <security-domains> > <security-domain /> > </security-domains> > {code} > Because the XSLT doesn't declare a default namespace, this is problematic depending on the processor used. Instead, the XSLT should be explicit about the QNames used in any element it creates. > Note that the XSLT is currently designed to work with both EAP and Wildfly, which have different namespaces for the element being created. So we'll likely need multiple templates for multiple versions of the "as" namespace. -- 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
0
0 / 0

[JBoss JIRA] (SRAMP-251) Improve XSLT in overlord commons installer

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-251?page=com.atlassian.jira.plugin.... ] Work on SRAMP-251 started by Eric Wittmann. > Improve XSLT in overlord commons installer > ------------------------------------------ > > Key: SRAMP-251 > URL: https://issues.jboss.org/browse/SRAMP-251 > 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 > > > The current overlord commons installer XSLT used to add security domains to jboss eap/wildfly has an ambiguous element declaration. When adding the security domain, the xslt has this: > {code} > <security-domains> > <security-domain /> > </security-domains> > {code} > Because the XSLT doesn't declare a default namespace, this is problematic depending on the processor used. Instead, the XSLT should be explicit about the QNames used in any element it creates. > Note that the XSLT is currently designed to work with both EAP and Wildfly, which have different namespaces for the element being created. So we'll likely need multiple templates for multiple versions of the "as" namespace. -- 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
0
0 / 0

[JBoss JIRA] (RTGOV-307) Derive list of service and operation names from response time collection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-307?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-307: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> changed the Status of [bug 1003928|https://bugzilla.redhat.com/show_bug.cgi?id=1003928] from NEW to MODIFIED > Derive list of service and operation names from response time collection > ------------------------------------------------------------------------ > > Key: RTGOV-307 > URL: https://issues.jboss.org/browse/RTGOV-307 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the list of service types, and operations for those service types, are derived from the service definition active map. However the contents of this map expires after a predefined time period, and therefore the options available in the drop down lists will not necessarily relate to the search criteria defined in the response time collection. > Therefore it would be better if the service type and operation information is derived from the complete response time collection contents instead. -- 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
0
0 / 0

[JBoss JIRA] (RTGOV-307) Derive list of service and operation names from response time collection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-307?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-307: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1003928 > Derive list of service and operation names from response time collection > ------------------------------------------------------------------------ > > Key: RTGOV-307 > URL: https://issues.jboss.org/browse/RTGOV-307 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the list of service types, and operations for those service types, are derived from the service definition active map. However the contents of this map expires after a predefined time period, and therefore the options available in the drop down lists will not necessarily relate to the search criteria defined in the response time collection. > Therefore it would be better if the service type and operation information is derived from the complete response time collection contents instead. -- 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
0
0 / 0

[JBoss JIRA] (RTGOV-307) Derive list of service and operation names from response time collection

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-307?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-307. ------------------------------ Resolution: Done > Derive list of service and operation names from response time collection > ------------------------------------------------------------------------ > > Key: RTGOV-307 > URL: https://issues.jboss.org/browse/RTGOV-307 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the list of service types, and operations for those service types, are derived from the service definition active map. However the contents of this map expires after a predefined time period, and therefore the options available in the drop down lists will not necessarily relate to the search criteria defined in the response time collection. > Therefore it would be better if the service type and operation information is derived from the complete response time collection contents instead. -- 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
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues October 2013