think we're missing xsd for fql_query_response

[GoogleCodeExporter]

http://groups.google.com/group/facebook-java/browse_thread/thread/82749f1db2149e
ee#

it looks like we're missing another xsd element.

do you want to take this one for us david?  I have a feeling you know
jaxb/xsd more than I..

Original issue reported on code.google.com by fern...@gmail.com on 2 Dec 2008 at 6:01

[GoogleCodeExporter]

One idea is we could manually create the return type in the xsd and then 
compile, as
a temp fix until FB updates their schema.

Original comment by hahna...@gmail.com on 8 Dec 2008 at 4:09

[GoogleCodeExporter]

oh yeah.  we've been totally having to maintain our own xsd, with lots and lots 
of
fixes.. If anyone wants to tailor our xsd, these are the files involved..

facebook.xsd = original (no modifications)
facebook.xsd.diff = patch that we apply to it
src/main/resources/schema.xsd = the xsd we actually compile against.

I maintain the .diff file separately to be anal, and be able to catch changes 
more
easily, if they ever come up with an updated facebook.xsd, then we should be 
able to
figure things out..

Original comment by fern...@gmail.com on 8 Dec 2008 at 5:35

[GoogleCodeExporter]

I've created a new element in schema.xsd which should fix the problem. I need 
to test
this when I have access to facebook.com this evening.

I *haven't* updated facebook.xsd.diff. I'm going to try and work out the 
procedure
(svn command line) for generating this file and will post here:
http://code.google.com/p/facebook-java-api/wiki/XSDSchemas

Original comment by david.j....@googlemail.com on 11 Dec 2008 at 1:56

[GoogleCodeExporter]

Working now... please see new JUnit test for example of how to use the JAXB 
function.

Original comment by david.j....@googlemail.com on 16 Dec 2008 at 11:24

• Changed state: Fixed