eclipse-ee4j / eclipse-ee4j/metro-wsit
Shared WS-RM Session across multiple endpoints
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 1
Description
We are using WS-Reliable Messaging to maintain a session between clients and web
services. It works well between a client an a single endpoints. A session is
created at the first call and re-used for each call.
What we need is to have the same WS-RM session used with multiple endpoints. For
a client, the session should be create on the first call to any endpoint and
then re-used for all calls to any endpoints.
We need this because we use the WS-RM session to store and retrieve an execution
context for the calls (through a custom LogicalHandler). This execution context
allow a client to define a base reference used to resolve references used as
calls parameters. Messages ordering across multiples endpoints is also needed.
PS: With Microsoft Windows Communication Foundation this can be achieved be
using a single WSHttpBinding to create multiples ClientBase instances.
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[current]
Source: [https://github.com/javaee/metro-wsit/issues/807](https://github.com/javaee/metro-wsit/issues/807)
Author: glassfishrobot
Contributor guide
Research direction
No implementation files, tests, or entry points are named. Start by tracing how WS-RM sessions are created and associated with client endpoints, then identify how the custom LogicalHandler receives execution context. Done means one client can reuse a WS-RM session, shared context, and message ordering across multiple endpoints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100