Forum Discussion

embs's avatar
embs
New Contributor
16 years ago

messageExchange.requestContent does not return valid xml in Soap3.0

On a Script Assertion written using SoapUI 2.5 ,  the method call messageExchange.requestContent returned valid xml - and thus could be passed as a parameter into groovyUtils :

    groovyUtils.getXmlHolder( messageExchange.requestContent )

When running the same Script Assertion after installing SoapUI 3.0, messageExchange.requestContent now reuturns the pre/post-amble to the xml content as well:

Tue Jul 28 15:09:47 EST 2009:INFO:messageExchange.requestContent
------=_Part_73_19105844.1248757714698
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-ID:



------=_Part_73_19105844.1248757714698--


and therefore groovyUtils.getXmlHolder( messageExchange.requestContent )
fails ( returns null ).

Is anyone knowing why this would happen ? Is there a fix/workaround ?
 

4 Replies

  • Hi!

    thanks for reporting.. this sounds like a bug to me.. is this a standard soap request/response?

    regards,

    /Ole
    eviware.com
  • Hi again,

    this should be fixed in upcoming nightly-build, great thanks for reporting!

    regards!

    /Ole
    eviware.com
  • embs's avatar
    embs
    New Contributor
    Thanks guys

    Also, much appreciate if you could give me a way to track when the fix is in (or if you could reply to this post ?)
  • Hello,

    The nightly builds are automatically built each night, so if Ole put in a fix it should be in any of the builds after July 29th. The nightly builds are available here, you should try the latest one.

    Regards,
    Dain
    eviware.