[JBoss JIRA] (ARTIF-657) Remove updateContent and deleteContent
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-657?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed ARTIF-657.
-----------------------------
> Remove updateContent and deleteContent
> --------------------------------------
>
> Key: ARTIF-657
> URL: https://issues.jboss.org/browse/ARTIF-657
> Project: Artificer
> Issue Type: Bug
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.1.0.Final, 1.0.0.Beta1
>
>
> 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)
9 years
[JBoss JIRA] (ARTIF-689) Remove the JCR persistence adapter
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-689?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed ARTIF-689.
-----------------------------
> Remove the JCR persistence adapter
> ----------------------------------
>
> Key: ARTIF-689
> URL: https://issues.jboss.org/browse/ARTIF-689
> Project: Artificer
> Issue Type: Task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.1.0.Final, 1.0.0.Beta1
>
>
> ARTIF-683 switched to a JPA/RDBMS default persistence strategy. Originally, we intended to keep the JCR plugin and continue to maintain it, however:
> First and foremost, initial performance tests are looking extremely promising. With the exception of uploads (slower for JPA due to Hibernate Search indexing and complicated INSERTs, as opposed to JCR node creation), everything else is 2-5x faster, including complex queries.
> Further, I'm starting to hit certain dependency conflicts between Hibernate and ModeShape that might eventually require a split in Artificer distros. Maintaining both is already becoming a headache.
> Is there much of a point in keeping both? The only argument I can think of is if for some reason a user was integrating S-RAMP's JCR storage with their existing, *non-RDBMS* source (Cassandra, etc) through ModeShape/Infinispan. But that's highly unlikely. In my mind, everything else trumps the off-chance for backward compatibility issues. Most users we talk to see JCR purely as an implementation detail.
> We will, however, provide a migration strategy. It would simply be code fragments from both adapters, translating to and from the backends. Honestly simple stuff.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ARTIF-657) Remove updateContent and deleteContent
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-657?page=com.atlassian.jira.plugin.... ]
Brett Meyer resolved ARTIF-657.
-------------------------------
Resolution: Done
> Remove updateContent and deleteContent
> --------------------------------------
>
> Key: ARTIF-657
> URL: https://issues.jboss.org/browse/ARTIF-657
> Project: Artificer
> Issue Type: Bug
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.1.0.Final, 1.0.0.Beta1
>
>
> 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)
9 years
[JBoss JIRA] (ARTIF-657) Remove updateContent and deleteContent
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-657?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-657:
------------------------------
Summary: Remove updateContent and deleteContent (was: Remove updateContent capability)
> Remove updateContent and deleteContent
> --------------------------------------
>
> Key: ARTIF-657
> URL: https://issues.jboss.org/browse/ARTIF-657
> Project: Artificer
> Issue Type: Bug
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.1.0.Final, 1.0.0.Beta1
>
>
> 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)
9 years
[JBoss JIRA] (ARTIF-695) Refactor the file storage service
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-695?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-695:
------------------------------
Description: JDBC Blob vs filesystem storage is currently tightly coupled to the JPA plugin. Pull out into a separate contract (strategy registration pattern) (was: JDBC Blob vs filesystem storage is currently tightly coupled to the JPA plugin. Pull out into a separate contract.)
> Refactor the file storage service
> ---------------------------------
>
> Key: ARTIF-695
> URL: https://issues.jboss.org/browse/ARTIF-695
> Project: Artificer
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> JDBC Blob vs filesystem storage is currently tightly coupled to the JPA plugin. Pull out into a separate contract (strategy registration pattern)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years