Title:
Bug 82821:Add support for deserialising CFCs returned from Remote ColdFusion web services back to their native CFC type rather than a Java proxy stub
| View in TrackerStatus/Resolution/Reason: Closed/Won't Fix/
Reporter/Name(from Bugbase): Phil Haeusler / Phil Haeusler (phil haeusler)
Created: 05/06/2010
Components: Web Services
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Minor / Unknown
Locale/System: English / Platforms All
Vote Count: 0
Problem:
Add support for deserialising CFCs returned from Remote ColdFusion web services back to their native CFC type rather than a Java proxy stub.
Method:
When calling a remote ColdFusion Component as a WebService, if the component returns a ColdFusion component the data is returned as a Java axis stub rather than the CFC type. This means that the calling code must know if it is calling a Local or Remote CFC and act differently on the results. ColdFusion should be able to identify where a component has been returned from a remote web service call, and if a matching local implementation of the CFC can be found then CF should instantiate the local CFC and populate the defined properties rather than just returning the axis java object back to the calling code.This would allow easier creation of distributed coldfusion applications as CFCs could be accessed as local components or through web service without the calling code knowing the implementation.I would expect that this would only include those properties that have been explicity defined with cfproperty in the way that objects are serialised passed to a Flex client over remoting.
Result:
n/a
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3041416
External Customer Info:
External Company:
External Customer Name: Phil Haeusler
External Customer Email: 361F280E425B9CD5992015D5
External Test Config: 05/06/2010Attachments:
Comments: