Atom REST interface - 7.1

Talend ESB Infrastructure Services Configuration Guide

EnrichVersion
7.1
EnrichProdName
Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for ESB
Talend Real-Time Big Data Platform
EnrichPlatform
Talend ESB
Talend Runtime
task
Design and Development
Installation and Upgrade

The Atom REST interface is defined as follows:

   @GET
   @Produces({ "application/atomserv+xml" })
   Response getAtomApplicationDocument();

   @GET
   @Path("{type}")
   @Produces({ "application/atom+xml" })
   ResourceCollection getResources(@PathParam("type") ResourceType type);

   @GET
   @Path("{type}/{id}")
   @Produces({ "application/atom+xml;type=entry" })
   Resource getResource(@PathParam("type") ResourceType type, 
      @PathParam("id") String id);

   @POST
   @Path("{type}")
   @Consumes({ "application/atom+xml;type=entry" })
   @Produces({ "application/atom+xml;type=entry" })
   @CreateResourceResponse
   Resource createResource(@PathParam("type") ResourceType type, 
      Resource resource);

   @PUT
   @Path("{type}/{id}")
   @Consumes({ "application/atom+xml;type=entry" })
   @Produces({ "application/atom+xml;type=entry" })
   void updateResource(@PathParam("type") ResourceType type, 
      @PathParam("id") String id, Resource resource);

   @DELETE
   @Path("{type}/{id}")
   void deleteResource(@PathParam("type") ResourceType type, 
      @PathParam("id") String id);


   @GET
   @Path("{type}/{id}/content")
   @Produces({ "application/xml" })
   Response getResourceContent(@PathParam("type") ResourceType type, 
      @PathParam("id") String id);

   @PUT
   @Path("{type}/{id}/content")
   @Consumes({ "application/xml" })
   void updateResourceContent(@PathParam("type") ResourceType type, 
      @PathParam("id") String id, InputStream body);

The XACML Registry Atom REST interface is very similar to the Talend Registry Service. Instead of the WSDL and Policy resource types, the XACML Registry supports resource types ROOT (for roles) and XACML (for access control definitions), but the provided service operations are the same.

The XACML Registry content model is defined analogously to the Talend Registry Content model. The XACML Registry uses Jackrabbit to persist policies. The Registry root has two subnodes, one for roles (labeled "ROOT") and one for access control definitions referenced by the roles (labeled "XACML"). Other than Talend Registry these subnodes define flat sets of policies, they are itself not hierarchical. A JCR relation between roles and access control definitions is supported by the XACML registry REST frontend but not used by the current PDP implementation.

The XACML Registry Domain Model is shown as below: