OSLC - Doors Next creating Artifacts and adding them to a module
Hi,
I've successfully created Artifacts and modules but am having problems trying to add the created artifact to a module. I've looked at the module api, but I don't see where that comes in. Is there a different CreationFactory I should be using?
You need to create an artifact to get the resourceUri to add it to the uses @resource attribute. However, what do you do about the parent?
My projects are set up to save base artifacts in a given folder, so does my client need to be aware of that?
Are you creating the base artifacts when you do this and does Doors create an instance if that module with its own resource url when you add the uses tag to the module rdf for the update? I notice that the artifacts that already exist in the module have ids that are prefixed with "MB_".
I can update the description of the module successfully but adding the uses tag refering to the new module causes a "bad request" error.
Lots of questions, but I'm close to doing what I need to do - adding artifacts to the module is the remaining task for me to figure out.
Thanks in advance for any pointers.
Andy.
|
2 answers
|
Ok, I've figured it out after looking through the docs more closely at
I didn't notice the different header
|
|
Ok,
Another question...
Out of the following binding, what do you need to provide? All of it or just the boundArtifact assuming that the rest would be filled in by the server?
<rm_modules:Binding rdf:about="https://clmwb.com:9444/rdm/resources/MB_e34eb5d27c8446c791e72a882d52fd34">
<oslc_config:component rdf:resource="https://clmwb.com:9444/rdm/cm/component/_Y5OakLruEeevMtDqCXe--Q"/>
<rm_modules:boundArtifact rdf:resource="https://clmwb.com:9444/rdm/resources/CA_63362a5f2a0842b0b83a66d04f39c327"/>
<rm_modules:module rdf:resource="https://clmwb.com:9444/rdm/resources/_4sscEb43EeeD0-df1VhHuw"/>
<rm_modules:childBindings rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#nil"/>
</rm_modules:Binding>
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.