|
|
||
Arun Gupta's Blog
«Screencast #Web10: CRUD using jMaki and JPA |
Main
| JRuby 1.0.2 released - Improved Windows experience and Rails 1.2.5 support »
TOTD #16: Optimizing Metro Stubs by locally packaging the WSDLPosted by arungupta on November 09, 2007 at 07:14 AM | Comments (2)When Metro stubs are used to invoke a Web service endpoint, two invocations are made over the network - one for retrieving the WSDL and the other for sending the request message. The second invocation is easy to explain because that's when the actual message is sent to the endpoint. The first invocation to retrieve the WSDL is necessary because the generated stubs contain only the portable method signatures and annotations. All the binding specific information, such as quality-of-service policy assertions, are retrieved at the runtime. This approach was taken because of two reasons:
However if the WSDL is not expected to change then you can consider locally packaging the WSDL with the client. In this case the locally packaged WSDL, instead of accessing over the network, is used to retrieve the binding information. Metro runtime is integrated in GlassFish and can also be installed on Tomcat. Vivek explained the several Tooling options with Metro - NetBeans IDE being the most comprehensive. Several screencasts are available to get you started with Metro. Technorati: webservices projectmetro glassfish netbeans performance Bookmark blog post: CommentsComments are listed in date ascending order (oldest first)
| ||
|
|