Difference between revisions of "Registry-Publisher"

From Gcube Wiki
Jump to: navigation, search
(Library Implementation Notes)
(Sample Usage)
Line 17: Line 17:
 
== Publishing a profile ==
 
== Publishing a profile ==
 
In order to publish a Resource profile the Registry-Publisher contacts the IS-Registry service of the current scope by invoking its appropriate operations. The following operation can be used to manage profiles on the IS:
 
In order to publish a Resource profile the Registry-Publisher contacts the IS-Registry service of the current scope by invoking its appropriate operations. The following operation can be used to manage profiles on the IS:
 
== Sample Usage ==
 
 
 
 
=== GCUBEResources (RegistryPublisher interface) ===
 
 
 
 
==== How to publish a GCUBEResource ====
 
 
 
 
==== How to update a GCUBEResource ====
 
 
 
 
==== How to remove a GCUBEResource ====
 
 
 
 
=== XML Documents (RegistryPublisher interface) ===
 
 
 
 
==== Publishing an XML Document ====
 
 
 
 
==== Removing an XML Document ====
 

Revision as of 12:22, 12 April 2013


In conjunction with the IC-Client, the Registry-Publisher represents the mediation layer gCube Services, based on FWS, will rely on to interact with the Information Service as a whole.



Design

The Registry-Publisher is a Java library providing the implementation of two interfaces (RegistryPublisher and ScopedPublisher) that allow services to publish GCUBEResource as well as their state in the IS.

More specifically:

  • by implementing the org.gcube.common.core.informationsystem.publisher.RegistryPublisher interface, the library allows gCube services to publish GCUBEResources and instances' states as of the gCube Resource Model defined in Common-gcore-resources;
  • by implementing the org.gcube.informationsystem.publisher.ScopedPublisher interface, the library allows gCube services to publish GCUBEResources in multi scope way;

Interface

Publishing a profile

In order to publish a Resource profile the Registry-Publisher contacts the IS-Registry service of the current scope by invoking its appropriate operations. The following operation can be used to manage profiles on the IS: