Eclipse Community Forums: Lyo » DoorsOauthSample - Unable to get the Entity of the Resource Shape for Requirements

Home » Eclipse Projects » Lyo » DoorsOauthSample - Unable to get the Entity of the Resource Shape for Requirements(Unable to get the Entity of the Resource Shape for Requirements)

Show: Today's Messages :: Show Polls :: Message Navigator

DoorsOauthSample - Unable to get the Entity of the Resource Shape for Requirements [message #1124001]

Thu, 03 October 2013 00:53

Rachita Sakibanda
Messages: 4
Registered: September 2013

Junior Member

Hi,

I am currently going through the DoorsOauthSample.java example to understand how it works and have come across a problem where I am not able to get the entity details for Resource Shape (this process occurs in RmUtil.java).

In DoorsOauthSample there are lines that gets the catalog, service provider, requirement creation factory and then requirement shape url. Its the last part where the error is happening. The lines where error is occuring is as follows:

[typeURI value is ......./dwa/rm/oslc/shape/requirement......, which looks correct]

-> response = client.getResource(typeURI.toString(),OSLCConstants.CT_RDF);
-> ResourceShape resourceShape = response.getEntity(ResourceShape.class);

When the first line runs, the reponse has some entity value but the message displayed is "Internal Server Error" and the status is "500".

When the second line runs, the resourceShape value is set to null.

I just wanted to find out if any body else has had this problem with the DoorsOauthSample example and if so then would you be able to provide some help.

Thanks.

Your help would be much appreciated Smile

.

Kind Regards,
Rachita Sakibanda

Report message to a moderator

Re: DoorsOauthSample - Unable to get the Entity of the Resource Shape for Requirements [message #1124359 is a reply to message #1124001]

Thu, 03 October 2013 09:02

Maeve OReilly
Messages: 1
Registered: October 2013

Junior Member

Hi Rachita,

I did get it running with DOORS 9.5. I had trouble with earlier versions. You are passing a module name to it, not a project? These were my parameters:

-url link_to_dwa -user Administrator -password Password123 -project myModule

The -project is a bit confusing; it wants a module not a project.

I would also suggest you look in your <DOORS Web Access install>/server/festival/logs. There is pretty good logging for any OSLC requests there; might give you more detail. The logging level can be increased by going to festival/config and swapping the log4j.support with the log4j.xml and restarting DWA.

There was a defect with http 500s occurring after numerous OSLC requests. Restarting 'fixes' it. It is properly fixed in 9.5.1.2 so if all else fails, try that - I would give you link but I am not allowed. Google fix central site:ibm.com.

HTH,
Maeve

Report message to a moderator