eclipse-ee4j / eclipse-ee4j/metro-wsit
Make get methods in PolicyMapKey package-private again
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 1
Description
Right now the getOperation/getPort/getService methods in
com.sun.xml.ws.policy.PolicyMapKey are publicly readable so that the WS-TX
implementation can determine to which operation a feature is attached. We should
introduce features that can be tied to operations and messages without having to
expose methods in PolicyMapKey.
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[current]
Source: [https://github.com/javaee/metro-wsit/issues/1462](https://github.com/javaee/metro-wsit/issues/1462)
Author: glassfishrobot
Contributor guide
Research direction
Start by inspecting com.sun.xml.ws.policy.PolicyMapKey and the WS-TX implementation that calls getOperation, getPort, and getService. Trace how features are currently tied to operations and messages, then determine the project-supported replacement for exposing those values. Done means the methods are package-private again while WS-TX can still identify the relevant operation and message attachments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100