Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve deployment in OSGi environments #225

Closed
reckart opened this issue Jul 28, 2022 · 0 comments
Closed

Improve deployment in OSGi environments #225

reckart opened this issue Jul 28, 2022 · 0 comments
Assignees
Labels
⭐️ Enhancement Improvement or new feature for users
Milestone

Comments

@reckart
Copy link
Member

reckart commented Jul 28, 2022

Is your feature request related to a problem? Please describe.
UIMA does not work well in OSGi environments where JCas classes are distributed across different bundles. Cf. https://issues.apache.org/jira/browse/UIMA-6468

UIMA assume that it has a "global view" on all JCas classes that exist outside PEARs. With PEARs we have a strong isolation and the PEARs should provide their own copies of the JCas classes. But in OSGi, the situation is much more heterogeneous.

Describe the solution you'd like
We probably need a mechanism through which OSGi bundles can publish their JCas classes so that the UIMA framework can find and load them all. This should enable the "global view" that the JCas implementation assumes. Of course, in this situation there must never be the case that the same JCas class is provided by multiple bundles. But OSGi mandates anyway that one packages is always in one bundle.

Describe alternatives you've considered
Not sure if there are alternatives...

Additional context
Similar problem exists for type-system-descriptor detection in uimaFIT.

@reckart reckart added the ⭐️ Enhancement Improvement or new feature for users label Jul 28, 2022
@reckart reckart added this to the 3.4.0 milestone Jul 28, 2022
@reckart reckart self-assigned this Jul 28, 2022
reckart added a commit that referenced this issue Jul 28, 2022
- Update to UIMA Parent POM 16-SNAPSHOT
- Add OSGi metadata to several modules using the maven-bundle-plugin
reckart added a commit that referenced this issue Jul 28, 2022
- Update to UIMA Parent POM 16-SNAPSHOT
- Add OSGi metadata to several modules using the maven-bundle-plugin
reckart added a commit that referenced this issue Aug 17, 2022
- Make JCas SPI discovery available in OSGi
reckart added a commit that referenced this issue Aug 25, 2022
…-OSGi-environments

Issue #225: Improve deployment in OSGi environments
reckart added a commit that referenced this issue Aug 26, 2022
- SPI resolution should be optional
reckart added a commit that referenced this issue Aug 26, 2022
…-OSGi-environments

Issue #225: Improve deployment in OSGi environments
reckart added a commit that referenced this issue Sep 16, 2022
- Turned uimaj-cpe into a fragment of uimaj-core because uimaj-core needs access to the packages of uimaj-cpe, e.g. because it accesses classes like CpeInclude via reflection in its factories
reckart added a commit that referenced this issue Sep 16, 2022
…vironments

Issue #225: Improve deployment in OSGi environments
reckart added a commit that referenced this issue Oct 14, 2022
…manceTuning.properties

* main: (74 commits)
  Issue #252: Potential failure to look up FsGenerator3 in OSGI-like contexts
  Issue #225: Improve deployment in OSGi environments
  Issue #226: Provide SPI interfaces to locate descriptors and JCas classes
  Issue #226: Provide SPI interfaces to locate descriptors and JCas classes
  Issue #247 - RelativePathResolver should consider TCCL
  #245 - Utility method for loading type systems in SPI providers
  #245 - Utility method for loading type systems in SPI providers
  #245 - Utility method for loading type systems in SPI providers
  #245 - Utility method for loading type systems in SPI providers
  Issue #225: Improve deployment in OSGi environments
  Issue #225: Improve deployment in OSGi environments
  Issue #226: Provide SPI interfaces to locate descriptors
  Issue #226: Provide SPI interfaces to locate descriptors
  [UIMA-6481] Enable issue management in GitHub repos
  Issue #226: Provide SPI interfaces to locate descriptors
  Issue #226: Provide SPI interfaces to locate descriptors
  Issue #228 - Move the UimaDecompiler class
  Issue #226: Provide SPI interfaces to locate descriptors
  Issue #228 - Move the UimaDecompiler class
  Issue #230: Remove version overrides in Maven plugin modules
  ...
@reckart reckart closed this as completed Nov 24, 2022
reckart added a commit that referenced this issue Jan 11, 2023
…ipse-plugins-during-release-builds

* main: (94 commits)
  No issue: Remove Jira line from PR template - we do not use Jira anymore.
  #270 - Update dependencies
  #270 - Update dependencies
  #267 - UIMA Log4jLogger_impl not compatible with log4j 2.18.0+
  No issue. Adjust jira legacy module version.
  [maven-release-plugin] prepare for next development iteration
  [maven-release-plugin] prepare release uimaj-3.3.1
  Issue #258: Apache UIMA Java SDK 3.3.1 release
  Issue #258: Apache UIMA Java SDK 3.3.1 release
  Issue #258: Apache UIMA Java SDK 3.3.1 release
  Issue #260: Issues-fixed report for GitHub and Jira
  Issue #258: Apache UIMA Java SDK 3.3.1 release
  Issue #258: Apache UIMA Java SDK 3.3.1 release
  Issue #258: Apache UIMA Java SDK 3.3.1 release
  Issue #255: File handle leak accessing performanceTuning.properties
  Issue #252: Potential failure to look up FsGenerator3 in OSGI-like contexts
  Issue #225: Improve deployment in OSGi environments
  Issue #226: Provide SPI interfaces to locate descriptors and JCas classes
  Issue #226: Provide SPI interfaces to locate descriptors and JCas classes
  Issue #247 - RelativePathResolver should consider TCCL
  ...

% Conflicts:
%	uimaj-parent/pom.xml
reckart added a commit that referenced this issue Jan 20, 2023
…-a-PEAR-context

* main: (91 commits)
  Issue #283: Update issue report generation
  Issue #283: Update issue report generation
  [UIMA-6436] Move maintainer documentation from website into maintainer guide
  [UIMA-6436] Move maintainer documentation from website into maintainer guide
  [UIMA-6436] Move maintainer documentation from website into maintainer guide
  Issue #265: Unable to release without auto-staging
  Issue #267 - UIMA Log4jLogger_impl not compatible with log4j 2.18.0+
  Issue #268: UIMA components log and then re-throw exceptions which usually leads to errors being logged twice
  Issue #275: Improved error message made it even more misleading
  Issue #266: Unable to install UIMA 3.3.1 Eclipse Plugins in Eclipse 2022-09
  No issue: Remove Jira line from PR template - we do not use Jira anymore.
  #270 - Update dependencies
  #270 - Update dependencies
  #267 - UIMA Log4jLogger_impl not compatible with log4j 2.18.0+
  No issue. Adjust jira legacy module version.
  Issue #252: Potential failure to look up FsGenerator3 in OSGI-like contexts
  Issue #225: Improve deployment in OSGi environments
  Issue #226: Provide SPI interfaces to locate descriptors and JCas classes
  Issue #226: Provide SPI interfaces to locate descriptors and JCas classes
  Issue #247 - RelativePathResolver should consider TCCL
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⭐️ Enhancement Improvement or new feature for users
Projects
None yet
Development

No branches or pull requests

1 participant