book-api | Book API demonstrates the RESTful web services | Object-Relational Mapping library

you don't need parse to json before return on springboot. Spring boot will do this for you ( using jackson lib for default )

try this:

After trying with the uploaded repo. I've confirmed the error lies at the following place

config.js

Add publish_to_groups permission to the access token and the request for the post should be with parameter published: true. It appears to have a bug in the graph api or lack of information in the official docs.

Currently in order to publish a page post with multiple photos you will need to:

• upload individually the photos and obtain their IDs
• use PAGE access token which contains publish_to_groups permission
• attach all photo IDs with attached_media[0..N]: {"media_fbid": "PHOTO_ID"}
• currently the request for publishing the post fails if it's with parameter published: false, so it needs to be published: true

All of this does not make really sense to me, so I opened a bug report in the developers platform of Facebook. It does not looks right during development of the App to publish live posts to the page...

I'll edit the answer once I have a feedback.

You start with

The version of this project is 7.2ga1 and I use Liferay Tomcat 7.3.5

and you state that you've tried target platform. In fact, the build dependencies show that you are still using target platform, and most likely your target platform is set to a different version than the runtime you're using: Target Platform should at least match the major/minor part (e.g. 7.3.x), there are different opinions about the depth of it. Simplest: Make your target platform match the version you use at runtime.

Your service can't import the API bundle, because the API bundle doesn't deploy: It has a dependency on a Liferay kernel that is not there at runtime due to the version mismatch introduced at compile time (through the target platform).

Set the target platform to 7.3.5, do a clean rebuild and your dependencies should match your runtime version

Answering your comment: This way you'll have the correct dependency declared in your plugin, and it will be matched at runtime. Your build.gradle doesn't contain any version numbers, because those versions come from the target platform declaration. If you override any dependency's version in bnd.bnd (to 0), the version will be ignored, but there's no guarantee that you have compatible code that indeed can deal with what they find at runtime. Just switching off the correct dependency might work now, but can fail any time that the API you're dependent on is updated with a binary incompatible change.

The PHP SDK apparently does not have a dedicated section in the FB docs any more, they are redirecting directly to GitHub.

If you check the /docs/reference folder there and look for the class in question, you can find the available public methods listed there though.

https://github.com/facebookarchive/php-graph-sdk/blob/master/docs/reference/FacebookResponse.md

getHeaders()
public array getHeaders()
Returns the response headers that were returned.

Interesting question! From your link:

The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a modified version of the one residing on the origin server. [emphasis mine]

This means you must PUT the entire resource (changes and and non-changes alike). Very few APIs are designed that way.

From the spec for POST:

The POST method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line. POST is designed to allow a uniform method to cover the following functions:

• Annotation of existing resources;

Many/most APIs have adopted POST as the way to update objects.

Some additional thoughts here: https://stackoverflow.com/a/25909372/379538

From the look at the source code here and here, $insights is the instance of FacebookAds\Cursor class, so you can use:

Domain name as "localhost" is not an option when developing and testing a React application with the Facebook Chat Plugin.

1. In the operation system hosts file have to add a new entry, for example: 127.0.0.1 react-with-chat-app.com
2. On Windows run command prompt as administrator with ipconfig /flushdns command.
3. Add .env file in the root of the React project, and add your new hostname: HOST=react-with-chat-app.com
4. Add http://react-with-chat.com/ to the Facebook Site whitelist domains array, and change the Facebook App's website also to http://react-with-chat.com/.
5. Restart React application, and access using: http://react-with-chat-app.com:3000, and test the chat functionality.