Any chance you can try testing with the latest 2.2.10-SNAPSHOTs or the 2.3.0- SNAPSHOTs? As part of getting the 2.2 TCK passing, there were a LOT of ws- addressing issues fixed and some stuff around the reference params was included in that. I'd like to know if it's already fixed before digging too deep into it.
Dan On Tuesday 27 July 2010 11:37:19 am Vanore, Gregory wrote: > I'm having trouble getting WS-Addressing to fully function with the > Dispatch API. > > When I use a standard JAX-WS service proxy and enable the feature, no > problems. I get the WS-Addressing errata (To, Reply-To, etc.) in the > SOAP header as well as the reference parameters from the EPR. > > When I use the dispatch API (payload mode) to the same EPR, I only get > the To, Reply-To, and other such WS-Addressing elements - but the > reference parameters from the EPR are *not* copied into the SOAP header. > > Anyone else experience this? -- Daniel Kulp [email protected] http://dankulp.com/blog
