[
https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin....
]
Eric Wittmann commented on SRAMP-395:
-------------------------------------
I added an isValid() method in the artifact type which gets called whenever an extended
artifact type is being created. If the valid test fails then the artifact type cannot be
created. This is very low level and should prevent this problem no matter where it comes
from (UI, CLI, API, any other I).
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