February 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-339) Date/time range filter does not currently allow time to be specified

by Michael Clay (JIRA)

[ https://issues.jboss.org/browse/RTGOV-339?page=com.atlassian.jira.plugin.... ] Michael Clay reassigned RTGOV-339: ---------------------------------- Assignee: Michael Clay (was: Gary Brown) > Date/time range filter does not currently allow time to be specified > -------------------------------------------------------------------- > > Key: RTGOV-339 > URL: https://issues.jboss.org/browse/RTGOV-339 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Date/time filter only currently allows the date to be specified, which only allows the granularity to be at the level of days. > We need the user to be able to specify the filter down to the seconds level of granularity. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-360) Move the 'resubmit' fields closer to the resubmit button

by Michael Clay (JIRA)

[ https://issues.jboss.org/browse/RTGOV-360?page=com.atlassian.jira.plugin.... ] Michael Clay resolved RTGOV-360. -------------------------------- Resolution: Done > Move the 'resubmit' fields closer to the resubmit button > -------------------------------------------------------- > > Key: RTGOV-360 > URL: https://issues.jboss.org/browse/RTGOV-360 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Currently the resubmit by, at and result fields are displayed above the message content. I think it would be better if this information was displayed along side the 'resubmit' button, and only information once a resubmission has been performed. > The text should then be of the form: > Resubmitted by 'xyz' at 'date and time': Successful -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-360) Move the 'resubmit' fields closer to the resubmit button

by Michael Clay (JIRA)

[ https://issues.jboss.org/browse/RTGOV-360?page=com.atlassian.jira.plugin.... ] Work on RTGOV-360 started by Michael Clay. > Move the 'resubmit' fields closer to the resubmit button > -------------------------------------------------------- > > Key: RTGOV-360 > URL: https://issues.jboss.org/browse/RTGOV-360 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Currently the resubmit by, at and result fields are displayed above the message content. I think it would be better if this information was displayed along side the 'resubmit' button, and only information once a resubmission has been performed. > The text should then be of the form: > Resubmitted by 'xyz' at 'date and time': Successful -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-359) "Value too long" error when storing resubmit failure result

by Michael Clay (JIRA)

[ https://issues.jboss.org/browse/RTGOV-359?page=com.atlassian.jira.plugin.... ] Michael Clay resolved RTGOV-359. -------------------------------- Resolution: Done see pull request > "Value too long" error when storing resubmit failure result > ----------------------------------------------------------- > > Key: RTGOV-359 > URL: https://issues.jboss.org/browse/RTGOV-359 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Related to RTGOV-332. > When a failure occurs resubmitting the message, the result is stored in a property associated with the situation. However there is a length restriction of VARCHAR(255) on this field: > 10:08:01,249 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-3) Value too long for column "VALUE VARCHAR(255)": "STRINGDECODE('org.overlord.rtgov.ui.client.model.UiException: org.switchyard.HandlerException: SWITCHYARD014000: Validator ''org... (12795)"; SQL statement: > insert into RTGOV_SITUATION_PROPERTIES (id, name, value) values (?, ?, ?) [22001-168] > The original intention of the result field was to report whether the message had been resubmitted successfully or not. Therefore we have a few options: > 1) Just report 'successful' or 'failed' in this field - however this doesn't give an indication of why the resubmit failed. Although the failure is reported at the time when the resubmit is performed, so just depends whether we actually want the resubmission error to be persisted? > 2) Truncate the error message - probably 250 characters would be enough anyway? However we should prefix the result with "Failed: ". > Probably option 2 is best, although need to also ensure that a 'Successful' result is also recorded. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-267) Migrate gwt/bootstrap widgets to overlord-commons

by Gary Brown (JIRA)

Gary Brown created SRAMP-267: -------------------------------- Summary: Migrate gwt/bootstrap widgets to overlord-commons Key: SRAMP-267 URL: https://issues.jboss.org/browse/SRAMP-267 Project: S-RAMP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Kurt Stam Some of the common bootstrap/gwt related widgets have been moved to overlord-commons, to be shared across overlord projects. This issue is to: 1) Move any remaining widgets that are still only in sramp repo 2) Migrate sramp (and possibly dtgov) across to use the overload-commons version of the widgets, and remove the sramp copy. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-266) on tomcat password is in two places

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-266: ------------------------------- Summary: on tomcat password is in two places Key: SRAMP-266 URL: https://issues.jboss.org/browse/SRAMP-266 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Governance Environment: tomcat Reporter: Kurt Stam Assignee: Eric Wittmann Fix For: 0.4.0 - API Management This maybe a commons issue, but the admin/pw is in tomcat-users.xml as well as in tomcat-users-overlord.xml. One file should be sufficient I think? -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-265) persist s-ramp data on tomcat

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-265: ------------------------------- Summary: persist s-ramp data on tomcat Key: SRAMP-265 URL: https://issues.jboss.org/browse/SRAMP-265 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Persistence Environment: tomcat Reporter: Kurt Stam Assignee: Eric Wittmann Fix For: 0.4.0 - API Management Need a different modeshape json config file to turn on persistence -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-264) password with '!' breaks login

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-264: ------------------------------- Summary: password with '!' breaks login Key: SRAMP-264 URL: https://issues.jboss.org/browse/SRAMP-264 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Shell Reporter: Kurt Stam Assignee: Kurt Stam Fix For: 0.4.0 - API Management My password contains an exclamation mark: 'admin!23'. s-ramp> s-ramp:connect http://localhost:8080/s-ramp-server S-RAMP Username: admin S-RAMP Password: ******** java.lang.IllegalArgumentException: !23: event not found -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-264) password with '!' breaks login

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-264?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-264: ---------------------------- Assignee: Eric Wittmann (was: Kurt Stam) > password with '!' breaks login > ------------------------------ > > Key: SRAMP-264 > URL: https://issues.jboss.org/browse/SRAMP-264 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: 0.4.0 - API Management > > > My password contains an exclamation mark: 'admin!23'. > s-ramp> s-ramp:connect http://localhost:8080/s-ramp-server > S-RAMP Username: admin > S-RAMP Password: ******** > java.lang.IllegalArgumentException: !23: event not found -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-361) Migrate from sramp UI widgets to those in overlord-commons

by Gary Brown (JIRA)

Gary Brown created RTGOV-361: -------------------------------- Summary: Migrate from sramp UI widgets to those in overlord-commons Key: RTGOV-361 URL: https://issues.jboss.org/browse/RTGOV-361 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Some GWT based UI widgets have been moved from sramp to overlord-commons. Try migrating rtgov-ui to use the overlord-commons widgets, to remove the dependency on sramp. -- 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, 4 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