[overlord-issues] [JBoss JIRA] (ARTIF-657) Remove updateContent capability

[Brett Meyer (JIRA)]

    [ https://issues.jboss.org/browse/ARTIF-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061146#comment-13061146 ] 

Brett Meyer commented on ARTIF-657:
-----------------------------------

In the end, I think I'm going to go back to completely disabling updateContent.  First off, there are numerous technical challenges with that approach.  Secondly, and most importantly, I think it's detrimental to what we're trying to accomplish.  Instead, ARTIF-679 will add numerous capabilities to auditing and ARTIF-681 will add full-blown artifact versioning.

Note that ARTIF-678 added a "force delete" option that helps in some edge cases.

> Remove updateContent capability
> -------------------------------
>
>                 Key: ARTIF-657
>                 URL: https://issues.jboss.org/browse/ARTIF-657
>             Project: Artificer
>          Issue Type: Bug
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>
> In the middle of ImpactAnalysisDemo, after all artifacts and relationships have been created, run updateContent on the XSD, using the same .xsd file.  The demo will still run successfully.  But when finished, pull up the UI and hit one of the Part 'parameter" artifacts, then hit their Relationship tab.  It fails, most likely because the relationship wasn't re-created.
> Not sure how to handle that.  Should the relationships really be re-generated?  If so, what happens if, for example, a WSDL Part uses a type that's been modified or removed?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)