Hi Sergey, That example looks like its configuring the client to drop the namespace. What I need is the reverse, I need to configure the server to not use a namespace. I can't change the PHP client so I'm trying to change the server so that it works with existing PHP client code.
(Apparently in the older CXF version it accepted calls with or without a namespace specified.) -Dave On Fri, Jul 8, 2011 at 8:41 AM, Sergey Beryozkin <[email protected]> wrote: > Here you go: > > http://cxf.apache.org/docs/transformationfeature.html > > configure JAXWS endpoint to drop the namespace like this: > > {http://mynamespace}*:* > > where {http://mynamespace}* is a key, * is a value > > Cheers, Sergey > > On Fri, Jul 8, 2011 at 3:35 PM, David Hoffer <[email protected]> wrote: >> I have some existing services developed and deployed with 2.1.2 using >> the java first annotation approach (JAX-WS). After upgrading to 2.4.1 >> existing PHP clients receive the following error: >> >> INFO | jvm 1 | 2011/07/08 04:22:03 | WARNING: Interceptor for >> {http://some_namespace/}IAPIService#{http://some_namespace/}calc has >> thrown exception, unwinding now >> INFO | jvm 1 | 2011/07/08 04:22:03 | org.apache.cxf.interceptor. >> Fault: Unexpected wrapper element calc found. Expected >> {http://some_namespace/}calc. >> >> However Java CXF clients work just fine. It seems that the PHP client >> (which code I did not write) is not using any namespace. How can I >> configure CXF 2.4.1 to behave so it can work with existing PHP code? >> I have no need for namespaces so if disabling that would solve the >> problem that would be fine...how do I do that? >> >> -Dave >> > > > > -- > Sergey Beryozkin > > http://sberyozkin.blogspot.com > Talend - http://www.talend.com >
