Skip to main content

[MS to Sun]scenario 1.1.2.1_OneWay_Reliable_Anonymous_BP12 failed.

3 replies [Last post]
Anonymous

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Potociar Marek

Thank you Ram,
Marek

On 8.2.2010, at 18:32, Ram Jeyaraman wrote:

> Sure, I will request the WG to make this change. I expect it will
> take about 2 weeks before a new version of the scenarios document
> with this change will be available.
>
> From: Marek.Potociar@Sun.COM [mailto:Marek.Potociar@Sun.COM]
> Sent: Saturday, February 06, 2010 2:42 AM
> To: Mark Cowlishaw
> Cc: Lianhao Gao; users@metro.dev.java.net; Harold Carr; Ram
> Jeyaraman; Xingrui Pei; Anchuan Qian; Unknown Unknown; Falei Wang
> Subject: Re: [MS to Sun]scenario
> 1.1.2.1_OneWay_Reliable_Anonymous_BP12 failed.
>
>
> On 5.2.2010, at 19:58, Mark Cowlishaw wrote:
>
>
> You are correct, if wsdl is used to generate the client. However,
> since ws-policy is not part of RSP, our clients are static, not
> generated from wsdl, and our anonymous clients for scenarios 1.1.x.x
> and 1.2.x.x are set up to use WS-MakeConnection. I think you’re
> right about the easiest solution.
>
> Ram, do you think we need to augment the test scenarios document to
> explicitly require the use of ws-MakeConnection in positive
> scenarios that use a non-addressable client?
>
> +1. That would remove another piece of ambiguity.
>
> Marek
>
>
>
> From: Marek.Potociar@Sun.COM [mailto:Marek.Potociar@Sun.COM]
> Sent: Friday, February 05, 2010 3:21 AM
> To: Mark Cowlishaw; Lianhao Gao
> Cc: users@metro.dev.java.net; Harold Carr; Ram Jeyaraman; Xingrui
> Pei; Anchuan Qian; Unknown Unknown; Falei Wang
> Subject: Re: [MS to Sun]scenario
> 1.1.2.1_OneWay_Reliable_Anonymous_BP12 failed.
>
> Mark,
> Is this address valid also in case the endpoint does not advertise
> support for WS-MC? I am afraid such behavior goes against the intent
> of the WS-Policy spec[1]:
>
> Any entity in a Web services based system may expose a policy to
> convey conditions under which it functions.
>
> My understanding is that if an endpoint does not specify
> wsmc:MCSupported assertion in it's policy, then it is not required
> to understand and properly process the WS-MC anonymous addresses. It
> is the responsibility of the requester (client) to choose a valid
> policy alternative and adhere to it.
>
> Lianhao, if the scenario allows it, I think the easiest resolution
> would be to add the wsmc:MCSupported assertion into the endpoint's
> policy config. This will make sure that the Metro endpoint enables
> the WS-MC message processing tube which can handle the WSMC
> annonymous addresses properly.
>
> Best regards,
> Marek
>
> [1] http://www.w3.org/TR/ws-policy/#Web_services
>
>
>
> On 4.2.2010, at 20:21, Mark Cowlishaw wrote:
>
>
>
> This is a WS-MakeConnection anonymous address. It’s use is valid in
> any of the anonymous client scenarios.
>
> From: Lianhao Gao [mailto:lhgao@thoughtworks.com]
> Sent: Wednesday, February 03, 2010 10:03 PM
> To: users@metro.dev.java.net; Potociar Marek
> Cc: Harold Carr; Mark Cowlishaw; Ram Jeyaraman; Xingrui Pei; Anchuan
> Qian; Unknown Unknown; Falei Wang
> Subject: [MS to Sun]scenario 1.1.2.1_OneWay_Reliable_Anonymous_BP12
> failed.
>
> Hello Marek,
>
> we tested scenario MS to Sun 1.1.2.1_OneWay_Reliable_Anonymous_BP12,
> but failed.
>
> Server Log and messages exchanges log are attached.
>
> The error is
> "...............Cannot resolve wsdl operation that this Packet is
> targeted for...............Caused by: java.net.UnknownHostException:
> docs.oasis-open.org..........".
>
> We found messages from WCF client contains following part in soap
> header.
>
> http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=b72300ff-1052-4574-a502-8d753e6a318f
>

>

>
> Metro endpoint can't recognize it.
>
> Compared with Metro to Metro, "docs.oasis-open.org" is only
> appears when MC is supported on server side. If server side is
> configured as OneWay and No MC supported, the Address in ReplyTo is
> "http://www.w3.org/2005/08/addressing/anonymous".
> OneWay scenarios on Metro endpoints have no MC supported. But WCF
> client still send "docs.oasis-open.org".
>
> I am not sure who's bug is it. Please help to check that.
>
> --
> Lianhao Gao
> ThoughtWorks
> lhgao@thoughtworks.com
> MSN gaolianhao@hotmail.com
>
>

[att1.html]

Lianhao Gao

Now It works with adding MC support on Metro server.

On Tue, Feb 9, 2010 at 8:25 PM, Potociar Marek wrote:

> Thank you Ram,
> Marek
>
>
>
>
>
> On 8.2.2010, at 18:32, Ram Jeyaraman wrote:
>
> Sure, I will request the WG to make this change. I expect it will take
> about 2 weeks before a new version of the scenarios document with this
> change will be available.
>
> *From:* Marek.Potociar@Sun.COM [mailto:Marek.Potociar@Sun.COM
> ]
> *Sent:* Saturday, February 06, 2010 2:42 AM
> *To:* Mark Cowlishaw
> *Cc:* Lianhao Gao; users@metro.dev.java.net; Harold Carr; Ram Jeyaraman;
> Xingrui Pei; Anchuan Qian; Unknown Unknown; Falei Wang
>
> *Subject:* Re: [MS to Sun]scenario 1.1.2.1_OneWay_Reliable_Anonymous_BP12
> failed.
>
>
> On 5.2.2010, at 19:58, Mark Cowlishaw wrote:
>
>
> You are correct, if wsdl is used to generate the client. However, since
> ws-policy is not part of RSP, our clients are static, not generated from
> wsdl, and our anonymous clients for scenarios 1.1.x.x and 1.2.x.x are set up
> to use WS-MakeConnection. I think you’re right about the easiest solution.
>
> *Ram*, do you think we need to augment the test scenarios document to
> explicitly require the use of ws-MakeConnection in positive scenarios that
> use a non-addressable client?
>
> +1. That would remove another piece of ambiguity.
>
> Marek
>
>
>
> *From:* Marek.Potociar@Sun.COM [mailto:Marek.Potociar@Sun.COM
> ]
> *Sent:* Friday, February 05, 2010 3:21 AM
> *To:* Mark Cowlishaw; Lianhao Gao
> *Cc:* users@metro.dev.java.net; Harold Carr; Ram Jeyaraman; Xingrui Pei;
> Anchuan Qian; Unknown Unknown; Falei Wang
> *Subject:* Re: [MS to Sun]scenario 1.1.2.1_OneWay_Reliable_Anonymous_BP12
> failed.
>
> Mark,
> Is this address valid also in case the endpoint does not advertise support
> for WS-MC? I am afraid such behavior goes against the intent of the
> WS-Policy spec[1]:
>
> *Any entity in a Web services based system may expose a policy to convey
> conditions under which it functions.*
>
> My understanding is that if an endpoint does not specify wsmc:MCSupported
> assertion in it's policy, then it is not required to understand and properly
> process the WS-MC anonymous addresses. It is the responsibility of the
> requester (client) to choose a valid policy alternative and adhere to it.
>
> Lianhao, if the scenario allows it, I think the easiest resolution would be
> to add the wsmc:MCSupported assertion into the endpoint's policy config.
> This will make sure that the Metro endpoint enables the WS-MC message
> processing tube which can handle the WSMC annonymous addresses properly.
>
> Best regards,
> Marek
>
> [1] http://www.w3.org/TR/ws-policy/#Web_services
>
>
>
> On 4.2.2010, at 20:21, Mark Cowlishaw wrote:
>
>
>
> This is a WS-MakeConnection anonymous address. It’s use is valid in any of
> the anonymous client scenarios.
>
> *From:* Lianhao Gao [mailto:lhgao@thoughtworks.com
> ]
> *Sent:* Wednesday, February 03, 2010 10:03 PM
> *To:* users@metro.dev.java.net; Potociar Marek
> *Cc:* Harold Carr; Mark Cowlishaw; Ram Jeyaraman; Xingrui Pei; Anchuan
> Qian; Unknown Unknown; Falei Wang
> *Subject:* [MS to Sun]scenario 1.1.2.1_OneWay_Reliable_Anonymous_BP12
> failed.
>
>
> Hello Marek,
> we tested scenario *MS to Sun 1.1.2.1_OneWay_Reliable_Anonymous_BP12*, but
> failed.
>
> Server Log and messages exchanges log are attached.
>
> The error is
> "...............Cannot resolve wsdl operation that this Packet is targeted
> for...............Caused by: java.net.UnknownHostException:
> docs.oasis-open.org..........".
>
> We found messages from WCF client contains following part in soap header.
>
>
>
> http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=b72300ff-1052-...
>

>

> Metro endpoint can't recognize it.
>
> Compared with Metro to Metro, "docs.oasis-open.org" is only appears when
> MC is supported on server side. If server side is configured as OneWay and
> No MC supported, the Address in ReplyTo is "
> http://www.w3.org/2005/08/addressing/anonymous".
> OneWay scenarios on Metro endpoints have no MC supported. But WCF client
> still send "docs.oasis-open.org".
>
> I am not sure who's bug is it. Please help to check that.
>
> --
> Lianhao Gao
> ThoughtWorks
> lhgao@thoughtworks.com
> MSN gaolianhao@hotmail.com
>
>
>
>
>

--
Lianhao Gao
ThoughtWorks
lhgao@thoughtworks.com
MSN gaolianhao@hotmail.com
[att1.html]

Potociar Marek

Great, thank you for the update Lianhao,

Marek

On 10.2.2010, at 4:14, Lianhao Gao wrote:

> Now It works with adding MC support on Metro server.
>
> On Tue, Feb 9, 2010 at 8:25 PM, Potociar Marek
> wrote:
> Thank you Ram,
> Marek
>
>
>
>
>
> On 8.2.2010, at 18:32, Ram Jeyaraman wrote:
>
>> Sure, I will request the WG to make this change. I expect it will
>> take about 2 weeks before a new version of the scenarios document
>> with this change will be available.
>>
>> From: Marek.Potociar@Sun.COM [mailto:Marek.Potociar@Sun.COM]
>> Sent: Saturday, February 06, 2010 2:42 AM
>> To: Mark Cowlishaw
>> Cc: Lianhao Gao; users@metro.dev.java.net; Harold Carr; Ram
>> Jeyaraman; Xingrui Pei; Anchuan Qian; Unknown Unknown; Falei Wang
>>
>> Subject: Re: [MS to Sun]scenario
>> 1.1.2.1_OneWay_Reliable_Anonymous_BP12 failed.
>>
>>
>> On 5.2.2010, at 19:58, Mark Cowlishaw wrote:
>>
>>
>> You are correct, if wsdl is used to generate the client. However,
>> since ws-policy is not part of RSP, our clients are static, not
>> generated from wsdl, and our anonymous clients for scenarios
>> 1.1.x.x and 1.2.x.x are set up to use WS-MakeConnection. I think
>> you’re right about the easiest solution.
>>
>> Ram, do you think we need to augment the test scenarios document to
>> explicitly require the use of ws-MakeConnection in positive
>> scenarios that use a non-addressable client?
>>
>> +1. That would remove another piece of ambiguity.
>>
>> Marek
>>
>>
>>
>> From: Marek.Potociar@Sun.COM [mailto:Marek.Potociar@Sun.COM]
>> Sent: Friday, February 05, 2010 3:21 AM
>> To: Mark Cowlishaw; Lianhao Gao
>> Cc: users@metro.dev.java.net; Harold Carr; Ram Jeyaraman; Xingrui
>> Pei; Anchuan Qian; Unknown Unknown; Falei Wang
>> Subject: Re: [MS to Sun]scenario
>> 1.1.2.1_OneWay_Reliable_Anonymous_BP12 failed.
>>
>> Mark,
>> Is this address valid also in case the endpoint does not advertise
>> support for WS-MC? I am afraid such behavior goes against the
>> intent of the WS-Policy spec[1]:
>>
>> Any entity in a Web services based system may expose a policy to
>> convey conditions under which it functions.
>>
>> My understanding is that if an endpoint does not specify
>> wsmc:MCSupported assertion in it's policy, then it is not required
>> to understand and properly process the WS-MC anonymous addresses.
>> It is the responsibility of the requester (client) to choose a
>> valid policy alternative and adhere to it.
>>
>> Lianhao, if the scenario allows it, I think the easiest resolution
>> would be to add the wsmc:MCSupported assertion into the endpoint's
>> policy config. This will make sure that the Metro endpoint enables
>> the WS-MC message processing tube which can handle the WSMC
>> annonymous addresses properly.
>>
>> Best regards,
>> Marek
>>
>> [1] http://www.w3.org/TR/ws-policy/#Web_services
>>
>>
>>
>> On 4.2.2010, at 20:21, Mark Cowlishaw wrote:
>>
>>
>>
>> This is a WS-MakeConnection anonymous address. It’s use is valid
>> in any of the anonymous client scenarios.
>>
>> From: Lianhao Gao [mailto:lhgao@thoughtworks.com]
>> Sent: Wednesday, February 03, 2010 10:03 PM
>> To: users@metro.dev.java.net; Potociar Marek
>> Cc: Harold Carr; Mark Cowlishaw; Ram Jeyaraman; Xingrui Pei;
>> Anchuan Qian; Unknown Unknown; Falei Wang
>> Subject: [MS to Sun]scenario 1.1.2.1_OneWay_Reliable_Anonymous_BP12
>> failed.
>>
>> Hello Marek,
>>
>> we tested scenario MS to Sun
>> 1.1.2.1_OneWay_Reliable_Anonymous_BP12, but failed.
>>
>> Server Log and messages exchanges log are attached.
>>
>> The error is
>> "...............Cannot resolve wsdl operation that this Packet is
>> targeted for...............Caused by:
>> java.net.UnknownHostException: docs.oasis-open.org..........".
>>
>> We found messages from WCF client contains following part in soap
>> header.
>>
>> http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=b72300ff-1052-4574-a502-8d753e6a318f
>>

>>

>>
>> Metro endpoint can't recognize it.
>>
>> Compared with Metro to Metro, "docs.oasis-open.org" is only
>> appears when MC is supported on server side. If server side is
>> configured as OneWay and No MC supported, the Address in ReplyTo
>> is "http://www.w3.org/2005/08/addressing/anonymous".
>> OneWay scenarios on Metro endpoints have no MC supported. But WCF
>> client still send "docs.oasis-open.org".
>>
>> I am not sure who's bug is it. Please help to check that.
>>
>> --
>> Lianhao Gao
>> ThoughtWorks
>> lhgao@thoughtworks.com
>> MSN gaolianhao@hotmail.com
>>
>>
>
>
>
>
> --
> Lianhao Gao
> ThoughtWorks
> lhgao@thoughtworks.com
> MSN gaolianhao@hotmail.com

[att1.html]