I get the proper namespace in the place in the soap response that you see the wrong one. Is your stack doing some "fuzzy namespace replacement"? Mine has support for this kind of behaviour (although it's not turned on). -- Chris On 10/11/06 10:47, "Peter G. Lane" <lane@mcs.anl.gov> wrote:
Is anyone else seeing an incorrect version of WS-Addressing in their CreatActivityResponse messages from CROWN? Liang says they're using the correct version and others haven't had this problem AFAIK, but my SOAP message says otherwise. Here's an example:
2006-11-10 11:42:50,813 DEBUG handlers.MessageLoggingHandler [main,logMessage:58] SOAPEnvelope: <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" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"><soapenv:Header><; wsa:MessageID soapenv:mustUnderstand="0">uuid:4389a040-70eb-11db-943a-e1848c059f31</wsa:Mess ageID><wsa:To soapenv:mustUnderstand="0">http://schemas.xmlsoap.org/ws/2004/03/addressing/ro le/anonymous</wsa:To><wsa:Action soapenv:mustUnderstand="0">http://schemas.ggf.org/bes/2006/08/bes-factory/BESF actoryPortType/CreateActivityResponse</wsa:Action><From soapenv:mustUnderstand="0" xmlns="http://schemas.xmlsoap.org/ws/2004/03/addressing"><Address>https://cola b.crown.org.cn:8080/crown/services/ScheduleService</Address></From><wsa:Relate sTo RelationshipType="wsa:Reply" soapenv:mustUnderstand="0">uuid:40bf35a0-70eb-11db-8d44-8c0196de5385</wsa:Rela tesTo></soapenv:Header><soapenv:Body><ns1:CreateActivityResponse xmlns:ns1="http://schemas.ggf.org/bes/2006/08/bes-factory"><ns1:ActivityIdenti fier xmlns="http://schemas.xmlsoap.org/ws/2004/03/addressing"><Address>https://cola b.crown.org.cn:8080/crown/services/ScheduleService</Address></ns1:ActivityIden tifier></ns1:CreateActivityResponse></soapenv:Body></soapenv:Envelope>
Peter -- ogsa-hpcp-wg mailing list ogsa-hpcp-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg