No idea smogger914
But what happen in your Java client if you change your query to something less restrictive, e.g.:
SELECT * FROM messages WHERE replies.count(*) = 0 AND depth = 0
Do you get the author email?
OlivierS when I do the SELECT * query the author object doesn't have the email. It looks like this:
"author" : {
"type" : "user",
"id" : "3",
"href" : "/users/3",
"view_href" : "/t5/user/viewprofilepage/user-id/3",
"login" : "blah"
},
I did author.email hoping it would work because I wanted to avoid doing another query to get each authors email. Seems like I will have to...
Just a thought here ... smogger914
It might be a permission issue ... When you're using the API browser, you're logged as an administrator.
When running your JAVA code, is your user authenticated as an Admin, or has he just the API privileges?
That it, I wasn't authenticated in the java side. Doing the recomended oauth approach for a server to server app isn't something I wanted to do. Similar to the concerns expressed in this post. I ended up having to switch to api v1. Thanks for the help OlivierS
