Red Hat Bugzilla – Bug 1011397
Value of attribute 'derived' is inconsistent for SwitchYardComponentService artifact
Last modified: 2014-02-06 10:25:28 EST
Description of problem:
Value of attribute 'derived' is inconsistent for SwitchYardComponentService artifact.
* Artifact details in S-RAMP repository browser:
2013-09-24 by admin
2013-09-24 by admin
* Downloaded meta-data:
<s-ramp:ExtendedArtifactType extendedType="SwitchYardComponentService" artifactType="ExtendedArtifactType" name="ExampleService" createdBy="admin" uuid="6ff0e58b-a4dc-454a-a35d-d045b34ebc5d" createdTimestamp="2013-09-24T09:46:51.603+02:00" lastModifiedTimestamp="2013-09-24T09:46:53.922+02:00" lastModifiedBy="admin" s-ramp:derived="true" s-ramp:contentType="application/xml">
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy application which contains policy definition so that S-RAMP will derive SwitchYardComponentService for it
2. Check the S-RAMP repository for the inconsistency
This also applies to SwitchYardTransformer & SwitchYardService artifact type.
This is causing these derived artifacts not to show when selected 'Origin' to derived in S-RAMP repository browser.
In my testing I haven't been able to confirm that the artifacts fail to come back when 'Origin' is set to Derived.
In my testing my SY app was added to s-ramp, resulting in 64 total artifacts. When I click Primary it results in 11 being shown, when I click on Derived it results in 53 being shown (albeit paged).
I believe the bug is limited to the Derived column in the list of artifacts and also the "Derived:" section of the artifact details page.
Eric Wittmann <firstname.lastname@example.org> updated the status of jira SRAMPUI-110 to Coding In Progress
Eric Wittmann <email@example.com> updated the status of jira SRAMPUI-110 to Resolved
Eric Wittmann <firstname.lastname@example.org> updated the status of jira SRAMPUI-110 to Closed
Created attachment 802376 [details]
s-ramp-ui patch to fix this issue
I have merged the community fix onto the s-ramp-ui product branch (0.3.0.Final-prod-ip6.0).
Additionally, I am attaching a standalone patch file, in case that is desired (more targeted fix for ER3 vs. doing a full rebuild).
NOTE: you should *either* pull latest changes from the s-ramp-ui git repo (product branch) *OR* use the attached patch. They are the same - I am simply providing options to the prod team. :)
This hasn't been fixed in ER4, I can still reproduce.
I'll test with ER4 and see what's up.
Looks like the ER4 tag was incorrectly created (by me) for the s-ramp-ui project. I have re-tagged as:
We can use this if another ER4 build is being done. If not, then this fix can get in for ER5 instead.
Nick, see my previous comment. Will there be another ER4 build?
In either case, can you push this bug into whatever state it should be given the details above?
Verified in FSW 6.0.0.ER7