Write a Karate/Postman Test to verify that OSGI plugins can be installed and then reloaded
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Parent Issue
https://github.com/dotCMS/core/issues/31185
Task
Issue Description:
Given the problem encountered in ticket 31185, where installing an OSGi plugin containing a REST resource caused our Jersey container to become unusable due to a recurring exception, we want to create a Karate or Postman test to ensure stability.
This will help confirm that our container remains stable even after multiple plugin lifecycle operations.
Proposed Objective
Same as Parent Issue
Proposed Priority
Priority 2 - Important
Acceptance Criteria
This test should validate that we can:
1. Install OSGi plugins,
2. Stop them,
3. Restart them, and
4. Verify that the Jersey container remains functional after a few consecutive cycles, properly serving content from other endpoints and maintaining expected behavior.
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Parent: #31604
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with parent issue #31185 and inspect existing Karate or Postman tests in the repository to find the supported entry points for OSGi lifecycle operations and Jersey endpoint checks. The test is done when it installs, stops, and restarts the plugin through several cycles and confirms that unrelated endpoints remain functional after each cycle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postman
- Domain
- backend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100