I am using this code to getting album names list.In that i am getting null value of the nodes.item(0);

Document doc = (Document)client.photos_getAlbums(userId);
org.w3c.dom.NodeList nodes = doc.getElementsByTagName(”album”);
org.w3c.dom.Node node = nodes.item(0);
logger.info(node.toString());

So please give me your suggession for this

as I can see you know alot of developing of facebook apps.

I have a question that havent been answered yet on other sites,
and official forums.

Is there any way to retrive, user messages, news feed and wall content.
Im developing and desktop app, and without this data is my app more likely useless.

Will be very greatfull for help.
Regards

This is with reference to “#2 – Callback URL is not a page, it’s a directory”

Let me how faceBook application will come to know which jsp page it has to call first time or when I click on my canvas URL….. my callback Url directory has 5 jsp pages…

No idea about Java but creating a PHP based app was pretty straightforward.

I would really appreciate your help. As I am stuck.
Here is my code
[code]
com.facebook.api.FacebookXmlRestClient authenticatedClient = new com.facebook.api.FacebookXmlRestClient("my_api", "my_secret");
authenticatedClient.setIsDesktop(false);
authenticatedClient.auth_getSession(authToken);

request.getSession().setAttribute( "facebookClient", authenticatedClient );

org.w3c.dom.Document document = (org.w3c.dom.Document) authenticatedClient.photos_getAlbums(new java.lang.Integer(authenticatedClient.auth_getUserId(authToken)));
org.w3c.dom.NodeList nodes = document.getElementsByTagName("albums");
org.w3c.dom.Node node = nodes.item(0);
out.write(node.toString());
[/code]
I am working on this in a jsp to simply get something working.

Keep up the good work! I’ve bookmarked you and passed your site to a few of my colleagues looking to create mashups with Facebook.

Kudos!

Josh

The idea was this.

HEAD>
STYLE type=”text/css”>
H1 {border-width: 1; border: solid; text-align: center}
/STYLE>
/HEAD>

H1 {border-width: 1; border: solid; text-align: center}

“Get this fabulous Game? <fb:req-choice url=’http://www.facebook.com/add.php?apikey=” + api_key + “‘ label=’Add The Application’ > ”

But i dont get anything for the <fb:req-choice ..> tag.

can anyone help me how can i send invitation from my java code .

Thanks in advance

I started working with after trying to work with the original jar and it makes all the difference in the world. The POJO approach is making the code much more readable. Not to mention all the bugs that were fixed.

I would definitely join in, except for fact that the overriding aim of the project is to be drop-in compatible with the old facebook API – this seems to me a waste of time. There is too little benefit in carrying on implementing within the strictures of an un-maintained and hacked-together API just for the sake of it.

If they were willing to make the API cleaner, I’d be right there :).

http://code.google.com/p/facebook-java-api/

And I agree that having the Pair declared as ‘protected’ essentially means that the API is broken. It makes no sense to have a publicly exposed API call that requires as a parameter a protected data structure. Either the API call should be declared as protected, or the data structure should be declared public.

And of course, there was also no reason for ‘Pair’ to have been nested inside of FacebookRestClient anyways.

My guess is that the code was thrown together fairly quickly, passed basic “Oh, I can write a class that uses this” testing (sure, if you put all your classes into facebook’s package, you’ll be fine), and then they kindly put it up for download. Nothing wrong with that; much preferable to us all having to re-invent the wheel with our own wrappers for the REST calls.

I see your point on the version/updates issue but I doubt that’s going to be a problem in practice, because Facebook’s real API is the REST one, and the java “API” is really just a simple wrapper to that. Any changes that do happen are just going to be the addition of a new method occasionally, which will take all of a few seconds to add to the improved version.

OR…there’ll be a whole new API implementation in java, with better separation into multiple classes and interfaces, in which case we’ll all need to rewrite our own interfacing code anyway :).

Take it or leave it :) if it’s no use to you, that’s fine. For me, I *needed* to refactor this into a proper interface/class separation anyway (I’ve also created a “FakeFacebookClient.java” implementation that fakes the authentication part and makes it easy to test without accidentally doing bad things to the FB servers; using the interface, I can swap this in and out without even having to recompile my code), so I’d already taken the potential (but very small) cost of version updates, and doing some bugfixing at the same time could only be beneficial for me.

public class MyFacebookRestClient extends FacebookRestClient {
protected Logger log = Logger.getLogger(this.getClass());

public MyFacebookRestClient(String apiKey, String secret) {
super(apiKey, secret);
}

public void setUserPreference(int key, String value) throws FacebookException, IOException {
assert (value != null);
assert (key >= 0 && key (”pref_id”, String.valueOf(key)),
new Pair(”value”, value));
}

public String getUserPreference(int key) throws FacebookException, IOException {
assert (key >= 0 && key (”pref_id”, String.valueOf(key))));
log.debug(”Getting user preference: ” + document);
return document.getRootElement().getTextTrim();
}

}

However, I cannot see a way around having to edit FacebookMethod to get new methods (such as the two above) as you cannot extends Enums, this is poor design.

The problem you will face when (or if) FB release a new version is that you will have to re-implement your version of the code, whereas by extending it, you wouldn’t.