On a project that I am currently working on, the team was having some issues consuming JBoss SOAP services. The root of the problem took a while to figure out, as apparently there are very few people that try to consume SOAP services experience the same issue we were encountering and The Google revealed few clues. At first we thought that perhaps the difference was between WSDL 1.1 and WSDL 2.0 and Flex’s lack of support for WSDL 2.0, as that is what the SOAP services were generating. After some initial investigation, we thought we eliminated that as a possibility. Then we discovered that the WSDL that we were consuming contained overloaded methods. Some reinvestigation at the W3C was done to see if perhaps a difference between the WSDL 1.1 or 2.0 specifications was support for WSDL overloading. It turns out the the specs are silent on this issue, so again we eliminated the difference in WSDL versions. Some additional searching after that determined that Flex definitely lacks support for WSDL overloading.
Continue Reading »
Aug
21