I’ve found soapUI a valuable tool when working with web services. I previously wrote about how to get started and some test case basics here, here and here. I just want to add a few more tips I that took me a little bit of trying and reading to figure out:
Continue Reading →
If you missed the first two parts of this series, you may want to check them out first here and here. Today I want to show a few more enhancements to make a test case more flexible. We’ll be using the simple add method of the Arithmatics service to calculate the beginning of the Fibonacci Sequence (Wikipedia).
Continue Reading →
In my previous post I’ve shown how soapUI can quickly create and run SOAP requests for you. Now I want to create a simple test case to show a few features that can be used for unit and load testing.
Continue Reading →
soapUI is a web service testing tool by eviware. I found it extremely useful for trouble-shooting, unit testing and even load testing web services. soapUI generates SOAP test requests based on WSDLs and makes it very easy to work with the actual XML. There is no messing with web service proxies (clients) or writing programs; only for complex test scenarios you may have to do a little scripting. soapUI Pro adds a lot of features to simplify those advanced tasks but I will restrict this introduction to features available in the freely available open source version.
Continue Reading →
Like many of us, I never learned the JavaScript formally but started dabbling in it, using a similar-looking language (Java) as base for my coding style. Here’s another feature that seems quite simple but it took me a while to realize how powerful it really is because of my Java bias. In Java or .Net, information about an object can be gathered and generic operations executed at runtime via a mechanism called Reflection. Since it adds a certain overhead and is cumbersome to code, it is used rarely in everyday code (although frameworks like Spring frequently use it internally). In JavaScript, on the other hand, it’s not only very easy to discover object details at runtime and perform operations in a generic way, but it’s even possible to add and remove object properties themselves.
Continue Reading →
This is the last part of the Spring.NET Web Service Exporter example. I’ve shown the Web.config entries and the application details. Now we are only missing the Spring configuration file – named Continue Reading →Spring.xml in my example. This is the whole configuration file (note that I have not set up transaction handling or other aspects in this example):
In my previous posts here and here, I explained the advantages of using Spring.NET’s Web Service Exporter and how to initialize Spring and Spring Web Service Exporting in the Continue Reading →Web.config file. Now we need a service to export. Below I’ve listed the most important parts of the application – for brevity, I’ll omit imports and namespace declarations.
In my previous post I discussed advantages of choosing the Spring.NET web service exporter over the standard .NET mechanism through decoration with attributes. Now I would like to show how to set up an web service exporter. Basic configuration details for the Spring.NET Web Service Exporter can be found in the Spring.NET Documentation but my example will add some important aspects like registering custom objects and session access that are not included in the above link.
Continue Reading →
Spring.NET is a .NET port of the popular Java Spring framework. It simplifies implementation and maintenance of large applications by:
Continue Reading →
JavaScript has become one of my favorite languages. It is extremely flexible and powerful. It is not hard picking up the basics if you have programmed Java or C# before. But there are many features that are very hard to emulate or simply not possible in those languages. One example is the Function object’s call() operator. It allows execution of any function in the context of an object passed into the function, or, in other words, changing the Continue Reading →this reference a function uses for the duration of the call.
Connect with us: