Forum Discussion

Daniela_Lawn's avatar
Daniela_Lawn
New Contributor
15 years ago

Proxy settings in 3.5.1

Hi there,

We use the soapUI 3.5.1 for our testing and need to use proxy as well. However that version of the soapUI has a few bugs (that the proxy settings are not picked up and that proxy credentials can be keyed in only in the clear text).

Because we use 3-rd party library for our soap UI tests we have an issue with moving to the newer version of the soapUI (like 3.6.1 or 3.6.2) where these bugs have been fixed.

Is there a way how you can fix the proxy issues in the 3.5.1 version and provide us with the updated jar for the proxy class?
Or maybe you can provide a workaround...
I thought you should be able do it as part of your support.

Thanks in advance,
Vitaly

5 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hi Vitaly,

    we don't usually created patches for older versions of soapUI; what is the reason you can not use the 3rd party library with soapUI 3.6.x ?

    regards!

    /Ole
    eviware.com
  • Daniela_Lawn's avatar
    Daniela_Lawn
    New Contributor
    15 years ago
    Hi Ole,

    We use axis2 framework and it started to fail when we tried to use soap UI 3.6.1.
    You can see some extracts from our logs below.
    However I'm not sure what would be the best way to proceed.

    14:38:09,988 DEBUG [AbstractDefinitionContext] Loaded Definition: ok
    java.lang.IllegalArgumentException: Null InputStream is not a valid argument
    at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:614
    )
    at com.ctc.wstx.stax.WstxInputFactory.createXMLStreamReader(WstxInputFac
    tory.java:317)
    at org.apache.neethi.PolicyEngine.getPolicy(PolicyEngine.java:79)

    ... skipped ....

    java.lang.NullPointerException
    at org.apache.rampart.builder.BindingBuilder.getSignatureBuider(BindingB
    uilder.java:248)
    at org.apache.rampart.builder.TransportBindingBuilder.doX509TokenSignatu
    re(TransportBindingBuilder.java:257)
    at org.apache.rampart.builder.TransportBindingBuilder.build(TransportBin
    dingBuilder.java:144)
    at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:140)
    at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:64
    )
    at org.apache.axis2.engine.Phase.invoke(Phase.java:317)
    at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
    at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:429)
    at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisO
    peration.java:401)
    at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(Out
    InAxisOperation.java:228)
    at org.apache.axis2.client.OperationClient.execute(OperationClient.java:
    163)
    at com.microsoft.schemas.ws._2008._06.identity.securitytokenservice.Secu
    rityTokenServiceStub.trust13Issue(Unknown Source)
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hi!

    hm.. just so I get this right; the exact same request works with 3.5.1 but fails with 3.6.1 ? In that case I wonder if you could send me the content of the Raw request tab after sending the request from both 3.5.1 and 3.6.1 so we can try to figure out what is different..

    I hope this is not asking for too much, great thanks for your help!

    regards,

    /Ole
    eviware.com
  • Daniela_Lawn's avatar
    Daniela_Lawn
    New Contributor
    15 years ago
    Hi Ole,

    You are not asking too much. However in our tests the first step is a groovy script in which we call another web-service to get a special secured token. Then using this token we generate the actual request message and set it as the content of the next request step.

    So when we moved to 3.6.1 the groovy script execution started to fail.
    The 3-rd party libraries which fail don't give us too much information - see log in my previous post.

    I'm not sure whether you want to reproduce the whole environment...