[FLEX-24589] WebService request (setting value in the request from text field)

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Adobe Flex SDK 3.2 (Release)
• Component/s: Data Binding
• Environment: Affected OS(s): Windows; Affected OS(s): Windows XP; Browser: Firefox 3.x; Language Found: English
• Assignee: Unassigned
• Reporter: Adobe JIRA
• Created: 25/Jul/10 10:00
• Updated: 25/Jul/10 10:00

Description

Steps to reproduce:
1.Create a simple WebSerice component with one operation and xml request.
<mx:WebService id="userRequest" wsdl="WSDL.wsdl">
<mx:operation name="Login"
fault="mx.controls.Alert.show(event.fault.faultString)"
result="responseData(event)" resultFormat="xml">
<mx:request format="xml" xmlns="http://www.test.com/schemas/Test/Schema.xsd">
<root>
<a>

{temp.text}</a>
<a>3</a>
<b>
<c>1</c>
<d>2</d>
</b>
</root>
</mx:request>
</mx:operation>
</mx:WebService>

2. Creating one button and one text field in order to add value for {temp.text}

<mx:TextInput x="10" y="10" id="temp"/>
<mx:Button x="178" y="10" label="Button" click="

{userRequest.Login.send();}

"/>

3. After stating the application, enter some text in the text field (id="temp") and click on the button in order to send the request.

Actual Results:
The value from the text field isn't sent in the request.
This is the request that is sent to the service:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<root xmlns="http://www.test.com/schemas/Test/Schema.xsd">
<a/>
<a>3</a>
<b>
<c>1</c>
<d>2</d>
</b>
</root>
</SOAP-ENV:Body>

Expected Results:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<root xmlns="http://www.test.com/schemas/Test/Schema.xsd">
<a>VALUE FROM THE TEXT FIELD</a>
<a>3</a>
<b>
<c>1</c>
<d>2</d>
</b>
</root>
</SOAP-ENV:Body>

Workaround (if any):