Leave a Reply


  1. Nice! Thanx for letting me know there is such a thing as a MSE.

    guidol Reply

  2. I ran into the MSE-project while we discussed the WSDL/xsd-issue (svcutil) on the phone. I’m guessing you found it about then as well! ๐Ÿ™‚

    It looked very interesting to me as well, but it slipped my mind. It lookes like a promising product, worth investing some time on. So Edwin, keep up informed! ๐Ÿ˜‰

    I’m wondering if it’s possible to define your own contract and have MSE ‘convert’ calls to your custom contract to calls to the actual service’s contract. And by convert I don’t mean just message translation, but also operation-sequence translation; eg: one call to the custom (virtual) service, results in multiple calls to the real service. This way we can abstract product-specific services and therefore prevent vendor lock-in. It’s also possible to create a more ‘consumer-friendly’ contract.

    robertka Reply

  3. Robert,

    The channel moniker only supports mapping a certain URL and action to another URL and action. It is not possible to translate a single call to a virtual service into multiple calls to other services. But you could always create your own process-service with a consumer-friendly contract that calls multiple product-specific services and offer (perhaps multiple versions) of this process-service using MSE. But something tells me you've already thought about this yourself ๐Ÿ˜‰

    edwinw Reply