September 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-223) Jboss dependency should be org.jboss.as.clustering.infinispan

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-223?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-223: ----------------------------------------------- Stefan Bunciak <sbunciak(a)redhat.com> made a comment on [bug 991132|https://bugzilla.redhat.com/show_bug.cgi?id=991132] Verified in S-RAMP 6.0.0.ER2 > Jboss dependency should be org.jboss.as.clustering.infinispan > ------------------------------------------------------------- > > Key: SRAMP-223 > URL: https://issues.jboss.org/browse/SRAMP-223 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > The s-ramp-server WAR has a jboss dependency on org.infinispan (which we patch because we *thought* it was missing a dependency). Instead, the dependency from s-ramp-server should be on org.jboss.as.clustering.infinispan (which has all the right dependencies). > I need to update the dependency in s-ramp-server.war *and* remove the patching from the s-ramp installer. -- 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-223) Jboss dependency should be org.jboss.as.clustering.infinispan

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-223?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-223: ----------------------------------------------- Stefan Bunciak <sbunciak(a)redhat.com> changed the Status of [bug 991132|https://bugzilla.redhat.com/show_bug.cgi?id=991132] from ON_QA to VERIFIED > Jboss dependency should be org.jboss.as.clustering.infinispan > ------------------------------------------------------------- > > Key: SRAMP-223 > URL: https://issues.jboss.org/browse/SRAMP-223 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > The s-ramp-server WAR has a jboss dependency on org.infinispan (which we patch because we *thought* it was missing a dependency). Instead, the dependency from s-ramp-server should be on org.jboss.as.clustering.infinispan (which has all the right dependencies). > I need to update the dependency in s-ramp-server.war *and* remove the patching from the s-ramp installer. -- 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-268) Service response time aggregation not performed correctly for min/max values

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-268?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-268: ----------------------------------------------- Jiri Pechanec <jpechane(a)redhat.com> made a comment on [bug 1004173|https://bugzilla.redhat.com/show_bug.cgi?id=1004173] It works as expected, good job > Service response time aggregation not performed correctly for min/max values > ---------------------------------------------------------------------------- > > Key: RTGOV-268 > URL: https://issues.jboss.org/browse/RTGOV-268 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the min/max values are based on the extreme avg values being aggregated. > However the min/max values should also be aggregated, to get a better mean value over these properties. -- 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-269) Report activity logger problems via MBean

by Gary Brown (JIRA)

Gary Brown created RTGOV-269: -------------------------------- Summary: Report activity logger problems via MBean Key: RTGOV-269 URL: https://issues.jboss.org/browse/RTGOV-269 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 When the REST client fails to report a list of activity units to the server, then report issue via MBean. To avoid reporting a notification for each failure, only report the first occurrence within a 5 min window - if the issue persists, then send a further reminder each 5 mins. It may also be useful to provide an indication of the number of consecutive failures as a counter, so they can see when the issue is fixed. Alternatively send a notification when a failure is not reported for 1 min? -- 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-269) Report activity logger problems via MBean

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-269?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-269: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1005273 > Report activity logger problems via MBean > ----------------------------------------- > > Key: RTGOV-269 > URL: https://issues.jboss.org/browse/RTGOV-269 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > When the REST client fails to report a list of activity units to the server, then report issue via MBean. > To avoid reporting a notification for each failure, only report the first occurrence within a 5 min window - if the issue persists, then send a further reminder each 5 mins. > It may also be useful to provide an indication of the number of consecutive failures as a counter, so they can see when the issue is fixed. Alternatively send a notification when a failure is not reported for 1 min? -- 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-233) Check for null logger in s-ramp wagon

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-233?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-233. ------------------------------- > Check for null logger in s-ramp wagon > ------------------------------------- > > Key: SRAMP-233 > URL: https://issues.jboss.org/browse/SRAMP-233 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > In certain use cases the wagon will not be injected with the logger. Make sure to check for null before using it. Once that is done, remove the SrampWagonProxy class from dtgov. -- 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-232) Custom Properties Do Not Render Correctly In The Safari Browser

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-232?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-232. ------------------------------- > Custom Properties Do Not Render Correctly In The Safari Browser > --------------------------------------------------------------- > > Key: SRAMP-232 > URL: https://issues.jboss.org/browse/SRAMP-232 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.4.0 - API Management > Environment: OS X 10.8.4, Safari 6.0.5 > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > Attachments: customProperties.png > > > The custom properties of artifacts are displaying on the same line and wrapping when necessary. So for instance, properties x, y, and z, with values 1, 2, and 3 respectfully could display in these 2 different ways (depending on window size): > a: 1b: 2c: 3|Add Property| > or > a: 1b: 2c: > 3|Add Property| > I did not see this problem using the Chrome browser. -- 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-230) ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-230?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-230. ------------------------------- > ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext > ---------------------------------------------------------------------------------- > > Key: SRAMP-230 > URL: https://issues.jboss.org/browse/SRAMP-230 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.4.0 - API Management > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > While writing a custom {{AbstractXmlDeriver}}, I needed to register a namespace discovered during the processing of the XML file (i.e., during the {{derive}} method). The only way I could figure out how to do this was to cache the instance of the {{StaticNamespaceContext}} passed into the {{configureNamespaceMappings}} method. Then, when the {{derive}} method is called I could register namespaces with the namespace context. It would be nice to have a getter for the namespace context for subclasses to use. -- 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-232) Custom Properties Do Not Render Correctly In The Safari Browser

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-232?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-232. --------------------------------- Resolution: Done I was creating spans when I should have been creating divs. > Custom Properties Do Not Render Correctly In The Safari Browser > --------------------------------------------------------------- > > Key: SRAMP-232 > URL: https://issues.jboss.org/browse/SRAMP-232 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.4.0 - API Management > Environment: OS X 10.8.4, Safari 6.0.5 > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > Attachments: customProperties.png > > > The custom properties of artifacts are displaying on the same line and wrapping when necessary. So for instance, properties x, y, and z, with values 1, 2, and 3 respectfully could display in these 2 different ways (depending on window size): > a: 1b: 2c: 3|Add Property| > or > a: 1b: 2c: > 3|Add Property| > I did not see this problem using the Chrome browser. -- 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-233) Check for null logger in s-ramp wagon

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-233?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-233. --------------------------------- Resolution: Done > Check for null logger in s-ramp wagon > ------------------------------------- > > Key: SRAMP-233 > URL: https://issues.jboss.org/browse/SRAMP-233 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > In certain use cases the wagon will not be injected with the logger. Make sure to check for null before using it. Once that is done, remove the SrampWagonProxy class from dtgov. -- 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 September 2013