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:MessageID><wsa:To soapenv:mustUnderstand="0">http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa:To><wsa:Action soapenv:mustUnderstand="0">http://schemas.ggf.org/bes/2006/08/bes-factory/BESFactoryPortType/CreateActivityResponse</wsa:Action><From soapenv:mustUnderstand="0" xmlns="http://schemas.xmlsoap.org/ws/2004/03/addressing"><Address>https://colab.crown.org.cn:8080/crown/services/ScheduleService</Address></From><wsa:RelatesTo RelationshipType="wsa:Reply" soapenv:mustUnderstand="0">uuid:40bf35a0-70eb-11db-8d44-8c0196de5385</wsa:RelatesTo></soapenv:Header><soapenv:Body><ns1:CreateActivityResponse xmlns:ns1="http://schemas.ggf.org/bes/2006/08/bes-factory"><ns1:ActivityIdentifier xmlns="http://schemas.xmlsoap.org/ws/2004/03/addressing"><Address>https://colab.crown.org.cn:8080/crown/services/ScheduleService</Address></ns1:ActivityIdentifier></ns1:CreateActivityResponse></soapenv:Body></soapenv:Envelope> Peter
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
Same here -- looks correct to me. -- Mark Morgan Research Scientist Department of Computer Science University of Virginia http://www.cs.virginia.edu mmm2a@virginia.edu (434) 982-2047
-----Original Message----- From: ogsa-hpcp-wg-bounces@ogf.org [mailto:ogsa-hpcp-wg-bounces@ogf.org] On Behalf Of Christopher Smith Sent: Friday, November 10, 2006 1:57 PM To: Peter G. Lane; ogsa-hpcp-wg@ggf.org Subject: Re: [ogsa-hpcp-wg] CROWN WS-Addressing version
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/addre
ssing/ro le/anonymous</wsa:To><wsa:Action
soapenv:mustUnderstand="0">http://schemas.ggf.org/bes/2006/08/bes-fact
ory/BESF actoryPortType/CreateActivityResponse</wsa:Action><From soapenv:mustUnderstand="0"
xmlns="http://schemas.xmlsoap.org/ws/2004/03/addressing"><Address>http
s://cola
b.crown.org.cn:8080/crown/services/ScheduleService</Address></From><ws
a: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:Activi
tyIdenti fier
xmlns="http://schemas.xmlsoap.org/ws/2004/03/addressing"><Address>http
s://cola
b.crown.org.cn:8080/crown/services/ScheduleService</Address></ns1:Acti
vityIden
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
-- ogsa-hpcp-wg mailing list ogsa-hpcp-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg
I guess it must be. It's certainly the version of WS-Addressing that we use. Liang, are you explicitly defining the wsa prefix, or are you just using it? I'm wondering if my tooling is inserting the xmlns:wsa=... attribute because it's missing. Peter Christopher Smith wrote:
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
Hi Peter, We just using the WS-addressing as one of our handler, and this handler are configured in both requestFlow and responseFlow. After having a look at my log, I though the following request might been sent by you. In the request you are using 2004 03 version, so my server just insert 2004 03 verion in the header when return the message. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/address ing" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Header><wsse: Securi ty xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri ty-secext-1.0.xsd"> <wsse:UsernameToken><wsse:Username>SC06</wsse:Username><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss- username-token-profile-1.0#PasswordText">SC06</wsse:Password><wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-20 0401-wss-wssecurity-utility-1.0.xsd">2006-11-10T18:30:59Z</wsu:Created></wss e:UsernameToken></wsse:Security><wsa:MessageID>uuid:9ca2 3a90-70e9-11db-9f26-e6dc371052d9</wsa:MessageID><wsa:To>https://colab.crown. org.cn:8080/crown/services/ScheduleService</wsa:To><wsa: Action>http://schemas.ggf.org/bes/2006/08/bes-factory/BESFactoryPortType/Get FactoryAttributesDocument</wsa:Action><wsa:From><wsa:Add ress>http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa:Ad dress></wsa:From></soapenv:Header><soapenv:Body><GetFact oryAttributesDocument xmlns="http://schemas.ggf.org/bes/2006/08/bes-factory"></GetFactoryAttribute sDocument></soapenv:Body></soapenv :Envelope> Best Regards, Liang ZHONG Grid Computing Research Group Institute of Advanced Computing Technology, Beihang University Tel: +86 10 8231 6262 Fax: +86 10 8231 6796 Addr: Room 507, Building G,The New Main Building, 37# Xueyuan Rd., Haidian District, Beijing 100083, PRC -----Original Message----- From: ogsa-hpcp-wg-bounces@ogf.org [mailto:ogsa-hpcp-wg-bounces@ogf.org] On Behalf Of Peter G. Lane Sent: Saturday, November 11, 2006 3:34 AM To: Christopher Smith Cc: ogsa-hpcp-wg@ggf.org Subject: Re: [ogsa-hpcp-wg] CROWN WS-Addressing version I guess it must be. It's certainly the version of WS-Addressing that we use. Liang, are you explicitly defining the wsa prefix, or are you just using it? I'm wondering if my tooling is inserting the xmlns:wsa=... attribute because it's missing. Peter Christopher Smith wrote:
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:Me ss
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/BE SF
actoryPortType/CreateActivityResponse</wsa:Action><From soapenv:mustUnderstand="0"
xmlns="http://schemas.xmlsoap.org/ws/2004/03/addressing"><Address>https://co la
b.crown.org.cn:8080/crown/services/ScheduleService</Address></From><wsa:Rela te
sTo RelationshipType="wsa:Reply"
soapenv:mustUnderstand="0">uuid:40bf35a0-70eb-11db-8d44-8c0196de5385</wsa:Re la
tesTo></soapenv:Header><soapenv:Body><ns1:CreateActivityResponse
xmlns:ns1="http://schemas.ggf.org/bes/2006/08/bes-factory"><ns1:ActivityIden ti
fier
xmlns="http://schemas.xmlsoap.org/ws/2004/03/addressing"><Address>https://co la
b.crown.org.cn:8080/crown/services/ScheduleService</Address></ns1:ActivityId en
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
participants (4)
-
Christopher Smith -
Liang Zhong -
Mark Morgan -
Peter G. Lane