Web服务互操作性的开发人员无能坏了吗？ [英] Web service interoperability broken by developers incompetence?
问题描述
你如何开发Web服务以及如何创建WSDL？你怎么在WSDL中包括哪些内容？
How do you develop web services and how do you create WSDL? What do you include in WSDL?
这个问题是基于观察，开发商不使用WSDL正常。 WSDL描述该服务。我认为，服务描述应该包括使用该服务所需要的一切。所以，如果我使用任何WS- *协议，我必须包含的WS-Policy描述了使用。
This question is based on observation that developers don't use WSDL properly. WSDL describes the service. I think that service description should include everything needed to use that service. So if I use any WS-* protocol I have to include WS-Policy describing that usage.
我经常访问MSDN论坛与WCF - .NET API来创建Web服务。几乎每天都会有出现类似的问题：我有Java的安全Web服务，我需要消耗的.NET客户端服务。首先回答通常要求的Java Web服务的WSDL。可惜的是，几乎每一次WSDL描述，只有方法和消息。安全信息完全丢失=>的WSDL没有描述的服务，因为基础上，你是不是能够消耗该服务的WSDL信息！
I often visit MSDN forum related to WCF - .NET API for creating web services. Almost every day there appear question like: "I have Java secured web service and I need to consume that service in .net client". First answer usually asks for WSDL of that Java web service. Unfortunatelly almost every time WSDL describes only methods and messages. Security information is completely missing => that WSDL does not describe that service because based on information in the WSDL you are not able to consume the service!
什么是Java世界的情况呢？您是否使用WS策略？你有没有配套的工具来创建WSDL为你，如果你是不是不够熟练写呢？你如何共享有关服务的信息，当一个团队来消费由其他团队提供的服务？
What is the situation in Java world? Do you use WS policies? Do you have supporting tools to create WSDL for you if you are not skilled enough to write it? How do you share information about services when one team has to consume services provided by other team?
我也从其他角度来看一个问题：什么样的问题的Java开发人员时，他们都需要消耗在.NET中创建Web服务？
I have also a questions from other point of view: What problems Java developers have when they have to consume web services created in .NET?
我觉得这就像在许多项目中，不同的平台有沟通过Web服务的一个很大的痛苦。开发商不共享单一的语言（这应该是与政策WSDL）和大部分时间他们无法解释他们使用了什么样的WS- *功能，因为它涵盖了一些API。如果我们有一个事实，即仅限于一套WS- *的特征通常是支持的API，我们必须得一塌糊涂。 SOAP消息的逆向工程实在是费时费力。
I feel this like a big pain in many projects where different platforms have to communicate over web services. Developers do not share single language (which should be WSDL with policies) and most of the time they are not able to explain what WS-* features they used because it is covered by some API. If we include the fact that only limited set of WS-* features is usually supported in API we have complete mess. Reverse engineering of SOAP message is really time consuming.
推荐答案
你究竟期待什么样的答案？关于互操作性问题或的Web服务规范的复杂性很长的咆哮？或确认简单的事情确实是可互操作的？
What kind of answer do you exactly expect? A long rant about interoperability issue or the complexity of the web service specifications? Or a confirmation that simple things are indeed interoperable?
在一个项目上工作过是我们必须提供Java编写的Web服务被另一支球队被消耗在.NET中，简单的事情工作pretty的好。
Having worked on a project were we had to provide web service written in Java to be consumed in .NET by another team, simple things worked pretty well.
但它开始将变得混乱，一旦我们离开简单的场景。安全，认证，MTOM，是一场噩梦，至少对被琐碎的。
But it starts be get messy as soon as we leave the simple scenario. Security, authentication, MTOM, is a nightmare, at least for from being trivial.
有很多的工具，并实现在Javaland。我知道，太阳新城栈身后的团队做了伟大的工作，并投入了大量的努力，也使东西互操作性与微软合作。然而，我不知道其它实现或工具。
There are a lot of tools and implementations in Javaland. I know that the team behind the Sun Metro stack did a great work and invested lots of effort to also make thing interoperable with Microsoft. I however don't know for other implementations or tools.
我觉得你有能力把自己的见解在这个维基回答，请随时：<一href="http://stackoverflow.com/questions/2810485/how-to-write-web-services-in-java/2810717#2810717">How在Java中编写Web服务。
I you feel competent to bring your own insight in this wiki answer, feel free: How to write web services in java.
这篇关于Web服务互操作性的开发人员无能坏了吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
