MTOM/adressing changes not applied properly

Mingjian Jin:
when I change the mtom policy to addresing policy, the wsdl has been changed into mtom without any addressing info. But when the client talks to the the web service, it complains the addressing problem. I am not sure the problem is about the cm, I guess maybe the addressing feature was cached or controlled by other metro components. So, just FYI.
#### Affected Versions
[2.1]

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

Start by reproducing the MTOM-to-addressing policy change described for Metro 2.1 and compare the generated WSDL with the addressing behavior observed by the client. Trace which Metro components handle policy caching or addressing, then confirm that the generated WSDL and client interaction consistently reflect the selected policy.

Written by the indexing model from the issue text.