On Monday, August 08, 2011 6:20:12 PM Philippe Merle wrote: > Hi Dan, > > Le 08/08/11 18:09, Daniel Kulp a écrit : > > On Saturday, August 06, 2011 2:59:00 AM Philippe Merle wrote: > >>> Have you looked at the SOAP server side yet? I'm wondering how > >>> they > >>> are restricting the server side but not the client side. Most > >>> likely, if you drop down to the CXF server factory instead of > >>> Endpoint.publish(...), you may be able to even get CXF services > >>> working. > >> > >> Good news: The server-side of Apache CXF JAX-WS frontend seems to work > >> as it on GAE, at least for a simple example available at > >> http://ow2-frascati.appspot.com/services/fibonacci-ws?wsdl > > > > Did you try hitting the endpoint with a client or just deploying? > > Since Message.Scope is used on the server side during request > > processing, I'm surprised it would work if your client didn't work. > > I tried the service with soapUI and replies are correct. > > My service is Java-first interface, WSDL is generated at runtime, no > JAX-WS annotation in my interface. > Perhaps this implies this works well. > > I will try an example with a WSDL interface first.
That's really interesting. I wonder why the Scope things works there, but not client side. Very strange. Oh well. Glad it works. :-) -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
