Oh I'm not positive that it's the case (I really don't use CF's web services
very much), but I'm *fairly* sure it is. The original poster will definitely
want to confirm.

On Tue, Mar 24, 2009 at 3:37 PM, Mark Mandel <[email protected]> wrote:

> Ah, in which case, I'll shut my gob ;o)
>
> I wonder why it's inconsistent that way.
>
> Mark
>
>
> On Wed, Mar 25, 2009 at 6:36 AM, Brian Kotek <[email protected]> wrote:
>
>> That's the thing, I'm farily sure that the way it works for Flash Remoting
>> is *not* how it works for web service calls, they're handled by totally
>> separate adapters.
>>
>> On Tue, Mar 24, 2009 at 3:28 PM, Mark Mandel <[email protected]>wrote:
>>
>>> Actually Brian, I expect that if you define your <cfproperty> tags
>>> correctly, CF will look for get() methods like it does with Flex, when it
>>> can't find the variables under 'this' (least I assume this is how it would
>>> work, it's how it works in Flex).
>>>
>>> I'm wondering if the issue is that on server 2, what you are trying to
>>> deserialise to? i.e. what do you expect to get back, the original
>>> TransferObject? a CFC with properties? or just a struct?
>>>
>>> I doubt the webservice would be able to rebuild a TO from scratch for you
>>> on the recieving end, but I would have thought it could build a CFC with
>>> properties, or just a struct pretty easily.
>>>
>>> What is the errors you are getting?
>>>
>>> Mark
>>>
>>>
>>
>>
>>
>
>
> --
> E: [email protected]
> W: www.compoundtheory.com
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer

You received this message because you are subscribed to the Google Groups 
"transfer-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/transfer-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to