Same problem here. To check I switched from woodstock 3.2.0 to BEA STAX implementation and see less duplicates namespaces.
BTW the BEA STAX implemention is old (2003) and I hope to see this problem fixed in XFire/Woodstox will fix it soon 2007/1/24, bstearman <[EMAIL PROTECTED]>:
I'm trying to see if there is a solution to the problem of the SOAP response containing repeated namespaces. This bloats the response size by quite a bit, and we really need to find a way to fix this. Here is a sample of the SOAP response XFire is returning from one of our services: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soap:Body> <getMapResponse xmlns="http://somenamespace";> <out> <layers xsi:nil="true" xmlns="http://somenamespace/map/"/> <legendURL xmlns="http://somenamespace/map/";>http://some.url/someimage.jpg</legendURL> <mapArea xmlns="http://somenamespace/map/";> <center> <coordSys xmlns="http://somenamespace/geom/";> <datumTransformation xsi:nil="true"/> <projection>4326</projection> </coordSys> <x xmlns="http://somenamespace/geom/";>-117.19</x> <y xmlns="http://somenamespace/geom/";>34.05</y> </center> <extent> <coordSys xmlns="http://somenamespace/geom/";> <datumTransformation xsi:nil="true"/> <projection>4326</projection> </coordSys> <maxX xmlns="http://somenamespace/geom/";>-116.714109</maxX> <maxY xmlns="http://somenamespace/geom/";>34.406918</maxY> <minX xmlns="http://somenamespace/geom/";>-117.665891</minX> <minY xmlns="http://somenamespace/geom/";>33.693082</minY> </extent> <scale>999999</scale> </mapArea> <mapURL xmlns="http://somenamespace/map/";>http://some.url/someimage2.jpg</mapURL> <outputCoordSys xmlns="http://somenamespace/map/";> <datumTransformation xsi:nil="true" xmlns="http://somenamespace/geom/"/> <projection xmlns="http://somenamespace/geom/";>4326</projection> </outputCoordSys> </out> </getMapResponse> </soap:Body> </soap:Envelope> As you can see, each field in the response lists out the namespace. It seems that the more appropriate way to construct the response would be to have the namespaces defined at the top level, such as xmlns:ns1"http://somenamespace/map/"; and xmlns:ns2="http://somenamespace/geom/"; and then just use the namespace prefixes throughout the rest of the response. Is there any way to configure XFire to do this either through Spring, in the Aegis mappings, or perhaps wrapping or extending XFire? Our web services are using XFire loaded through Spring. Here's our current setup: Java 1.4.2 (Sadly, at this point we cannot move to Java 5) XFire 1.2.4 Spring 1.2.6 Stax API 1.0.1 We are using Aegis mapping files to control definition of our service endpoints (since we don't have access to annotations) and complex types. I ran across this old JIRA issue that seems relevant to this issue: http://jira.codehaus.org/browse/XFIRE-512 as well as the following forum threads: http://www.nabble.com/duplicate-namespaces-tf2073137.html#a5707988 http://www.nabble.com/Namespace-repeating-on-mapped-java-bean-tf2430495.html#a6776747 http://www.nabble.com/how-to-enforce-namespace-prefix-usage-in-SOAP-replies--tf1865789.html#a5097786 The information seems to suggest that XFire has fixed the way they use Stax, however, we haven't noticed any change when upgrading to the latest XFire release. Thanks in advance, Blake Stearman -- View this message in context: http://www.nabble.com/SOAP-response-contains-redundant-namespaces-tf3084484.html#a8572240 Sent from the XFire - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
--------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
