WebServiceGatewaySupport vs WebServiceTemplate的优点(Advantages of WebServiceGatewaySupport vs WebServi

WebServiceGatewaySupport vs WebServiceTemplate的优点(Advantages of WebServiceGatewaySupport vs WebServiceTemplate)

我必须使用Spring WS实现一个web服务客户端。

我已阅读http://static.springsource.org/spring-ws/site/reference/html/client.html上的文档，但我不清楚扩展WebServiceGatewaySupport与直接在我的服务中使用WebServiceTemplate的优点类。

据我从源头可以看出， WebServiceGatewaySupport只有一些WebServiceTemplate的封装方法和一些初始化支持。

那么为什么我应该扩展WebServiceGatewaySupport而不是直接使用WebServiceTemplate ？

谢谢！

I have to implement a webservice client using Spring WS.

I've read the documentation at http://static.springsource.org/spring-ws/site/reference/html/client.html but it's not clear to me what are the advantages of extending WebServiceGatewaySupport versus directly using WebServiceTemplate in my service class.

As far as I can tell from the source, the WebServiceGatewaySupport only has a couple of wrapper methods for the WebServiceTemplate and some initialization support.

So why should I extend WebServiceGatewaySupport instead of directly using a WebServiceTemplate ?

Thank you!

最满意答案

我认为这一切总结起来（在您链接的客户端引用中找到）：

或者，可以考虑从Spring-WS的WebServiceGatewaySupport方便的基类中派生出来，该基类提供了方便的bean属性来实现简单的配置。 （你不必扩展这个基类......它仅作为一个便利类提供。）

所以，如果WebserviceTemplate提供了所有你需要的，那可能就足够了。 如果您需要额外的任何东西，您可以使用WebServiceGatewaySupport作为示例，了解如何在WebserviceTemplate包装您自己的便捷方法。

在我的客户端软件中，我只需在我的@Configuration类中配置WebserviceTemplate ，如下所示：

@Bean public WebServiceTemplate webServiceTemplate() { WebServiceTemplate template = new WebServiceTemplate(); template.setMessageFactory(messageFactory()); template.setDefaultUri(defaultUri); template.setMarshaller(marshaller()); template.setUnmarshaller(marshaller()); template.setInterceptors(new ClientInterceptor[] {interceptor()}); return template; }

（所有的方法调用都是对配置中其他方法的引用，这些在本例中并不相关）。 我可以在我的代码中的任何地方使用该bean来发送消息。

I think this sums it all up (found in the client reference you linked):

Alternatively, consider deriving from Spring-WS's WebServiceGatewaySupport convenience base class, which exposes convenient bean properties to enable easy configuration. (You do not have to extend this base class... it is provided as a convenience class only.)

So, if the WebserviceTemplate offers all you need, that'll probably suffice. If you need anything extra you can use the WebServiceGatewaySupport as an example on how to wrap your own convenience methods around the WebserviceTemplate.

In my client software, I just configure the WebserviceTemplate in my @Configuration class like this:

@Bean public WebServiceTemplate webServiceTemplate() { WebServiceTemplate template = new WebServiceTemplate(); template.setMessageFactory(messageFactory()); template.setDefaultUri(defaultUri); template.setMarshaller(marshaller()); template.setUnmarshaller(marshaller()); template.setInterceptors(new ClientInterceptor[] {interceptor()}); return template; }

(All the method calls are references to other methods in the configuration which aren't that relevant in this example). I can use that bean everywhere in my code to send messages.