2/ the, umm, let me call it "recognizer" that parses an incoming SOAP document to see what rails controller action should get it blows up if your spec says "X contains 1 Y" and the actual doc contains 2 doesn't set a flag blows up BEFORE your handlers are run
-
-
Show this thread
-
3/ ...and there's no way in the spec (which you write to help the recognizer do its job) to specify "multiples" SOOOO I think the solution is to remove the repeated element from the spec entirely HOWEVER that means that the recognizer, which ALSO parses the incoming SOAP
Show this thread -
4/ and uses it to populate the Rails framework 'params' variable, won't populate those element(s) into params ...which means that in my code, if I want to inspect them, I need to rederive them by looking at request.raw_post FML
Show this thread -
This Tweet is unavailable.Show this thread
-
6/ and .... update spent another 2+ hrs on this horror because even after I gave up on the washout gem and started parsing the XML manually ... Nokogiri gem uses a different delimeter for namespaces than XML does "<soap-env:Header>" is parsed with "soap-env|Header"
Show this thread -
7/ astronaut 1: wait, SOAP is a lie? astronaut 2, with gun: always has beenhttps://twitter.com/notPotus42/status/1308162874137874434 …
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.