Uploaded image for project: 'UIMA'
  1. UIMA
  2. UIMA-5280 UIMA-AS V3: Redesign to simplify embedding in applications
  3. UIMA-5501

UIMA-AS V3: Refactor code to support deploying services without a broker

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • 3.0.1AS
    • Async Scaleout
    • None

    Description

      Current code supports JMS-base communication between UIMA-AS client and a service. When both are co-located in the same process broker should not be needed and replaced with a "direct" communication using java based queues.
      The code refactoring is needed to support both jms and direct communication. The communication choice will be defined in the DD by

      <deployment protocol="[jms,java]" provider="[activemq,java]">

      If the protocol=java and provider=java, the new UIMA-AS will use direct communication(java) between client and a service. If the protocol=jms and provider=activemq, the code will function as it currently does using AMQ for transport between client and a service.

      The DDs should use a placeholder ${Protocol} and ${Provider} to simplify deployment and promote reuse. Except for the DD changes, the user code should not be impacted by this change as most of it is internal. The code will instantiate appropriate builder class which would create components necessary to support communication model chosen in the DD.

      Attachments

        Activity

          People

            cwiklik Jaroslaw Cwiklik
            cwiklik Jaroslaw Cwiklik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: