tracker issue : CF-3038645

Problem:

[JFERNANDES]CF team needs to certify CF adapters on LCDS 3

This ER is based on Ram advice, right now there is no way to work with CF and LCDS DCD workflow within Flash Builder. 

If I want to use CF + LCDS I can't use DCD workflow for data management (just for remoting). If I use LCDS DCD in Flex Builder, I can't use it with CF since it will only work with LCDS 3.0, so I'm stuck.

Ram says that CF team need to certify CF Adapters on LCDS 3.

FB Related bug   
http://bugs.adobe.com/jira/browse/FB-19580
LCDS related Bug
https://bugs.adobe.com/jira/browse/LCDS-740

Method:


Result:

[Flex]Error invoking service 'data-service': flex.data.adapters.AdapterException
: Unable to locate a fill method for destination 'cfcompany' which matches the f
ollowing parameters: [].
  incomingMessage: Flex Message (flex.data.messages.DataMessageExt)
    operation = fill
    id = null
    clientId = 87E45D05-DED0-DBF6-DDBF-8741C6B3B73F
    correlationId =
    destination = cfcompany
    messageId = 91B36823-3368-E3F0-3431-8741C8F5845C
    timestamp = 1243514784255
    timeToLive = 0
    body =
    [

    ]
    hdr(DSId) = DB379DB4-D00F-0F4E-5BD4-5593E74F2C17
    hdr(DSEndpoint) = cf-rtmp
  Exception: flex.data.adapters.AdapterException: Unable to locate a fill method
 for destination 'cfcompany' which matches the following parameters: [].
        at flex.data.adapters.JavaAdapter.invokeFillOperation(JavaAdapter.java:9
69)
        at flex.data.adapters.JavaAdapter.invoke(JavaAdapter.java:602)
        at flex.messaging.services.MessageService.serviceMessage(MessageService.
java:277)
        at flex.messaging.services.MessageService.serviceMessage(MessageService.
java:218)
        at flex.data.DataService.serviceMessage(DataService.java:565)
        at flex.messaging.AsyncMessageBroker.in(AsyncMessageBroker.java:421)
        at flex.messaging.MessageContext.doIn(MessageContext.java:293)
        at flex.messaging.filters.AsyncMessageFilterChain.in(AsyncMessageFilterC
hain.java:214)
        at flex.messaging.MessageContext.doIn(MessageContext.java:293)
        at flex.messaging.endpoints.BaseSocketServerEndpoint.in(BaseSocketServer
Endpoint.java:441)
        at flex.messaging.MessageContext.doIn(MessageContext.java:293)
        at flex.messaging.endpoints.RTMPConnection.handleTCCommandIn(RTMPConnect
ion.java:784)
        at flex.messaging.endpoints.RTMPConnection.in(RTMPConnection.java:934)
        at flex.messaging.endpoints.RTMPConnection.serviceTCMessage(RTMPConnecti
on.java:1021)
        at flex.messaging.endpoints.RTMPConnection.doRead(RTMPConnection.java:56
2)
        at flex.messaging.endpoints.RTMPProtocolHandler.doRead(RTMPProtocolHandl
er.java:125)
        at flex.messaging.socketserver.Connection$ConnectionReader.run(Connectio
n.java:846)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:907)
        at java.lang.Thread.run(Thread.java:619)

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3038645

External Customer Info:
External Company:  
External Customer Name: João Fernandes
External Customer Email: 4E9A42C244586146992015D5
External Test Config: 05/20/2009

Attachments:

Comments: