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/14Broadcast Extension Test fails with extra messages2017-09-24T06:33:33-04:00bseegerBroadcast Extension Test fails with extra messagesOne of the broadcast extension integration tests fails with extra messages on each of the queues. It seems that there are probably JMS messages on the queue from other tests.
A @Before function could be created to clear the queue befor...One of the broadcast extension integration tests fails with extra messages on each of the queues. It seems that there are probably JMS messages on the queue from other tests.
A @Before function could be created to clear the queue before hand. bseegerbseegerhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/issues/12Revamp acrepo-exts-template to use different templates2017-09-24T06:33:33-04:00bseegerRevamp acrepo-exts-template to use different templatesFrom comments in https://gitlab.amherst.edu/acdc/repository-extension-services/issues/4#note_739
The idea is to revamp this module to work with any supplied template. There would be a URL param that points to a template, so it's fle...From comments in https://gitlab.amherst.edu/acdc/repository-extension-services/issues/4#note_739
The idea is to revamp this module to work with any supplied template. There would be a URL param that points to a template, so it's flexible. Perhaps the default could be a mustache template, but others could be supplied via this param. Or we could have a cfg variable that has the URL of the default (mustache) and that could be overridden by a URL param, if the user wants.bseegerbseeger