1. Building your own plugin

Catalog QT allows to integrate numerous data sources in order to populate it with data. At the moment two data sources are supported:

  • MDSPlus files
  • UDA based data sources

The way of choosing proper data source handler (plugin) is based o URI's schema. Schema defines which plugin will be used for populating data described by given URI.

Example of mapping between Java classes and URI's schema

# Server requires mapping definition inside file
server/catalog-ws-server/src/main/resources/uri-mapping.properties

# Client application (e.g. UpdateProcess) requires mapping definition inside file
client/catalog-ws-client/src/main/resources/uri-mapping.properties

mapping of URIs to proper plugin is done via bundle file

uda:pl.psnc.catalog.plugin.feed.imas.al.uda.UDAFeeder
mdsplus:pl.psnc.catalog.plugin.feed.imas.al.mdsplus.MDSPlusFeeder

This file defines which Java class (regardless of where it can be found - whether it's external JAR file or internal part of project) will handle given URI.


  • No labels