handlerscope testcase is (native) stack specific

The handlerscope testcase in framework is based on getting the handler's name and appending it to the payload. Unfortunately the API does not provide means of getting the name from an handler, so what the test does is stack specific (native).
We should have different handler classes used in that testcase.
From a first try on this, it seems to me this is also shadowing some issues with wildcards in port-name-pattern and multiple protocol with the cxf stack.