title: SOAP web service unit/integration testing
body: <p>My first version of the web service used plain <code>JDBC</code> to connect to the underlying database. I had written my Unit tests for the application using <code>JUnit</code>. I deployed this service on <code>Jboss EAP 6.4</code>. So far so good.</p>
  
  <p>I altered my application code to use Jboss's JDBC connection pool. It seems like <code>Jboss 7+</code> does not allow referring to a data source externally (from outside the server). While the service still works fine , my unit tests are now broken. I am wondering how I can fix this.</p>
  
  <p>I was thinking of re-writing same tests to test the service instead of the application code. One way to do this would be to generate the stubs using wsimport and then write a client. I can then use JUnit to test the client. The problem is one has to manually create the stubs and every time the WSDL changes </p>
  
  <p>I am looking for an efficient way to accomplish this. What would be ideal is a framework that accepts a url for the <code>WSDL</code> (or url to the service) and then allow me to call the service operations.</p>
  
  <p>I am aware that the above is no longer unit tests but integration tests. Is this approach the best way to test a <code>JAX-WS</code> service ? </p>