Introduce "forTest" subclass to clean up Transaction Participant's public interface

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The Transaction Participant exposes several methods with names containing "forTest". We can consider introducing a subclass to test functionality as a part of the class type but not pollute the public interface with methods that will not be used in production.

            Assignee:
            Unassigned
            Reporter:
            Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: