Hi, okay, you are saying that your previous non-soap service implementation didn't complain about the missing namespace declaration but your current cxf based implementation complains about the missing xsd namespace declaration needed to decode the type value. This happens because the generated code is xml-schema-aware and expects a valid type in the xsi attribute value if given.
First of all, it's not a good idea to make your SOAP service implementation ignore the missing declaration, but there is a possibility to let the missing declarations ignored by using a jaxws provider based service. In this case, you just have a plain XML based interface in your service implementaiton using javax.xml.transform.Source and you can parse the XML document as you like. You can look at the jaxws_dispatch_provider sample in the sample distribution. But as I said, you should really be fixing the clients by making them either not sending the xsi attributes or including the xsd namespace declaration instead of adding this workaround in the service implementation to accept those invalid messages. regards, aki 2011/7/18 Shyamranny <[email protected]>: > Hi, > > I have upgraded my web service and now the new webservice uses CXF. When I > send my old soap message to the new CXF webservice, i am getting the > following response. > > 'Unmarshalling Error: prefix xsd is not bound to a namespace'. > > In my soap request, I have the following element. > > '<A700129Naam xsi:type="xsd:string">Shyam</A700129Naam>' Here I use the > prefix 'xsd' and if I add this prefix in the xmlns, this soap will go well. > But our client will not change there soap request. They need to send the old > soap request. > > How can I solve this issue? Can I add namespace and prefix in the spring > configuration file? I have tried a lot like XMLFilterImpl, > AbstractInDatabindingInterceptor, NamespacePrefixMapper etc. But not worked. > > Thanks and regards, > Shyam S > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Unmarshalling-Error-prefix-xsd-is-not-bound-to-a-namespace-tp4598539p4598539.html > Sent from the cxf-user mailing list archive at Nabble.com. >
