从支持 WSE 的 Web 服务进行切换，WCF 是正确的选择吗？
我们目前有六个项目最初是使用 .NET Framework 1.1 和 WSE 2.0 构建的。但微软缺乏对 WSE 的支持，并且其最新版本 (3.0) 仅针对 .NET Framework 2.0。我们的新项目将使用 .NET Framework 3.5，而不是 黑客攻击我们自己的 WSE 支持，我们目前正在寻找替代方法。
我们当前的项目使用 WSE 使用 X.509 证书对 SOAP 消息进行数字签名。这也是我们未来项目的要求。
看起来使用 WCF 路由似乎是明智的选择，但是还有其他选择吗？ WCF 似乎支持 X.509 认证，但我们并不担心它对 .NET 以外的其他平台的支持。我们的客户需要能够使用基于 Java 的软件来连接到我们的服务。他们表示它应该像以前一样简单（当我们使用 Web 服务时）。因此 WCF 必须配置为使用 HTTP 和 SOAP。
考虑到 X.509、跨平台互操作性和易用性（HTTP 和 SOAP）的要求，Windows Communication Foundation 是正确的解决方案吗？
We currently have a half a dozen of project which originally have been built using .NET Framework 1.1 and WSE 2.0. But Microsoft's support for WSE is lacking and the latest version of it (3.0) only targets .NET Framework 2.0. Our new projects will use .NET Framework 3.5 and instead of hacking our self a WSE-support, we are currently looking for alternative approaches.
Our current projects use WSE to digitally sign the SOAP-messages with a X.509 certificate. This is what we require also for our future projects.
It seems that going with the WCF-route seems to be the smart choice but is there any alternatives? WCF seems to support X.509 certifications but we are little worried of its support for other platforms than .NET. Our clients need to be able to use Java-based software to connect to out services. And they've stated that it should be as easy as it has been before (when we were using Web Services). So WCF must be configured to use HTTP and SOAP.
Given the requirements of X.509, cross-platform interoperability and ease of use (HTTP & SOAP), is Windows Communication Foundation the right solution?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
是的，WCF 就是解决方案 - 它是用于构建 Web 服务的 API，如果您不使用 MS/.NET 特定功能，它是可互操作的。但您应该意识到，有时将 WSE 服务移植到 WCF 会出现一些问题。我建议在 WSE 中构建非常简单的服务（例如 Hello World），并以与实际服务相同的方式使用证书保护它。然后创建 Jave 客户端来使用该服务。之后用 WCF 替换 WSE 服务。这将是您的概念证明。如果出现问题，您可以在此处或 MSDN 上轻松分享此解决方案以获得帮助。
Yes WCF is the solution - it is API for building Web services and it is interoperable if you don't use MS/.NET specific features. But you should be aware that sometimes there are some problems with porting WSE services to WCF. I recommend to build very simple service in WSE (like Hello World) and secure it with certificates in the same way as real services. Then create Jave client to consume the service. After that replace WSE service with WCF. It will be your proof of concept. In a case of problems you can easily share this solution here or on MSDN to get some help.