Hi, I've got a client application which is using Java 5 and XFire 1.2.4 and Annotations to call a web service.
When upgrading to XFire 1.2.6, I'm seeing different behaviour in that the namespace and prefix declaration is now split between being specified on the <body> element as well as the operation element. This is causing me problems, as the web service (which I have no control over), expects the namespaces to all be declared on the operation element, <productSearch>. I have seen a related post: http://www.nabble.com/1.2.3-vs-1.2.6-with-XMLBeans-tf3907669.html#a11079218 1.2.3-vs-1.2.6-with-XMLBeans which itself has raised a http://jira.codehaus.org/browse/XFIRE-1035 JIRA , but these have had no conclusion. Does anyone have any idea how to stop the namespaces being declared on the body element? As an aside, I've had zero success trying to get named prefixes, as opposed to the xfire generated ones. Regards Matt FYI: 1.2.6: <soap:Body xmlns:ns1="http://example.com/schemas/ps/20070309"> <ns1:productSearch xmlns:ns3="http://example.com/schemas/ct/20070309" xmlns:ns2="http://example.com/schemas/uc/20070309"> <ns1:clientSearchText>text</ns1:clientSearchText> <ns3:dateRange> <ns3:startDate>2007-10-01</ns3:startDate> <ns3:endDate>2007-10-31</ns3:endDate> </ns3:dateRange> </ns1:productSearch> </soap:Body> 1.2.4: <soap:Body> <ns2:productSearch xmlns:ns2="http://example.com/schemas/ps/20070309" xmlns:ns3="http://example.com/schemas/ct/20070309" xmlns="http://example.com/schemas/uc/20070309"> <ns2:clientSearchText>vmtv</ns2:clientSearchText> <ns3:dateRange> <ns3:startDate>2007-10-01</ns3:startDate> <ns3:endDate>2007-10-31</ns3:endDate> </ns3:dateRange> </ns2:productSearch> </soap:Body> -- View this message in context: http://www.nabble.com/Namespace-declared-in-body-element-in-1.2.6-tf4467294.html#a12737481 Sent from the XFire - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
