search

vipsoft / JiraExtension

Load Features for Behat from Jira issues
MIT License
22 stars 18 forks source link

SOAP UI problems #22

Closed srizzling closed 6 years ago

srizzling commented 10 years ago

We been having a few problems with the current verison of the 2.5 branch.

This is error we are having

SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://mycompany.jira.com/rpc/soap/jirasoapservice-v2?wsdl' : failed to load external entity "http://mycompany.jira.com/rpc/soap/jirasoapservice-v2?wsdl"

The link actual returns a valid WSDL. The extension also worked before, with our own branch that we were maintaining with all the improvements made in a previous PR.

I have reason to believe this is because of the recent upgrades to add proxy configuration. Wasn't exactly sure what the actual cause is. /cc @jeffreyguo

Intial thoughts is that it is trying to inject null params into the proxy config which causes an error within SoapClient

srizzling commented 10 years ago

Would I use something like on-invalid="ignored"for the params or does that not do what I think it does?

robocoder commented 10 years ago

Sorry. Proxy support was a short term solution -- I unfortunately did the bare minimum fix/test to the original PR.

I'm going to change it to a compiler pass, and open up the soapclient options.

srizzling commented 10 years ago

Thats cool no worries!

srizzling commented 6 years ago

Closing this, as its like 4 years old.. I don't use the project anymore :P