Closed
Bug 574324
Opened 14 years ago
Closed 13 years ago
SOAP-Faults for Flash application broken
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: albert, Unassigned)
Details
(Whiteboard: [Fixed in FF6])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.4) Gecko/20100611 Firefox/3.6.4 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.4) Gecko/20100611 Firefox/3.6.4 ( .NET CLR 3.5.30729) Environment: A Flex Application that calls Webservices, loaded by firefox. The Webservice returns SOAP faults (HTTP Code 500) and the flex application should extract and display the error message. Firefox 3.6.3: Everything works fine. Flex can compute the fault object correctly, extract the message and display it. Firefox 3.6.4: With the new Version, the soap fault object in flex is broken, Flex cannot extract the message ("DecodingError", "Error while decoding SOAP Response"). Reproducible: Always Steps to Reproduce: 1. Load a flex application that calls webservices in firefox 2. Use an (for the webservice) incorrect input => The webservice returns a SOAP fault with HTTP Code 500 (e.g. with Apache Tomcat) 3. Let the Flex application display the error message Actual Results: Flex cannot display the message. Expected Results: The message will be displayed.
Updated•13 years ago
|
Version: unspecified → 3.6 Branch
Comment 1•13 years ago
|
||
Reporter -> Are you still experiencing this issue with the latest version of Firefox 5? Does the issue occur with the latest nightly? http://nightly.mozilla.org/
Reporter | ||
Comment 2•13 years ago
|
||
Firefox 5.0: The problem still occurs. Nightly 8.0a1 (2011-07-26): The problem does NOT occur anymore. The Flash application can now evaluate the content of the SOAP FAULT message correctly.
Updated•13 years ago
|
Whiteboard: [Fixed in Nightly]
Version: 3.6 Branch → 5 Branch
Comment 3•13 years ago
|
||
Patrick -> Does the issue still occur in FF 6?
Reporter | ||
Comment 4•13 years ago
|
||
Tim -> No, in FF 6 everything is fine. The problem does not occur anymore.
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Whiteboard: [Fixed in Nightly] → [Fixed in FF6]
You need to log in
before you can comment on or make changes to this bug.
Description
•