flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Michas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-26969) Custom headers set for the HTTPMultiService class are not being used by the operation
Date Mon, 30 Dec 2013 14:54:52 GMT

    [ https://issues.apache.org/jira/browse/FLEX-26969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858847#comment-13858847

Jason Michas commented on FLEX-26969:

Can this be reopened? As of 4.10 this issue is still unresolved. The same steps as outlined
in the OP cause the same error/problem. Existing workaround (setting operation headers to
null to allow propagation of MultiService headers) continues to work. 

Cant the operations have headers=null by default? 
It seems like a simple fix that would allow us to use the data centric tools in Flash Builder
without having to manually edit each generated service code file.

> Custom headers set for the HTTPMultiService class are not being used by the operation
> -------------------------------------------------------------------------------------
>                 Key: FLEX-26969
>                 URL: https://issues.apache.org/jira/browse/FLEX-26969
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: RPC: HTTPService
>    Affects Versions: Adobe Flex SDK Previous
>         Environment: Affected OS(s): Windows
> Affected OS(s): Windows 7
> Language Found: English
>            Reporter: Adobe JIRA
>            Assignee: Adobe JIRA
> Steps to reproduce:
> 1. Create an instance of HTTPMultiService and add an operation to the same
> 2. Set custom headers to HTTPMultiService
> 3. Invoke the operation
>  Actual Results:
>  You will observe that the operation being invoked will not send the custom headers set
in the HTTPMultiService.headers property.
>  Expected Results:
>  Custom headers set in HTTPMultiService should be passed when the operation is invoked.
>  Workaround (if any):
>  In mx.rpc.http.Operation, there is a function called getHeaders() which will send the
headers set in HTTPMultiService only if the headers property of the Operation is set to null.
But in the AbstractOperation, the headers property is initialized when it is declared. Due
to this headers instance is never null and hence the headers in HTTPMultiService are not being
> As a workaround, you can manually set the "headers" property of the Operation to null
to force the headers set in HTTPMultiService to be passed.

This message was sent by Atlassian JIRA

View raw message