Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • repository-extension-services repository-extension-services
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • acdc
  • repository-extension-servicesrepository-extension-services
  • Issues
  • #16

Closed
Open
Created Jul 11, 2016 by acoburn@acoburnGuest

Review JNDI-based naming conventions for services

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.

Assignee
Assign to
Time tracking