Hi Fellows,
I am wondering if anyone here could give me some advice on the best practice
of setting the value of the SoapActorAttribute in a XML HTTP Service. From
all the examples given, it seems that its always the URI of the Endpoints or
the Router. One thing with this tight coupling of endpoint addresses to the
recipient of the SOAP Message does bring along some restrictions.
I guess this is where the EndpointReference.Via comes in. The via comes in
as a Transport mechanism for a standard well-known interface
(urn:soap//ms.com) that is exposed as the SoapActor. In this case, you can
get several endpoint addresses and transports as well that is associated
with a well-known interface. This is all good.
However, the question I have is the real-world implementation of it. The
above seems to be only possible with the SoapReceivers and SoapClients and
such.
1) How do you set it in a ASMX Web Service with WSE2.0 ? Bound To and Via
together ?
2) If I am not able to set it, what would be the best practice to set as a
SoapActorAttribute ? EndpointAddress (*.asmx, *ashx) or Well-known name
(urn:soap//ms.com)
3) If I choose EndpointAddress, that message becomes tightly bound to its
endpoint which flouts one of the principles of Service-Orientation
4) If I choose a common name, I am assuming that everyone client knows about
this name which makes it restrictive and less secure to as the policy engine
looks at the TO in the addressing headers
AND the ONE BIG Question:
5) WSE looks at the Request URL if an addressing header is not found and
tries to match that with the SoapActorAttribute. Most messages sent today do
NOT have the addressing headers (be it .NET, pre-.NET or Java Consumers). So
this effectively means that the best way for interoperability is for the
SoapActorAttribute to be that of the EndpointAddress becos all messages sent
to the service has that same Request URL so it seems that I have to expose
that WSE ASMX Web Service with a SoapActorAttribute of a its own
EndpointAddress. BUT wouldnt that flout the purpose of the
EndpointReference.Via property ? So how should I be doing this ? Unless I
can do the same with a ASP.NET Web Service with WSE that I can do with the
SOAP Messaging stack of senders, receivers, services and clients. If not,
its quite a headache to implement all these...
6) Another thing, the practice of WSE looking at the Request URL if an
addressing header is not found and tries to match that with the
SoapActorAttribute. Is this a Microsoft WSE thingy ? Or a WS-I standard
implementaion that even IBM Emerging Toolkit practices ?
I hope I have made my questions clear. Thank you for any of your responses
and feedback.
--
Thank you very much
Warmest Regards,
Softwaremaker
Architect | Evangelist | Consultant
+++++++++++++++++++++++++++++++++
