Richard, can you elaborate on why this is expected given cxf is not full jaxws 2.2 compliant yet? afaik Andrew was running this against jbossws-cxf before the 3.3.0 update (hence with cxf 2.2.5), right?
Andrew, ok, perhaps you can provide a testcase or send me a deployment I can try to reproduce the issue with? I'd also check what happens with cxf 2.2.5...