April 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-395. ------------------------------- > S-RAMP allows artifacts to be created with invalid characters in the Artifact Type > ---------------------------------------------------------------------------------- > > Key: SRAMP-395 > URL: https://issues.jboss.org/browse/SRAMP-395 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0 - API Management > > > There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: > {code} > s-ramp:upload /path/to/file.ext "Invalid Type" > s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here." > {code} > The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. > We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). > For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-395: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/396 > S-RAMP allows artifacts to be created with invalid characters in the Artifact Type > ---------------------------------------------------------------------------------- > > Key: SRAMP-395 > URL: https://issues.jboss.org/browse/SRAMP-395 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0 - API Management > > > There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: > {code} > s-ramp:upload /path/to/file.ext "Invalid Type" > s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here." > {code} > The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. > We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). > For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ] Eric Wittmann reassigned SRAMP-395: ----------------------------------- Assignee: Eric Wittmann (was: David virgil naranjo) > S-RAMP allows artifacts to be created with invalid characters in the Artifact Type > ---------------------------------------------------------------------------------- > > Key: SRAMP-395 > URL: https://issues.jboss.org/browse/SRAMP-395 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0 - API Management > > > There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: > {code} > s-ramp:upload /path/to/file.ext "Invalid Type" > s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here." > {code} > The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. > We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). > For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-189) Upload Switchyard SCA diagram automatically from maven

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-189?page=com.atlassian.jira.plugin.... ] Brett Meyer reassigned SRAMP-189: --------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > Upload Switchyard SCA diagram automatically from maven > ------------------------------------------------------ > > Key: SRAMP-189 > URL: https://issues.jboss.org/browse/SRAMP-189 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0 - API Management > > > Switchyard is planning on generating an SCA diagram for applications during build. When uploading the application to s-ramp this diagram should be included and appropriately linked. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-170) Atom feeds do not work very well in exisiting clients

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-170?page=com.atlassian.jira.plugin.... ] Brett Meyer reassigned SRAMP-170: --------------------------------- Assignee: Brett Meyer (was: Kurt Stam) > Atom feeds do not work very well in exisiting clients > ----------------------------------------------------- > > Key: SRAMP-170 > URL: https://issues.jboss.org/browse/SRAMP-170 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Atom Binding > Affects Versions: 0.1.1 - Workflow Demo > Reporter: Kurt Stam > Assignee: Brett Meyer > Priority: Minor > Fix For: 0.5.0 - API Management > > Attachments: Screen Shot 2013-03-10 at 12.08.22 PM.png > > > When using exiting atom clients our feed don't work very well. I think one should be able to follow links down into an entry for example, but the link is not populated. We should investigate why this is. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-391) Support EAP 6.3

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-391?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-391: ----------------------------- Summary: Support EAP 6.3 (was: Support EAP 6.2) Fix Version/s: 2.0.0.Final (was: 2.1.0.Final) Description: Add support for EAP 6.3. (was: Add support for EAP 6.2.) > Support EAP 6.3 > --------------- > > Key: RTGOV-391 > URL: https://issues.jboss.org/browse/RTGOV-391 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Add support for EAP 6.3. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-431) Upgrade to EAP 6.3

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-431?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-431. ------------------------------ Fix Version/s: (was: 2.0.0.Final) Resolution: Duplicate Issue > Upgrade to EAP 6.3 > ------------------ > > Key: RTGOV-431 > URL: https://issues.jboss.org/browse/RTGOV-431 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-431) Upgrade to EAP 6.3

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-431?page=com.atlassian.jira.plugin.... ] Gary Brown closed RTGOV-431. ---------------------------- > Upgrade to EAP 6.3 > ------------------ > > Key: RTGOV-431 > URL: https://issues.jboss.org/browse/RTGOV-431 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-382) Support EAP 6.3

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.... ] Eric Wittmann reassigned SRAMP-382: ----------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > Support EAP 6.3 > --------------- > > Key: SRAMP-382 > URL: https://issues.jboss.org/browse/SRAMP-382 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.5.0 - API Management > > > Add support for EAP 6.3. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-382) Support EAP 6.2

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.... ] Gary Brown updated SRAMP-382: ----------------------------- Description: Add support for EAP 6.. (was: Add support for EAP 6.2.) > Support EAP 6.2 > --------------- > > Key: SRAMP-382 > URL: https://issues.jboss.org/browse/SRAMP-382 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Kurt Stam > Fix For: 0.5.0 - API Management > > > Add support for EAP 6.. -- 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, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues April 2014