[JBoss JIRA] (SRAMP-160) Change artifact's 'delete' action to be a logical delete
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-160:
-----------------------------------
Summary: Change artifact's 'delete' action to be a logical delete
Key: SRAMP-160
URL: https://issues.jboss.org/browse/SRAMP-160
Project: S-RAMP
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Core
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.2.0 - Milestone 4
The reason for doing this is that we should not allow duplicate UUIDs, even for deleted artifacts. Currently a delete will remove the artifact from the repository. Instead, we should either move the artifact to some alternate collection or simply tag it as deleted (and then augment all incoming queries with a predicate that will exclude deleted artifacts).
Do we need a way to actually for-real delete an artifact?
--
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, 7 months
[JBoss JIRA] (SRAMP-157) Implement Auditing in the S-RAMP repository
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-157:
-----------------------------------
Summary: Implement Auditing in the S-RAMP repository
Key: SRAMP-157
URL: https://issues.jboss.org/browse/SRAMP-157
Project: S-RAMP
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Core
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.2.0 - Milestone 4
We want to make sure that we have full auditing support so that we can track all changes made to artifacts.
--
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, 7 months
[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts
by Kurt Stam (JIRA)
[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ]
Kurt Stam commented on SRAMP-113:
---------------------------------
Yeah ATM we add them as properties:
if (contentType != null && contentLength != null) {
artifact.getOtherAttributes().put(SrampConstants.SRAMP_CONTENT_SIZE_QNAME, contentLength);
artifact.getOtherAttributes().put(SrampConstants.SRAMP_CONTENT_TYPE_QNAME, contentType);
}
but I think this will be problematic when writing queries.
> Improve WSDL derivation to find references to other artifacts
> -------------------------------------------------------------
>
> Key: SRAMP-113
> URL: https://issues.jboss.org/browse/SRAMP-113
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.2.0 - Milestone 4
>
>
> Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas.
--
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, 7 months
[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-113:
-------------------------------------
That's a great point and I think you're right. We need two extended types:
ExtendedArtifactType
ExtendedDocumentType
The latter might inherit from the former and add the standard DocumentType meta-data (file size, content type, hash). Alternatively the ExtendedDocumentType can extend DocumentType and add the 'extendedType' attribute.
> Improve WSDL derivation to find references to other artifacts
> -------------------------------------------------------------
>
> Key: SRAMP-113
> URL: https://issues.jboss.org/browse/SRAMP-113
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.2.0 - Milestone 4
>
>
> Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas.
--
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, 7 months
[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-113:
-------------------------------------
I could go either way. I think it's definitely a reasonable piece of meta-data to store on the artifact. Although we might consider adding it to Document rather than BaseArtifactType, since the latter might not necessarily have any content from which to calculate the hash.
> Improve WSDL derivation to find references to other artifacts
> -------------------------------------------------------------
>
> Key: SRAMP-113
> URL: https://issues.jboss.org/browse/SRAMP-113
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.2.0 - Milestone 4
>
>
> Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas.
--
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, 7 months