rubiii
rubiii
that sounds about right. savon_spec stubs your soap requests, but if you depend on a remote wsdl, savon still needs to fetch it to set up the client.
you're right, wasabi doesn't follow import statements. it's something i'm working on from time to time, but it's not ready yet.
unfortunately no. a decent wsdl parser is not that hard to write, but parsing the xs schema is kinda difficult. i'm still working on it and will let you know...
still no decent support for imports. if anyone wants to give it a go ...
master contains a [major rewrite](https://github.com/savonrb/wasabi/blob/master/CHANGELOG.md) which is not done yet, but already supports wsdl imports. xml schema imports should be supported soon. if you can, please give it a try....
@krisleech the first step only supports fully qualified import locations. i haven't found any information about whether relative URL's are even valid. if they are, it would be good to...
thanks @krisleech
this will be fixed with [savon version 3](http://savonrb.com/version3/) by handing the control of http-requests to the user.
we’re running all specs in a transaction now, which works just fine. ``` ruby around do |example| connection = Sequel.connect(config) connection.transaction do example.run # force rollback raise Sequel::Error::Rollback end end...