Stevo Slavic

Show:

What's happening?

  • Configuring endpoint per interface in soapui maven plugin

    Please implement support in soapui maven plugin for configuring endpoint per interface. Currently one can do that through soapui GUI, but not through maven plugin.

    2009-11-10 00:35:44 UTC in soapUI

  • Comment: Spring fails to find @Component bean with classpath scanning

    Problem is in JarClassLoader, it's "protected void loadByteCode(InputStream is, String jar, String tmp, Manifest man) throws IOException" method ignore directories, which Spring's component scan tries to find via call to "public Enumeration findResources(String name) throws IOException".

    2009-10-22 12:47:57 UTC in One-JAR(TM)

  • test.FailIgnore doesn't ignore test failure

    Configuring test.FailIgnore to true doesn't make soapui-maven-plugin to ignore test failure.

    2009-10-05 07:51:52 UTC in soapUI

  • checkstyle-m2eclispe integration dependencies

    checkstyle-m2eclispe integration seems to depend on eclipse-cs 5.0.1. Will there be support for 4.4.3? IMO it would be best if checkstyle-m2eclispe integration would use whichever eclipse-cs is installed, unless 4.4.x needs significant changes to support m2eclipse integration. Currently even if one just installs 4.4.3 and checkstyle-m2eclispe integration, checkstyle-m2eclispe integration will...

    2009-09-30 09:58:39 UTC in Eclipse Checkstyle Plug-in

  • Comment: Spring fails to find @Component bean with classpath scanning

    +1.

    2009-09-08 14:08:41 UTC in One-JAR(TM)

  • Comment: Test case fails even though all test steps are valid

    Just attached example project which demonstrates the bug. It's a Maven2 Java project. Bug was successfully reproduced on following platform: Apache Maven 2.2.1 Java version: 1.6.0_16 Default locale: en_US, platform encoding: Cp1252 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows".

    2009-09-03 11:05:31 UTC in soapUI

  • Comment: Test case fails even though all test steps are valid

    I'm suspecting that this occurs only when web service response is 404 error but with empty content (content-length: 0). This happens if web service is a web application project without registered 404 page and without application server serving it's default one - like on jetty (6.1.19) server. Trying to create appropriate project that would show the bug.

    2009-09-03 09:32:25 UTC in soapUI

  • Comment: Test case fails even though all test steps are valid

    To be more precise, test step with single script assertion fails even though assertion is (green and) marked as valid. A WS service handles request based on QName of root element in soap body. If request is soap envelope with empty soap body service should return HTTP 404 error and test step verifies this expected behavior using script assertion ( assert...

    2009-09-01 11:13:13 UTC in soapUI

  • Test case fails even though all test steps are valid

    A test case with multiple test steps fails in soapui-maven-plugin v3.0 although all test steps assertions are valid. Same test case is valid when run in soapUI eclipse plugin v2.5.1. Two of the test steps have a single script assertion each: "assert messageExchange.responseHeaders["#status#"].contains("HTTP/1.1 404 Not Found")" - for these test steps a response has status 404, empty content, and...

    2009-08-16 21:02:07 UTC in soapUI

  • Support projectFile to be classpath resource reference

    maven-soapui-plugin has a parameter, projectFile which configures plugin with a path to the soapUI project file. Currently (in v3.0 of the plugin) it seems that referencing class path resources via projectFile is not possible. This would come handy if one wants to execute the same soapUI project/tests against different web services project modules (all of them sharing WS operation subset). A...

    2009-08-14 12:04:17 UTC in soapUI

About Me

  • 2007-03-30 (3 years ago)
  • 1757269
  • sslavic (My Site)
  • Stevo Slavic

Send me a message