Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Later
-
Adobe Flex SDK 3.3 (Release)
-
None
-
None
-
Affected OS(s): All OS Platforms
Language Found: English
Description
Steps to reproduce:
1. run mxunit tests:
a. sync depot
b. make sure you have sdk, webtier.war configured(sdk to depot/flex/qa/sdk/build folder, also you need configure build.properties under depot/flex/qa folder to make sdk.dir set to depot/flex/qa/sdk/build. webtier.war should be in depot/flex/qa/sdk/dist folder)
c. run ant -Dfeature=webService flexunitAutomation, monitor tomcat launching, then stop the script
this will deploy the war file
d. start tomcat server
2. from browser, open:
http://localhost:8400/qa-regress/testsuites/mxunit/tests/proxyService/webService/bugs/171942/bug171942.mxml
.
Actual Results:
wsdl is loaded without an error and test fails
more information, please see bug report:
http://frpbugapp.macromedia.com/bugapp/detail.asp?ID=171942
"The problem is that it is a wrapped document-literal style service that makes use of input and output parameters across three XML Schemas. However, the problem is that each of these Schemas exist in their own namespaces but are making references to other schemas by a namespace that is not imported and thus not in scope.
For example, The getAttachmentList operation defines the output message part with the getAttachmentListResponse element defined in the Schema with targetNamespace http://modules.alexandria.optimal.com. The problem is that this element's complexType refers to another element by name as ns1:attachmentList. The ns1 prefix is defined on the wsdl:definition as xmlns:ns1="http://www.optimalpayments.com/moduleservices", however this namespace is not in scope for the Schema with the targetNamespace http://modules.alexandria.optimal.com. While the prefix is known from a high node in the XML document, this doesn't mean it is in scope for the Schema. You would need to import the http://www.optimalpayments.com/moduleservices namespace explicitly into this Schema in order to refer to its types.
Expected Results:
expect loading the webservice, receives: fault "WSDLError - Runtime exception Cannot resolve element definition for ref 'http://www.optimalpayments.com/moduleservices::attachmentList'."
and
test should pass
Workaround (if any):