Thanks for the ping Bryan, I actually figure it out... the stack trace
wasn't very forth coming in that the error could have been better IMO.
The error was a pretty stupid one that could have been, IMO, caught and
handled better... of course my client is a php one so there is no
compilation on that end which would have picked up on my error in any other
compiled language.
Basically my service call changed from
doSomething(1: String request)
to
doSomething(1: Request request)
So when I was calling doSomething("foo") i was seeing that error because the
type i was passing to the service was not the correct type...
hopefully this will help someone some day...
On Mon, Feb 22, 2010 at 6:10 PM, Bryan Duxbury <[email protected]> wrote:
> Can you tell us what languages you are using on the client and server? Is
> there a relevant stack trace?
> -Bryan
>
> On Mon, Feb 22, 2010 at 6:25 AM, Noam Wolf <[email protected]> wrote:
>
> > I'm seeing this error for the first time. Looking at where the error is
> > thrown it looks like maybe the object that is returned from the rpc is
> not
> > the expected one.... is that true? what does this mean if both the server
> > and client are using the same .thrift file?
> >
> > --
> > Best Regards,
> > Noam Wolf
> >
>
--
Best Regards,
Noam Wolf
