Context Navigation

Changes between Version 20 and Version 21 of VirtualCollectionRegistry

Timestamp:: 08/26/14 14:22:03 (10 years ago)
Author:: Twan Goosen
Comment:: some fixes in technical REST section

Legend:

: Unmodified
: Added
: Removed
: Modified

VirtualCollectionRegistry

-                      v20
+                      v21
 Two ''!BodyWriter'' classes are implemented and registered, taking care of the '''rendering''' of !VirtualCollection object as CMDI or XML/JSON respectively, by means of different methods of the (injected) ''!VirtualCollectionMarshaller'' service. This way, a single method in ''!VirtualCollectionResource'' can handle these various serialisation options (depending on the HTTP Accept header in the client request). An additional method handles requests accepting HTML by returning a redirect ('see other') response pointing to the collection details page of the Wicket UI.
 The CMDI output is generated by marshalling instances of the classes generated by the JAX-B Maven plugin at build time (XJC), based on the [http://catalog.clarin.eu/ds/ComponentRegistry/rest/registry/profiles/clarin.eu:cr1:p_1404130561238/xsd VirtualCollection profile schema], a copy of which is included in the sources.
+The '''CMDI output''' is generated by marshalling instances of the classes generated by the JAX-B Maven plugin at build time (XJC), based on the [http://catalog.clarin.eu/ds/ComponentRegistry/rest/registry/profiles/clarin.eu:cr1:p_1404130561238/xsd VirtualCollection profile schema], a copy of which is included in the sources.
 The collections space can be queried by means of a domain specific query language, as described in the [source:/VirtualCollectionRegistry/trunk/VirtualCollectionRegistry/doc/Protocol.txt  REST documentation]. The grammar is defined in the file [source:/VirtualCollectionRegistry/trunk/VirtualCollectionRegistry/src/main/jjtree/eu/clarin/cmdi/virtualcollectionregistry/query/QueryParser.jjt QueryParser.jjt]. The ''javacc-maven-plugin'' generates the parser at build time (with the JJTree preprocessor). Query string (as optional GET parameters) are passed from the REST resources to the ''VirtualCollectionRegistry'' service, which uses a static method to get it parsed into a ''ParsedQuery'' object, which in turn is used to obtain JPA query objects that can be used to retrieve concrete results.
+The collections space can be queried by means of a domain specific '''query language''', as described in the [source:/VirtualCollectionRegistry/trunk/VirtualCollectionRegistry/doc/Protocol.txt  REST documentation]. The grammar is defined in the file [source:/VirtualCollectionRegistry/trunk/VirtualCollectionRegistry/src/main/jjtree/eu/clarin/cmdi/virtualcollectionregistry/query/QueryParser.jjt QueryParser.jjt]. The ''javacc-maven-plugin'' generates the parser at build time (with the JJTree preprocessor). Query strings (as optional GET parameters) are passed from the REST resources to the ''VirtualCollectionRegistry'' service, which uses a static method to get it parsed into a ''!ParsedQuery'' object, which in turn is used to obtain JPA query objects that can be used to retrieve concrete results.
 More info: