We ran into an interesting problem with using queries and web services. This
was on MX 6.1 Windows. This may be known already, though we didn't find
anything about it with an initial search on the forums. We created a
component that has a method that returns a structure which contains a query as
one of its members. On trying to invoke the method, we sometimes got a message
that said something to the effect (I don't have the exact error available right
now) that a querybean wasn't available to deserialize the returned structure
(which contained the embedded query). With a bunch of tracing down, we found
that the problem only existed if there was nothing in the component that was
explicitly set to a datatype of 'query'. In other words, if no method had a
return type of 'query' and no arguments were set to type 'query', then the
problem showed up. As soon as the return type of any method in the component
or the datatype of any argument in any method in the component was set to
'query', it started to work. So, it basically appears that unless CF is told
that it needs to include the query deserializer, it doesn't and embedded
queries aren't processed when the web services is invoked. One way to get
around the problem is to simply include a CFARGUMENT of type 'query' in an
init() method. Actually, I don't believe the init() method even needs to be
invoked -- it seems to be just the presence of the argument that allows CF to
process the structure containing a query as one of its members. d