On Tue, Sep 21, 2010 at 7:41 AM, Michael <[email protected]> wrote: > And no echoes on the web about this problem, so I kind of conclude > that we're the only ones on earth having it. >
I still think it's *very* odd that this fails in SoapUI, but I suppose it could be a general Java issue ... Might be worth getting on the SoapUI forum/mailing list and asking why that WSDL might fail because it could reveal some general information we could use. Taking these assertions as hypothesis, could you help me to try to > find a way to validate it ? > I probably sound like a broken record at this point but I still think the best course of action to validate what's going on is to start with why it fails in SoapUI. It's just that this is the only WSDL I've ever seen that fails in SoapUI. Granted I don't do a ton with a lot of different web services, but as I said above if we can figure out why it doesn't work there, it might tell us a lot about why it's not working on OpenBD. -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
