How to define custom Resource Class for Requirement Folder
Hi All,
I have created a custom Resource class "Folder" in Lyo client project.
This class is used to de-serialize GET response on folder artifact.
String resourceURL="https://server:port/rm/folders/_c60fc18a132a467db44748c27d4b0e0b";
ClientResponse response = jfaClient.getResource(resourceURL,OSLCConstants.CT_RDF);
Folder fol = response.getEntity(Folder.class);
But i get null folder object.
Below is my folder resource class ::
@OslcNamespace(RmConstants.JAZZ_RM_NAV_NAMESPACE)
@OslcResourceShape(title = "Folder Resource Shape", describes = JazzConstant.TYPE_REQUIREMENTFOLDER)
public class Folder extends AbstractResource{
private URI subfolders;
private String title;
private URI parent;
private String description;
private URI serviceProvider;
public Folder() {
super();
}
public Folder(final URI about) {
super(about);
}
@OslcDescription("The base URI to use for queries. Queries are invoked via HTTP GET on a query URI formed by appending a key=value pair to the base URI, as described in Query Capabilities section")
@OslcOccurs(Occurs.ExactlyOne)
@OslcPropertyDefinition(RmConstants.JAZZ_RM_NAV_NAMESPACE+ "subfolders")
@OslcReadOnly
@OslcTitle("Sub Folders")
public URI getSubfolders() {
return subfolders;
}
@OslcDescription("Title (reference: Dublin Core) or often a single line summary of the resource represented as rich text in XHTML content.")
@OslcOccurs(Occurs.ExactlyOne)
@OslcPropertyDefinition(OslcConstants.DCTERMS_NAMESPACE + "title")
@OslcTitle("Title")
@OslcValueType(ValueType.XMLLiteral)
public String getTitle() {
return title;
}
@OslcDescription("The scope of a resource is a URI for the resource's OSLC Service Provider.")
@OslcPropertyDefinition(OslcConstants.OSLC_CORE_NAMESPACE + "serviceProvider")
@OslcRange(OslcConstants.TYPE_SERVICE_PROVIDER)
@OslcTitle("Service Provider")
public URI getServiceProvider() {
return serviceProvider;
}
@OslcDescription("Descriptive text (reference: Dublin Core) about resource represented as rich text in XHTML content.")
@OslcPropertyDefinition(OslcConstants.DCTERMS_NAMESPACE + "description")
@OslcTitle("Description")
@OslcValueType(ValueType.XMLLiteral)
public String getDescription() {
return description;
}
@OslcDescription("Parent Folder of this folder Artifact")
@OslcOccurs(Occurs.ExactlyOne)
@OslcPropertyDefinition(RmConstants.JAZZ_RM_NAV_NAMESPACE+ "parent")
@OslcReadOnly
@OslcTitle("Parent")
public URI getParent() {
return parent;
}
public void setTitle(final String title) {
this.title = title;
}
public void setSubFolders(final URI subfolders) {
this.subfolders = subfolders;
}
public void setDescription(final String description) {
this.description = description;
}
public void setParent(final URI parent) {
this.parent = parent;
}
public void setServiceProvider(final URI serviceProvider) {
this.serviceProvider = serviceProvider;
}
}
|
Accepted answer
I suggest you do some debugging to find out more. The Lyo project provides most of the source code for you to debug.
I have spent some time on this and the key thing I have found out is that you need to define the class as "folder", not "Folder". The reason for that is the class name will be part of the "qualified name", which will be used to extract the RDF+XML content. If we use "Folder" as the class name, the qualified name will become "http://jazz.net/ns/rm/navigation#Folder", which is incorrect. I do not get any further after changing the class name because I get OOM instead, which is much harder to debug. Also not that the <nav:parent> property is actually defined in the Requirement class, and is accessed as an "extended property". Maybe it has been done this way for a reason? Amit Kumar selected this answer as the correct answer
|
3 other answers
Donald,
Having been smacked by the same exception, it looks like there is a latent problem in determineErrorMediaType that leads to UndeclaredThrowableException throw loop. This is very hard to diagnose because it blows out Eclipse's stack and usually ends up crashing Eclipse and the debugging session.
This determineErrorMediaType code gets called after other code has detected something unexpected in the response entity content and is merely trying to construct an error message.
Exception in thread "main" java.lang.reflect.UndeclaredThrowableExceptionAs I step through one debugging session for this issue today, I become trained that the errors that often lead to the buildBadResponse code include:
|
Hello Amit
Can you provide some additional information around the Lyo marshalling (eg logging)? Can you confirm that the server is responding with application/rdf+xml document that looks correct? It should be something like shown below. <rdf:RDF ... <nav:folder rdf:about="https://greenfront.edinburgh.uk.ibm.com:9444/rdm/folders/_a42a43595c3c40bfb6700f3fd0c33090"> <dcterms:title>_AMR System Requirements Specification artifacts</dcterms:title> <dcterms:description></dcterms:description> |
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.