What I have now is this:
http://schemas.xmlsoap.org/soap/envelope/";>
http://docs.oasis-open.org/ws-sx/ws-trust/200512";
xmlns:ns2="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
xmlns:ns3="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit
Github user sberyozkin commented on the pull request:
https://github.com/apache/cxf/commit/d8edf3161f199d9c2fe3cb8314f6e98782bf22c5#commitcomment-14475026
Done
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proj
Github user lucaspouzac commented on the pull request:
https://github.com/apache/cxf/commit/d8edf3161f199d9c2fe3cb8314f6e98782bf22c5#commitcomment-14469030
Ok thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
Github user sberyozkin commented on the pull request:
https://github.com/apache/cxf/commit/d8edf3161f199d9c2fe3cb8314f6e98782bf22c5#commitcomment-14468992
Sure, was just a quick replacement of the map type. Will update shortly.
The whole thread proxy storage code will need to be rewri
Github user lucaspouzac commented on the pull request:
https://github.com/apache/cxf/commit/d8edf3161f199d9c2fe3cb8314f6e98782bf22c5#commitcomment-14468733
Why not use a ConcurrentHashMap ?
Regards
---
If your project is set up for it, you can reply to this email and have yo
