repository-extension-services issueshttps://gitlab.amherst.edu/acdc/repository-extension-services/-/issues2017-09-24T06:33:33-04:00https://gitlab.amherst.edu/acdc/repository-extension-services/-/issues/16Review JNDI-based naming conventions for services2017-09-24T06:33:33-04:00acoburnReview JNDI-based naming conventions for servicesWe currently have a number of names for the `osgi.jndi.service.name` values: acrepobroker, inference, jsonld, etc. It would be good to come up with some naming conventions -- maybe there are patterns for this? Should the names include `e...We currently have a number of names for the `osgi.jndi.service.name` values: acrepobroker, inference, jsonld, etc. It would be good to come up with some naming conventions -- maybe there are patterns for this? Should the names include `edu.amherst.acdc` or `acrepo`?
This applies to all of the `acrepo-services-*` modules, which then are used by many of the `acrepo-exts-*` and `acrepo-connector-*` modules.acoburnacoburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/issues/10Create a generic activemq service2017-09-24T06:33:33-04:00acoburnCreate a generic activemq serviceThis would be shared across all of the `acrepo-connector-*` modules.
This can be used as inspiration: https://github.com/fcrepo4-exts/fcrepo-camel-toolbox/tree/master/fcrepo-service-activemqThis would be shared across all of the `acrepo-connector-*` modules.
This can be used as inspiration: https://github.com/fcrepo4-exts/fcrepo-camel-toolbox/tree/master/fcrepo-service-activemqbseegerbseeger