Re: [lyo-dev] Lyo OSLC Client for Rational DOORS

[Samuel Padgett <spadgett@xxxxxxxxxx>]

Marcus,

> By the way, is there a way to fetch the whole information set of all requirements
> in a given module at once instead of querying the member urls first?

If you call OslcQueryParameters.setSelect("*") and then OslcQueryResult.getMembers(Class<T>) on the result, does it give you what you need?

--
Samuel Padgett | IBM Rational | spadgett@xxxxxxxxxx
Eclipse Lyo: Enabling tool integration with OSLC


"Marcus Engelhardt" ---02/03/2014 04:15:15 AM---Hi Maeve,   thank your very much for your response! You made my day! It is the project parameter tha

From:	"Marcus Engelhardt" <FDSProject@xxxxxx>
To:	"Maeve O Reilly" <maevedevine@xxxxxxxxx>, lyo-dev@xxxxxxxxxxx
Date:	02/03/2014 04:15 AM
Subject:	Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
Sent by:	lyo-dev-bounces@xxxxxxxxxxx

---

Hi Maeve,
 
thank your very much for your response! You made my day!
It is the project parameter that does the trick. In my setup, it was pointing to a project instead of a module. This name of the parameter is confusing, indeed. Maybe this can be modified in future versions?! I had a look at the  tutorial again and recognized that there a module is used, too.
 
Thanks to all for your help and sorry for my mistake!
By the way, is there a way to fetch the whole information set of all requirements in a given module at once instead of querying the member urls first?
 
Thank you very much!
 
Best,
Marcus

Gesendet: Freitag, 31. Januar 2014 um 14:56 Uhr
Von: "Maeve O Reilly" <maevedevine@xxxxxxxxx>
An: "Marcus Engelhardt" <FDSProject@xxxxxx>, "Lyo project developer discussions" <lyo-dev@xxxxxxxxxxx>
Betreff: Re: Aw: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
Hi Marcus,
 
I've been trying to figure this out and you do have some different query syntax to me.  I have attached the full thing I'm running, which works till it goes to process them (that dateTime issue).  The relevant queries:
 
//STEP 10: Query of changed values
OslcQueryParameters queryParams = new OslcQueryParameters();
queryParams.setPrefix("oslc_rm=<http://open-services.net/ns/rm#>");
queryParams.setWhere("oslc_rm:implementedBy=<https://win08vm2.rcsnl.ams.nl.ibm.com:9444/ccm/web/projects/RTC%20Project#action="">>");
OslcQuery query = new OslcQuery(client, queryCapability, 20, queryParams);
OslcQueryResult result = query.submit();
boolean processAsJavaObjects = false;
int resultsSize = result.getMembersUrls().length;
processPagedQueryResults(result,client, processAsJavaObjects);
System.out.println("\n------------------------------\n");
System.out.println("Number of Results for query 1  = " + resultsSize + "\n");
 
//STEP 11: Now get the artifact with identifier = 9
OslcQueryParameters queryParams2 = new OslcQueryParameters();
//queryParams2 = new OslcQueryParameters();
queryParams2.setPrefix("dcterms=<http://purl.org/dc/terms/>");
queryParams2.setPrefix("oslc_rm=<http://open-services.net/ns/rm#>");
queryParams2.setWhere("dcterms:identifier=9");
query = new OslcQuery(client, queryCapability, 20, queryParams2);
result = query.submit();
int resultsSize2 = result.getMembersUrls().length;
System.out.println("\n------------------------------\n");
 
System.out.println("Number of Results for query 2  = " + resultsSize2 + "\n");
 
 
And this then is the result:
------------------------------
 
Number of Results for query 1  = 4
 
 
------------------------------
 
Number of Results for query 2  = 1
 
Both of which are correct, there are 4 with that link and 1 whose id is 9 in my module.  
 
Apologies if you have covered this.  But in your run configuration, you are passing a DOORS module?  The parameter being '-project' is a bit confusing.  I just tested that with a project and it does break it. It must be a module to which you have full access.  
 
Maeve
 
 
 
On Thursday, 30 January 2014, 13:50, Marcus Engelhardt <FDSProject@xxxxxx> wrote:
Hi Maeve,
 
thanks for your reply and sorry for my late response.
I already have enabled full logging in DWA, but unfortunately there is no hint or stack trace in the output indicating an exception on the service side. I have tried this multiple times and with a lot of different queries. I was able to produce exception for example when dropping the where clause of the query or when providing a query that can not be parsed by the service.
I am actually using the DoorsOauthSample (i.e. the revision available in the git repository on 2014-01-16). The example works fine for fetching the catalog urls and the query facility urls, but each query only returns an empty result set as shown in one of my last mails.
 
Do you have another idea for the potential reason for that?
 
Many thanks in advance!
 
Cheers,
Marcus
 
Gesendet: Freitag, 24. Januar 2014 um 16:15 Uhr
Von: "Maeve O Reilly" <maevedevine@xxxxxxxxx>
An: "Lyo project developer discussions" <lyo-dev@xxxxxxxxxxx>
Betreff: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
I doubt there is a problem with your setup.  Have you set DWA to full logging?  It can be quite good at OSLC requests.  Rename server/festival/conf/log4.properties.support to log4.properties and restart DWA.
 
I missed some of this thread, so apologies if I'm repeating this.  But have you looked at the sample? -  http://wiki.eclipse.org/Lyo/BuildClient#DoorsOauthSample.
It does error out in the end (problem with date != dateTime), but the query works.
 
Maeve
 
 
 
On Friday, 24 January 2014, 14:55, Marcus Engelhardt <FDSProject@xxxxxx> wrote:
Hi Clyde,
well, the %HOSTNAME% value ist just a replacement for the real hostname I use.
Thanks for the mentioning the property. The URLs are now displayed in DWA.
However, the query capabilities still not work for me. The service is returning an "empty" reponse for each query I have tried so far. Does anyone have an idea what is going wrong in my installation?
Thanks!
Best,
Marcus
 
Gesendet: Freitag, 24. Januar 2014 um 14:34 Uhr
Von: "Clyde D Icuspit" <cdicuspi@xxxxxxxxxx>
An: "Lyo project developer discussions" <lyo-dev@xxxxxxxxxxx>
Cc: lyo-dev-bounces@xxxxxxxxxxx
Betreff: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
Hi Marcus,

It's interesting that you have %HOSTNAME% as part of the URI. You need to run the dbadmin command again this time replacing the string HOSTNAME with the name of the host running DWA.

To display the URL of the selected resource in the DWA GUI, you need to add the following property in the festival.xml file:

<f:property name="display.redirector.urls" value="true"/>
 

Sincerely,
Clyde Icuspit
____________________________________________________________
Business Partner ISV Technical Enablement IBM Certified I/T Specialist L2 IBM Rational Software tel: 617.693.7417 email: cdicuspi@xxxxxxxxxx	Ready for IBM Rational Software Partner Program Ready for IBM Rational partner plug-ins






From:        "Marcus Engelhardt" <FDSProject@xxxxxx>
To:        "Maeve O Reilly" <maevedevine@xxxxxxxxx>, "Lyo project developer        discussions" <lyo-dev@xxxxxxxxxxx>,
Date:        01/24/2014 05:14 AM
Subject:        Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
Sent by:        lyo-dev-bounces@xxxxxxxxxxx 

---




Hi Maeve,

I think the dbadmin setup at least for those parameters is ok. I have checked the module properties within the Doors client. The module has a URL that starts as excepted. I can also ask for the resource of a given requirement. I got the URL from the requirement's properties in the Doors client, too. The response looks like this:

<?xml version="1.0"?>
<rdf:RDF
  xmlns:dcterms="http://purl.org/dc/terms/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rm="http://jazz.net/ns/rm#"
  xmlns:rm_property="http://%HOSTNAME%:8080/dwa/rm/urn:rational::1-52d92f3f16611ecc-M-00000020/types/"
  xmlns:acp="http://jazz.net/ns/acp#"
  xmlns:oslc="http://open-services.net/ns/core#"
  xmlns:foaf="http://xmlns.com/foaf/0.1/"
  xmlns:oslc_rm="http://open-services.net/ns/rm#">
<oslc_rm:Requirement rdf:about="http://%HOSTNAME%:8080/dwa/rm/urn:rational::1-52d92f3f16611ecc-O-8447-00000020">
  <rm_property:attrDef-7 rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
  >2013-11-04</rm_property:attrDef-7>
  <rm_property:attrDef-9 rdf:datatype="http://www.w3.org/2001/XMLSchema#integer"
  >8447</rm_property:attrDef-9>
  <rm_property:attrDef-1025 rdf:parseType="Literal"></rm_property:attrDef-1025>
  <rm_property:attrDef-1020 rdf:parseType="Literal"></rm_property:attrDef-1020>
  <rm_property:attrDef-1024 rdf:resource="http://%HOSTNAME%:8080/dwa/rm/urn:rational::1-52d92f3f16611ecc-M-00000020/types/attrDef-1024#3"/>
  <rm_property:attrDef-1019 rdf:parseType="Literal"></rm_property:attrDef-1019>
  <dcterms:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
  >2013-11-04</dcterms:created>
  <rm_property:attrDef-5 rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
  >2013-11-04</rm_property:attrDef-5>
  <dcterms:contributor>
    <foaf:Person>
      <foaf:name>Alireza</foaf:name>
    </foaf:Person>
  </dcterms:contributor>
  <rm_property:attrDef-4 rdf:parseType="Literal">Alireza</rm_property:attrDef-4>
  <dcterms:title rdf:parseType="Literal">VZE_8447: DISPLAY,SPEAKER</dcterms:title>
  <oslc:shortTitle rdf:parseType="Literal">VZE_8447: DISPLAY,SPEAKER</oslc:shortTitle>
  <oslc:serviceProvider rdf:resource="http://%HOSTNAME%:8080/dwa/rm/discovery/service/urn:rational::1-52d92f3f16611ecc-M-00000020"/>
  <rm:primaryText rdf:parseType="Literal">DISPLAY,SPEAKER</rm:primaryText>
  <acp:accessControl rdf:resource="http://%HOSTNAME%:8080/dwa/rm/acp/urn:rational::1-52d92f3f16611ecc-F-00000000/gFgcK1req0%252BQ5gE6yE5YsEZZcDI%253D%250A"/>
  <rm_property:attrDef-12 rdf:parseType="Literal"></rm_property:attrDef-12>
  <oslc:instanceShape rdf:resource="http://%HOSTNAME%:8080/dwa/rm/oslc/shape/requirement/urn:rational::1-52d92f3f16611ecc-M-00000020"/>
  <rm_property:attrDef-10 rdf:resource="http://%HOSTNAME%:8080/dwa/rm/urn:rational::1-52d92f3f16611ecc-M-00000020/types/attrDef-10#1"/>
  <dcterms:description rdf:parseType="Literal">Sub-Blocks HMI</dcterms:description>
  <rm_property:attrDef-13 rdf:parseType="Literal">Sub-Blocks HMI</rm_property:attrDef-13>
  <dcterms:creator>
    <foaf:Person>
      <foaf:name>Alireza</foaf:name>
    </foaf:Person>
  </dcterms:creator>
  <rm_property:attrDef-1026 rdf:parseType="Literal"></rm_property:attrDef-1026>
  <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
  >2013-11-04T15:32:37Z</dcterms:modified>
  <dcterms:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
  >8447</dcterms:identifier>
  <rm_property:attrDef-6 rdf:parseType="Literal">Alireza</rm_property:attrDef-6>
  <rm_property:attrDef-8 rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
  >2013-11-04T15:32:37Z</rm_property:attrDef-8>
</oslc_rm:Requirement>
</rdf:RDF>

However, I can't query for a requirement using the query capability. Even if I query for the requirement whose RDF is printed above I receive an empty result:

<?xml version="1.0"?>
<rdf:RDF
  xmlns:dcterms="http://purl.org/dc/terms/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rm="http://jazz.net/ns/rm#"
  xmlns:acp="http://jazz.net/ns/acp#"
  xmlns:oslc="http://open-services.net/ns/core#"
  xmlns:foaf="http://xmlns.com/foaf/0.1/"
  xmlns:oslc_rm="http://open-services.net/ns/rm#">
<oslc_rm:ResponseInfo rdf:about="http://%HOSTNAME%:8080/dwa/rm/oslc/query/requirement?oslc.paging=true&amp;oslc.pageSize=10&amp;oslc.where=dcterms:identifier=8447&amp;oslc.prefix=dcterms=%3Chttp://purl.org/dc/terms/%3E">
  <dcterms:title>DOORS ERS Repository</dcterms:title>
</oslc_rm:ResponseInfo>
</rdf:RDF>

The lyo query code for this is:

OslcQueryParameters queryParams;          
queryParams = new OslcQueryParameters();
queryParams.setPrefix("dcterms=<http://purl.org/dc/terms/>");
queryParams.setWhere("dcterms:identifier=8447");
OslcQuery query = new OslcQuery(client, queryCapability, 10, queryParams);
OslcQueryResult result = query.submit();

It's the same when I just query for the dcterms:identifier property:

<?xml version="1.0"?>
<rdf:RDF
  xmlns:dcterms="http://purl.org/dc/terms/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rm="http://jazz.net/ns/rm#"
  xmlns:acp="http://jazz.net/ns/acp#"
  xmlns:oslc="http://open-services.net/ns/core#"
  xmlns:foaf="http://xmlns.com/foaf/0.1/"
  xmlns:oslc_rm="http://open-services.net/ns/rm#">
<oslc_rm:ResponseInfo rdf:about="http://%HOSTNAME%:8080/dwa/rm/oslc/query/requirement?oslc.paging=true&amp;oslc.pageSize=10&amp;oslc.where=dcterms:identifier=8447&amp;oslc.select=dcterms:identifier&amp;oslc.prefix=dcterms=%3Chttp://purl.org/dc/terms/%3E">
  <dcterms:title>DOORS ERS Repository</dcterms:title>
</oslc_rm:ResponseInfo>
</rdf:RDF>

The query code for this looks like:

OslcQueryParameters queryParams;              
queryParams = new OslcQueryParameters();
queryParams.setSelect("dcterms:identifier");
queryParams.setPrefix("dcterms=<http://purl.org/dc/terms/>");
queryParams.setWhere("dcterms:identifier=8447");
OslcQuery query = new OslcQuery(client, queryCapability, 10, queryParams);
OslcQueryResult result = query.submit();

So querying for a single requirement does not work for me.

What I actually need is the possibility to query for the full requirements collection available. That's why I am also trying to query for a requirements collection. However, the result is empty here, too. I have tried to query for identifier, date created, title, etc. It's all the same.
He is the result for querying a requirements collection based on the identifier (which should give me the requirement shown above. The result is empty even when dropping the select parameter.
 
<?xml version="1.0"?>
<rdf:RDF
  xmlns:dcterms="http://purl.org/dc/terms/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rm="http://jazz.net/ns/rm#"
  xmlns:acp="http://jazz.net/ns/acp#"
  xmlns:oslc="http://open-services.net/ns/core#"
  xmlns:foaf="http://xmlns.com/foaf/0.1/"
  xmlns:oslc_rm="http://open-services.net/ns/rm#">
<oslc_rm:ResponseInfo rdf:about="http://fokus-pc:8080/dwa/rm/oslc/query/requirementCollection?oslc.paging=true&amp;oslc.pageSize=10&amp;oslc.where=dcterms:identifier=8447&amp;oslc.select=dcterms:identifier&amp;oslc.prefix=dcterms=%3Chttp://purl.org/dc/terms/%3E">
  <dcterms:title>DOORS ERS Repository</dcterms:title>
</oslc_rm:ResponseInfo>
</rdf:RDF>

It's the same when querying by the creation date.

<?xml version="1.0"?>
<rdf:RDF
  xmlns:dcterms="http://purl.org/dc/terms/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rm="http://jazz.net/ns/rm#"
  xmlns:acp="http://jazz.net/ns/acp#"
  xmlns:oslc="http://open-services.net/ns/core#"
  xmlns:foaf="http://xmlns.com/foaf/0.1/"
  xmlns:oslc_rm="http://open-services.net/ns/rm#">
<oslc_rm:ResponseInfo rdf:about="http://fokus-pc:8080/dwa/rm/oslc/query/requirementCollection?oslc.paging=true&amp;oslc.pageSize=10&amp;oslc.where=dcterms:created=%222013-11-04%22&amp;oslc.select=dcterms:created&amp;oslc.prefix=dcterms=%3Chttp://purl.org/dc/terms/%3E">
  <dcterms:title>DOORS ERS Repository</dcterms:title>
</oslc_rm:ResponseInfo>
</rdf:RDF>


I still can see any URL for a requirement in the attribute listing in DWA. Is there something wrong in my setup?

Thanks for your efforts.

Best,
Marcus
 
Gesendet: Donnerstag, 23. Januar 2014 um 18:24 Uhr
Von: "Maeve O Reilly" <maevedevine@xxxxxxxxx>
An: "Marcus Engelhardt" <FDSProject@xxxxxx>
Betreff: Re: Aw: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
Hi Marcus,

I doubt this is related to DCNs.  But cut-n-paste of that dbadmin command can fail to run it properly in DOS - tab characters.  If you just run dbadmin - data 36677@HOSTNAME -dwaHost HOSTNAME -dwaPort 8080 -dwaProtocol http

you should get a response 3 times - stating each parameter is set.
Then open a DOORS client and bring up the properties of a module.  Does it have a URL with http://hostname etc?  That is then what you GET.

Maeve

 
On Thursday, 23 January 2014, 17:06, Marcus Engelhardt <FDSProject@xxxxxx> wrote:
Hi Maeve,

I have checked the configuration a couple of times. I have configured DW using the following command (host name replaced)

dbadmin -dcnEnable -data 36677@HOSTNAME -dcnBrokerUri "tcp://HOSTNAME:61616" -dcnChannelName "dcn" -dwaHost HOSTNAME -dwaPort 8080 -dwaProtocol http

Everything is running locally. DWA is accessible via http://HOSTNAME:8080/dwa.

When I apply these settings above with the dbadmin tool and restart the doors server only (i.e. the service from the windows panel), the dbadmin tool diagnotistics says

"C:\DOORS\Server\bin>dbadmin -dcnInfo -data 36677@HOSTNAME
-I- DBADMIN: Data Change Notification s are currently enabled (Broker URI = 'tcp:
//HOSTNAME:61616', Channel Name = 'dcn')."

When restarting the whole machine and checking the configuration again, it says:

"C:\DOORS\Server\bin>dbadmin -dcnInfo -data 36677@HOSTNAME
-I- DBADMIN: Data Change Notifications are currently enabled but not sending (Br
oker URI = 'tcp://HOSTNAME:61616', Channel Name = 'dcn')."

Is this a hint? I am pretty sure, that the dbadmin tool said "Data Change Notifications are currently enabled" before applying the changes again. But maybe I am wrong ;(

Thanks,
Marcus
 
Gesendet: Donnerstag, 23. Januar 2014 um 16:53 Uhr
Von: "Maeve O Reilly" <maevedevine@xxxxxxxxx>
An: "lyo-dev@xxxxxxxxxxx" <lyo-dev@xxxxxxxxxxx>
Betreff: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
Hi Marcus,

if you are not seeing a URL  to get, double check the dbadmin -dwaHost/dwaProtocol/dwaPort settings when you configured DWA.  

This is what a RDF looks like for me, but I don't know how to query for that foaf stuff seen for creator.  I assume you need some extra clauses.

Maeve

https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/urn:rational::1-51929a740f221131-O-21-0000002a
<?xml version="1.0"?>
<rdf:RDF
   xmlns:dcterms="http://purl.org/dc/terms/"
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:doorsAttribute="http://jazz.net/ns/rm/doors/attribute#"
   xmlns:rm="http://jazz.net/ns/rm#"
   xmlns:rm_property="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/urn:rational::1-51929a740f221131-M-0000002a/types/"
   xmlns:acp="http://jazz.net/ns/acp#"
   xmlns:oslc="http://open-services.net/ns/core#"
   xmlns:foaf="http://xmlns.com/foaf/0.1/"
   xmlns:oslc_rm="http://open-services.net/ns/rm#">
 <oslc_rm:Requirement rdf:about="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/urn:rational::1-51929a740f221131-O-21-0000002a">
   <dcterms:contributor>
     <foaf:Person>
       <foaf:name>Administrator</foaf:name>
     </foaf:Person>
   </dcterms:contributor>
   <oslc_rm:implementedBy rdf:resource="http://google.com"/>
   <doorsAttribute:modifiedBy rdf:parseType="Literal">Administrator</doorsAttribute:modifiedBy>
   <doorsAttribute:createdBy rdf:parseType="Literal">Administrator</doorsAttribute:createdBy>
   <doorsAttribute:createdOn rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
   >2013-10-14</doorsAttribute:createdOn>
   <rm:primaryText rdf:parseType="Literal">My Eclipse Lyo CREATED Primary Text</rm:primaryText>
   <doorsAttribute:absoluteNumber rdf:datatype="http://www.w3.org/2001/XMLSchema#integer"
   >21</doorsAttribute:absoluteNumber>
   <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
   >2013-10-14T14:22:46Z</dcterms:modified>
   <dcterms:title rdf:parseType="Literal">21: My Eclipse Lyo CREATED Primary Text</dcterms:title>
   <dcterms:creator>
     <foaf:Person>
       <foaf:name>Administrator</foaf:name>
     </foaf:Person>
   </dcterms:creator>
   <doorsAttribute:objectShortText rdf:parseType="Literal"></doorsAttribute:objectShortText>
   <rm_property:attrDef-8 rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
   >2013-10-14T14:22:46Z</rm_property:attrDef-8>
   <oslc:serviceProvider rdf:resource="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/discovery/service/urn:rational::1-51929a740f221131-M-0000002a"/>
   <doorsAttribute:objectHeading rdf:parseType="Literal"></doorsAttribute:objectHeading>
   <oslc:shortTitle rdf:parseType="Literal">21: My Eclipse Lyo CREATED Primary Text</oslc:shortTitle>
   <doorsAttribute:modifiedOn rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
   >2013-10-14</doorsAttribute:modifiedOn>
   <oslc:instanceShape rdf:resource="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/oslc/shape/requirement/urn:rational::1-51929a740f221131-M-0000002a"/>
   <doorsAttribute:createdThru rdf:resource="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/urn:rational::1-51929a740f221131-M-0000002a/types/attrDef-10#1"/>
   <dcterms:description rdf:parseType="Literal"></dcterms:description>
   <dcterms:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
   >21</dcterms:identifier>
   <dcterms:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime"
   >2013-10-14</dcterms:created>
   <acp:accessControl rdf:resource="https://sse-doors.rcsnl.ams.nl.ibm.com:8443/dwa/rm/acp/urn:rational::1-51929a740f221131-F-00000000/gFgcK1req0%252BQ5gE6yE5YsEZZcDI%253D%250A"/>
 </oslc_rm:Requirement>
</rdf:RDF>




 

---


Hi Clyde,

thanks for the clue, but unfortunately I can't find any attribute that indicates a URL. How is the attribute usually called?
I have a set of "custom" properties and some "system" properties that are "absolute number", "created by", "created on", "last modified by" and "last modified on". In the set of the custom properties there is one called "requirements reference" but this a no value in case of all requirements.

Best,
Marcus
 
Gesendet: Mittwoch, 22. Januar 2014 um 16:57 Uhr
Von: "Clyde D Icuspit" <cdicuspi@xxxxxxxxxx>
An: "Lyo project developer discussions" <lyo-dev@xxxxxxxxxxx>
Cc: lyo-dev-bounces@xxxxxxxxxxx
Betreff: Re: [lyo-dev] Lyo OSLC Client for Rational DOORS
Hi Marcus,

In the DWA GUI, lower right-hand corner under Attributes, the URL property value is usually displayed. You can copy the URL of the selected requirement from there and temporarily hard-code it in a GET request to get the RDF representation of that requirement. 

Sincerely,
Clyde Icuspit
____________________________________________________________
Business Partner ISV Technical Enablement IBM Certified I/T Specialist L2 IBM Rational Software tel: 617.693.7417 email: cdicuspi@xxxxxxxxxx	Ready for IBM Rational Software Partner Program Ready for IBM Rational partner plug-ins


_______________________________________________ lyo-dev mailing list lyo-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/lyo-dev

_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/lyo-dev

_______________________________________________ lyo-dev mailing list lyo-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/lyo-dev

_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/lyo-dev


_______________________________________________ lyo-dev mailing list lyo-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/lyo-dev

_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/lyo-dev