If this is indeed true, we probably should remove the uima-adapter-soap
Jar from the runtime-plugin build, since I couldn't run anyway. If
someone wanted to use SOAP within an OSGi bundle, they could always
build their own runtime bundle, including our uima-adapter-soap jar plus
the jars it depends on from axis.
What do others think?
-Marshall
Marshall Schor wrote:
UIMA's Soap implementation depends on having the axis classes (from
TomCat?) in its classpath. For normal UIMA deployments, this is
accomplished by adding the needed Jar to the classpath.
For Eclipse and RCP plugin environments, the user's plugin is
depending on the uima-ep-runtime plugin, which has our SOAP
implementation. Is it possible at run time to add to the classpath of
the uima-ep-runtime plugin the axis Jar?
If not, then I don't think our current Eclipse runtime plugin bundle
supports users who want to use the Soap APIs.
-Marshall
