Remove unused OperationContextBinding test wrappers

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Java Drivers
    • None
    • None
    • None
    • None
    • None
    • None

      Before the CSOT refactoring, SessionContext was applied in tests (ClusterFixture) at the binding level via SessionBinding / AsyncSessionBinding. The CSOT refactoring (JAVA-5640, PR #1781) decoupled OperationContext from Binding and removed SessionBinding / AsyncSessionBinding from the binding creation path in ClusterFixture. However, the pre-existing OperationContextBinding / AsyncOperationContextBinding wrappers were left in place.

      They carry an OperationContext with SessionContext attached, but nothing downstream consumes it (getOperationContext() is never called). As a result, SessionContext is no longer being applied to test operations.

      ClusterFixture also contains several overloads (getBinding(TimeoutSettings), getBinding(OperationContext), getAsyncBinding(OperationContext), createNewOperationContext(TimeoutSettings), etc.) that exist primarily to support these wrappers.

      Acceptance Criteria

      • OperationContextBinding and AsyncOperationContextBinding are deleted.
      • SessionContext is applied at operation execution time in executeSync / executeAsync.
      • All affected tests are updated and passing.

            Assignee:
            Slav Babanin
            Reporter:
            Slav Babanin
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: