This content has been marked as final. Show 3 replies
The problem might be that you need to expose information about your "User" type. Make sure your "User" component has cfproperty tags defining the fields that you set into it (id, fname, lname, email).
Also whenever our webservices return an array of a custom type (like "User"), we also put in the webservice component a function called "get<custom component>Type" (e.g. "getUserType") with a returntype of "User" which just creates a "User" component and returns it. This will cause details about the "User" type to be included in the WSDL which then allows the custom type to be handled/parsed more appropriately by clients of the webservice.
I don't know if this helps your case, but I've run into several clear bugs in CFMX 7.0.1 and CFMX7.0.2(beta 3) with web services. It's about registering and invoking the web services, since they run okay on WebLogic 8.1SP5, and are thoroughly multiplatform-tested (Java, Jsp, .NET). The web services are purely J2EE/Java-based, no CF involved.
You register a web-service A on server A - which works. Then you try to register an identical web service (of course with a different alias/name) on server B, but no, it doesn't work without restarting the CF Server first.
Let's clear all the web services and restart CF Server again. Now, to verify the behaviour, let's register a web service on machine B. OK, fine. And let's register again the first web service on Server A. Won't work without restarting CF.
Having restarted CF several times, registering the two (actually three now web services, calling any method from server A works. Let's try to call any method from B or C. Crash. Stack trace. Boom.
Case 4, 5.... Let's start invoking from B or C. The first invoked server always works, the rest don't. Have to restart CF always between the invocations.
It's driving me nuts, rendering the whole web services feature partially unusable with ColdFusion.
I've left a few bug reports to Adobe a couple weeks ago, so sopefully we'll see a hotfix or something in the near future.
If you recognized any of these scenarios in Your case, you might want to suspect CF. Tell us was it in your code?
I'm having the same problem as outlined above with the same error message. I'm returning an array of complex Java types, not CFCs. It works well when returning a string or int.
I'm running 7.0.2. Any ideas since this makes the web service unusable for CF.