UIMA
  1. UIMA
  2. UIMA-2007

uima-as-osgi plugin is missing most of its content

    Details

      Description

      The jar for this is missing the actual code. There are also several unresolved [warnings] generated during the running of the Felix Bundle plugin.

        Activity

        Hide
        Marshall Schor added a comment -

        Joern - can you check if this fix is the right one?

        I think the 2.3.0 build for this was attempting to have this have the jars for the 3 uima-as add-on projects: uimaj-as-core, uimaj-as-jms, and uimaj-as-activemq, without any of their dependencies - is this correct?

        The 2.3.0 version had a Manifest element <Fragement-Host>org.apache.uima.runtime</Fragement-Host> which pointed to the core uima runtime. However, I noticed that the XML tag was misspelled. So, I'm guessing this never worked? I've changed the spelling Fragement -> Fragment.

        Finally, I noted that the <Bundle-SymbolicName> was missing, and a strange default was being taken. I added this element, and followed the same convention being used in other osgi things:

        <Bundle-SymbolicName>org.apache.uima.runtime.fragments.uimaas;singleton:=true</Bundle-SymbolicName>

        If this is breaks something, or is not right, let's change it.

        Show
        Marshall Schor added a comment - Joern - can you check if this fix is the right one? I think the 2.3.0 build for this was attempting to have this have the jars for the 3 uima-as add-on projects: uimaj-as-core, uimaj-as-jms, and uimaj-as-activemq, without any of their dependencies - is this correct? The 2.3.0 version had a Manifest element <Fragement-Host>org.apache.uima.runtime</Fragement-Host> which pointed to the core uima runtime. However, I noticed that the XML tag was misspelled. So, I'm guessing this never worked? I've changed the spelling Fragement -> Fragment. Finally, I noted that the <Bundle-SymbolicName> was missing, and a strange default was being taken. I added this element, and followed the same convention being used in other osgi things: <Bundle-SymbolicName>org.apache.uima.runtime.fragments.uimaas;singleton:=true</Bundle-SymbolicName> If this is breaks something, or is not right, let's change it.
        Hide
        Joern Kottmann added a comment -

        Actually I never got it working. I tried to run an uima as driver inside an OSGi server, but an uima as client of course needs to talk to ActiveMQ and that component had some strange OSGi issues, finally I gave up. I guess the situation is better today, I heard that the ActiveMQ team worked on fixing OSGi related bugs ... maybe it works now out of the box ?

        Show
        Joern Kottmann added a comment - Actually I never got it working. I tried to run an uima as driver inside an OSGi server, but an uima as client of course needs to talk to ActiveMQ and that component had some strange OSGi issues, finally I gave up. I guess the situation is better today, I heard that the ActiveMQ team worked on fixing OSGi related bugs ... maybe it works now out of the box ?
        Hide
        Marshall Schor added a comment -

        I can imagine this module at the 2.3.0 level never working, because of the misspelling of <fragement>. So it might work better now. But, it might also need to be able to access all of the activeMQ etc. dependencies, which is a very long list (and if included directly here, would make this a very big jar). I'll leave it as is for now, though. Please open another Jira if it needs to change.

        Show
        Marshall Schor added a comment - I can imagine this module at the 2.3.0 level never working, because of the misspelling of <fragement>. So it might work better now. But, it might also need to be able to access all of the activeMQ etc. dependencies, which is a very long list (and if included directly here, would make this a very big jar). I'll leave it as is for now, though. Please open another Jira if it needs to change.
        Hide
        Joern Kottmann added a comment -

        Sure, I hopefully will try it again one day, and then I will of course open jiras if it does not work. When I tried it the first time I could trace my issue back to an ActiveMQ issue which was not related to UIMA.

        Show
        Joern Kottmann added a comment - Sure, I hopefully will try it again one day, and then I will of course open jiras if it does not work. When I tried it the first time I could trace my issue back to an ActiveMQ issue which was not related to UIMA.

          People

          • Assignee:
            Marshall Schor
            Reporter:
            Marshall Schor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development