[overlord-issues] [JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates
[
https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on SRAMP-541:
-----------------------------------
[~sbunciak], that was the thought -- removing it across the board. However, before we
jump to conclusions, let's think it through completely. The S-RAMP Atom spec does
have bits about updating content through PUT, but it's fairly vague.
Consider removing artifact/content updates
------------------------------------------
Key: SRAMP-541
URL: https://issues.jboss.org/browse/SRAMP-541
Project: S-RAMP
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Brett Meyer
Assignee: Brett Meyer
Fix For: 0.6.0
From [~eric.wittmann] on SRAMP-539:
{quote}
In particular, updates are problematic with regard to derived content. What do we do with
the derived artifacts if we change the content? Presumably we would delete them and
re-derive. But if we do that, we might lose meta-data added to those derived artifacts
manually by users. There may also be relationships that have been formed on those derived
artifacts, in which case referential integrity will prevent them from being deleted, and
the update will fail.
All in all I am disappointed in myself for implementing the updateContent feature to
begin with.
{quote}
I also agree that updateContent and artifact updates should probably be removed entirely.
It's caused quite a bit of confusion, is only partially implemented, and could cause
quite a bit of harm in real-world use cases.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)