I'm not sure why the latter would work, because you're not specifying the proper namespace (http://services.domain.com/) for it.
Also, for the former, I'm not certain that the parameter is really getting lost in parsing--could it be that the declared input parameter's namespace (http://services.domain.com/) is not what is expected by the web service? If the namespace is wrong, i.e., per the WSDL getApplication's namespace should *not* be http://services.domain.com/, the web service provider should ignore the element. Glen Chris Hardin wrote: > > I have a CXF service and a user is sending a Soap message to it like this\ > > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi=" > http://www.w3.org/2001/XMLSchema-instance";> > <soapenv:Body> > <getApplication xmlns="http://services.domain.com/";> > <arg0 xmlns="http://services.domain.com/";>33</arg0> > </getApplication> > </soapenv:Body> > </soapenv:Envelope> > > > The parameter gets lost in parsing and a null gets passed to the service, > but if I remove the xmlns elements from the tags or put it in the header > and > reference them in the tags, it works fine > > This works > > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi=" > http://www.w3.org/2001/XMLSchema-instance";> > <soapenv:Body> > <getApplication> > <arg0>33</arg0> > </getApplication> > </soapenv:Body> > </soapenv:Envelope> > > > Can anyone give me a clue as to what is happening. I am lost. > > -- View this message in context: http://old.nabble.com/Soap-Message-and-Namespace-issue-tp27932209p27934308.html Sent from the cxf-user mailing list archive at Nabble.com.
