[
https://issues.apache.org/jira/browse/UIMA-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365172#comment-14365172
]
Burn Lewis commented on UIMA-4285:
----------------------------------
The JD's ducc-side also has this problem ... apparently comes from the
IUimaPipelineAEComponent class which is part of the OR publication and includes
org.apache.uima.analysis_engine.AnalysisEngineManagement.State
Since this is essentially an internal communication between ducc daemons there
should be no problem leaving uima-core in the ducc classpaths as the object
doesn't cross the class-loader barrier (JMX must be safely marshalling it from
user to ducc-side)
> DUCC JP container for a service should not need UIMA
> ----------------------------------------------------
>
> Key: UIMA-4285
> URL: https://issues.apache.org/jira/browse/UIMA-4285
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Burn Lewis
> Priority: Minor
>
> When starting a DUCC service the JP is using a UIMA class but the intent was
> to isolate all UIMA use to the user container.
> java.lang.ClassNotFoundException:
> org.apache.uima.analysis_engine.AnalysisEngineManagement
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
