//AMIS Technology Blog » webservice

Posts tagged webservice

SIG Event

Automatic testing Oracle Service Bus using Hudson, maven and SoapUI

0
A lot of current projects are implementing some sort of service based architecture. Testing in this architecture becomes more complex. When implementing an OSB project with Scrum you test-automation is imperative. Scrum will require more frequent testing of your system. This is only feasible (in time and money) when you automate as much as possible.   Using soapUI you are able to create visually SOAP tests on your OSB implementation and running them against the defined infrastructure (develop, test, acceptance).  SoapUI enables with easy tools to implements verification and validation of the responses of your OSB implementation. When running the test you are also able to set limits in SLA response times on all the calls. This way you are able to monitor depreciation of performance in older parts of your OSB implementation when adding new services.   You can record and edit your SOAP test easy with the soapUI interface and edit it later. When you maven-enable your project it is quite easy running your tests when you implement the “maven-soapui-plugin” (see my other posting http://technology.amis.nl/blog/3061/automated-soap-testing-with-maven).  In the meantime version 3.0 of More >
SIG Event

Publish a WebService from a POJA (plain old Java application) – that is: out of the container using EndPoint class

 

This very brief article will demonstrate a very useful feature of Java 6 Standard Edition – that means: the Java as it is running in any stand-alone application. It is possible – and even extremely simple as it turns out – to have a Java SE application publish a (SOAP) WebService. That is: without using a Web Server or Application Server, your Java application can receive WebService calls. I had heard about this but could not actually believe that I understood correctly. When I met Gerard Davison this week – a very nice and knowledgeable guy working on web services tools for the JDeveloper IDE – he confirmed and explained it to me. 

Through the EndPoint class – part of the JAX-WS implementation – we can instruct the JVM to start receiving SOAP calls on the URL we tell it to listen to and have those calls forwarded to our Java class. Thus it is very simple all of a sudden to for example provide mock implementations of services our BPEL process or ESB needs to invoke. This mechanism makes interoperability between for example .NET and Java very easy – especially in terms of the infrastructure required. And of course in situation where a Java application running outside any More >

Go to Top