You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, A single Package-info.java class is produced for each adaptor.
Instead, such a class should exist for each package that contains OSLC resource classes.
This problem is most obvious when the adaptor is generated into a project different from that of the domain classes. Then the package-info.java classes is even produced in the wrong project.
To reproduce, setup a project as suggest above. Then try to do a GET on a resource, with format application/json. This results in an internal 500 error.
Exception is: throw new OslcCoreMissingNamespaceDeclarationException(namespace); (See JsonHelper class, in oslc4j-json4j-provider)
A less acute error, which nevertheless illustrates the problem is when doing a GET with say text/turtle. The response will lack the prefixes that ought to have been declared in the package-info class. Instead, the complete URIs are prointed in the body of the response.
The text was updated successfully, but these errors were encountered:
Currently, A single Package-info.java class is produced for each adaptor.
Instead, such a class should exist for each package that contains OSLC resource classes.
This problem is most obvious when the adaptor is generated into a project different from that of the domain classes. Then the package-info.java classes is even produced in the wrong project.
To reproduce, setup a project as suggest above. Then try to do a GET on a resource, with format application/json. This results in an internal 500 error.
Exception is: throw new OslcCoreMissingNamespaceDeclarationException(namespace); (See JsonHelper class, in oslc4j-json4j-provider)
A less acute error, which nevertheless illustrates the problem is when doing a GET with say text/turtle. The response will lack the prefixes that ought to have been declared in the package-info class. Instead, the complete URIs are prointed in the body of the response.
The text was updated successfully, but these errors were encountered: