Avoid Reestablishment of SC-Context in Multithreading case

Hello,

In multithreading cases we have problems attaching the holded established
authorisation in ws-trust and ws-security case with enabled SC.

1.)
In WS-Trust we cache the requester subject (of the response) and set it to the
dispatcher in another thread if needed. That works, but a ../trust/RST/SCT is
made at every business service call.

2.)
In 2 way ws-security SC case we cache the hole dispatcher object and set it back
from cache if needed. Works well and no ../trust/RST/SCT is made at every call,
but we do not think that this method should be the common way..

It would be nice when metro uses static cashes 

Best Greats from Berlin !
Andre
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[2.1]

Source: [https://github.com/javaee/metro-wsit/issues/1300](https://github.com/javaee/metro-wsit/issues/1300)
Author: glassfishrobot

Start by tracing the WS-Trust ../trust/RST/SCT creation path and the WS-Security dispatcher/requester-subject handling described in the issue. Compare the two multithreading approaches and determine the intended shared-context behavior; done means repeated business-service calls no longer recreate the security context while preserving correct authorization.

Written by the indexing model from the issue text.