This post is a continuation of the previous post where we connected a database to Java Shindig. Now I will use my own database with shindig. In other words when a social request is executed, the data will be taken from my own social database.
To start with you have to have a working version of shindig-database connection as described in previous post.
1) Imagine I have a social MySQL database with only one table 'people' and three colums:
This will be my own social database that I want to connect to Shindig. (To make life easier you can just remove tables and redundant columns from shindig database (generated in previous post) and rename 'person' table to 'people' table). Add the following data into table: .
2) Now we have to tell shindig not to generate database every time it loads. Normally it should be possible to do through java/samples/src/main/resources/META-INF/persistence.xml but it seems Shindig's samples implementation doesn't take those properties from that file. So I had to change the following file: java/samples/src/main/java/org/apache/shindig/social/opensocial/jpa/eclipselink/Bootstrap.java
3) Now we have to change the file java/samples/src/main/java/org/apache/shindig/social/opensocial/jpa/PersonDb.java so that it takes needed for us data from the database. Read the explanations in comments.
4) Now recompile project and run jetty server
5) Now execute a social request in your browser.
You should get back a json response (I had to reload page 3 times to get it)
So, now you are ready to change PersonDb.java, etc. files according to your own social database implementation! Concerning JPQL syntax I found the following useful: JPQL Language Reference
Monday 19 July 2010
Monday 12 July 2010
Java Shindig: how to connect to real database (Updated July-2011)
I decided finally to switch to Java Shindig from PHP Shindig due to the better support and development of the first one. I had my working shindig installation for PHP with my own social database. I wanted to have the same with Java Shindig. It turned out to be much harder to set it up in Java (maybe because of my java and maven ignorance). In PHP I only changed the database settings and added my own PersonService, AppDataService implementations. In Java the concept is the same but the way it is done was not that obvious for me. So, here is what I did.
1) I downloaded the shindig trunk from here:
2) To use database in Shindig one could take advantage of existing in shindig "samples" project that uses JPA and EclipseLink to connect to the database from Java. This how I compile the project:
3) First of all we need to add JPASocialModule.java into Shindig's Guice modules. This module will provide real database implementations for PersonService, AppDataService, etc. One should add this module in java/server/src/main/webapp/WEB-INF/web.xml. Some default Guice modules should be removed from this file in order to avoid compilation problems. This is how this file looks for me.
I also had to change the SocialApiGuiceModule.java to add a sample OAuthDataStore. I also had to change the JPASocialModule.java to add a sample implementation for MediaItemService, MessageService, AlbumService. 4) We will have to recompile shindig with database support now. We have to change 3 files. trunk/pom.xml - add samples module to default "all" and "run" and to dependencyManagement.
trunk/java/server/pom.xml - add dependency on shindig-samples
trunk/java/samples/pom.xml - add dependency on mysql driver (since I use mysql database)
Now to compile the project with maven command as in 2)
5) Generate signing keys for oAuth with the following commands.
Add the keys information into java/common/conf/shindig.properties. Don't forget the full path to your oauthkey.pem!! 6) Add your database information to java/samples/src/main/resources/socialjpa.properties. I use mysql database, so my settings are mysql specific. 7) Create database shindig and give access to it for user "shindig" with password "shindig". 8) Compile now the project and run jetty server according to 2). The tables will be created in the database based on shindig's default database structure. 9) When database is created, add manually a row to the Person table with oid = 1, person_id = 1 and display_name = Shindig User 10) Run the jetty server as explained in 2) (Ignore errors that tables already exist). Now execute a social request in your browser. You should get back a json response (I had to reload page 3 times to get it) So, this is a proof-of-concept step on how to connect Shindig to a real database. Next will be how to change shindig classes to connect to my own database!
1) I downloaded the shindig trunk from here:
2) To use database in Shindig one could take advantage of existing in shindig "samples" project that uses JPA and EclipseLink to connect to the database from Java. This how I compile the project:
3) First of all we need to add JPASocialModule.java into Shindig's Guice modules. This module will provide real database implementations for PersonService, AppDataService, etc. One should add this module in java/server/src/main/webapp/WEB-INF/web.xml. Some default Guice modules should be removed from this file in order to avoid compilation problems. This is how this file looks for me.
I also had to change the SocialApiGuiceModule.java to add a sample OAuthDataStore. I also had to change the JPASocialModule.java to add a sample implementation for MediaItemService, MessageService, AlbumService. 4) We will have to recompile shindig with database support now. We have to change 3 files. trunk/pom.xml - add samples module to default "all" and "run" and to dependencyManagement.
trunk/java/server/pom.xml - add dependency on shindig-samples
trunk/java/samples/pom.xml - add dependency on mysql driver (since I use mysql database)
Now to compile the project with maven command as in 2)
5) Generate signing keys for oAuth with the following commands.
Add the keys information into java/common/conf/shindig.properties. Don't forget the full path to your oauthkey.pem!! 6) Add your database information to java/samples/src/main/resources/socialjpa.properties. I use mysql database, so my settings are mysql specific. 7) Create database shindig and give access to it for user "shindig" with password "shindig". 8) Compile now the project and run jetty server according to 2). The tables will be created in the database based on shindig's default database structure. 9) When database is created, add manually a row to the Person table with oid = 1, person_id = 1 and display_name = Shindig User 10) Run the jetty server as explained in 2) (Ignore errors that tables already exist). Now execute a social request in your browser. You should get back a json response (I had to reload page 3 times to get it) So, this is a proof-of-concept step on how to connect Shindig to a real database. Next will be how to change shindig classes to connect to my own database!
Tuesday 9 March 2010
Apache Shindig: Java vs. PHP (part 2)
In my previous post I decided to make the Friends Gadget work on PHP Shindig. I managed to do so, thus I will stay with PHP version of Apache Shindig.
I will use the gadget that lists friends of the user. Notice that http://shindig/ is where you have your shindig installation (http://localhost:8080, for example). Here is the gadget code:
Now we want Apache Shindig to get a list of friends for a user with id=2 from my database 'graaasp_development'.
Here is a url that does it.
The most important parameter here is a "st" parameter, that stands for security token.
Owner_id means id of the owner of the gadget. Viewer_id means id the current user watching the gadget.
Application_id means the id of the gadget instance in the database.
In other words, in 'graaasp_development' database we have a gadget with id=12. Owner of this gadget is user with id=2 and the same user watches the gadget at the moment.
Now we have to add some code to shindig to let it know that 'graaasp_development' database should be used as a backend for gadgets requests.
First of all in the folder "shindig/php/config/" we should create a file 'local.php' with the following content.
This will force Shindig to use the code specific to the 'graaasp_development' database, which is located in '/Library/WebServer/Documents/graaasp'.
Now we have to rewrite the classes that will respond to opensocial code with data from 'graaasp_development' database.
1) in the file config.php we should change the database settings as follows:
2) In file PartuzaDbFetcher.php we have the code that gets friends from 'graaasp_development' database.
The output of the widget will be similar to the following:
Friends of User1:
* Guest
* User2
* User3
I will use the gadget that lists friends of the user. Notice that http://shindig/ is where you have your shindig installation (http://localhost:8080, for example). Here is the gadget code:
Now we want Apache Shindig to get a list of friends for a user with id=2 from my database 'graaasp_development'.
Here is a url that does it.
The most important parameter here is a "st" parameter, that stands for security token.
Owner_id means id of the owner of the gadget. Viewer_id means id the current user watching the gadget.
Application_id means the id of the gadget instance in the database.
In other words, in 'graaasp_development' database we have a gadget with id=12. Owner of this gadget is user with id=2 and the same user watches the gadget at the moment.
Now we have to add some code to shindig to let it know that 'graaasp_development' database should be used as a backend for gadgets requests.
First of all in the folder "shindig/php/config/" we should create a file 'local.php' with the following content.
This will force Shindig to use the code specific to the 'graaasp_development' database, which is located in '/Library/WebServer/Documents/graaasp'.
Now we have to rewrite the classes that will respond to opensocial code with data from 'graaasp_development' database.
1) in the file config.php we should change the database settings as follows:
2) In file PartuzaDbFetcher.php we have the code that gets friends from 'graaasp_development' database.
The output of the widget will be similar to the following:
Friends of User1:
* Guest
* User2
* User3
Monday 1 March 2010
Reminder: svn ignore
A reminder on how to work with svn ignore.
In every folder svn keeps a list of all files/folders to ignore. By using the command "svn propset svn:ignore" you change this list. From my experience the best way is to have a text file "ignore.txt" (where you keep the list of all ignore rules) for every folder. The command "svn propdel svn:ignore ." will remove all rules for this folder and "svn propset svn:ignore -F ignore.txt ." will apply all the rules from the file "ignore.txt" for this folder.
The scenario: you are in a folder "MyFolder" and you want to ignore in this folder all svg files, the whole folder "log" and the whole folder "tmp". Then, you want to remove all ignore rules for this folder.
To add svn:ignore property for folder "MyFolder"
1) Make sure a file/folder to be ignored is not committed to svn repository.
If it is there, remove it from svn repository
2) Create a file "ignore.txt" in the "MyFolder" with the following content:
3) Go to the folder "MyFolder"
4) Run the following command to apply the rules
5) Commit the changes
To remove svn:ignore property for the folder "MyFolder".
1) Go to "MyFolder"
2) Run the following command to remove all the ignore rules.
2) Commit the changes
To do it recursively for all subfolders add "-R" to the command.
In every folder svn keeps a list of all files/folders to ignore. By using the command "svn propset svn:ignore" you change this list. From my experience the best way is to have a text file "ignore.txt" (where you keep the list of all ignore rules) for every folder. The command "svn propdel svn:ignore ." will remove all rules for this folder and "svn propset svn:ignore -F ignore.txt ." will apply all the rules from the file "ignore.txt" for this folder.
The scenario: you are in a folder "MyFolder" and you want to ignore in this folder all svg files, the whole folder "log" and the whole folder "tmp". Then, you want to remove all ignore rules for this folder.
To add svn:ignore property for folder "MyFolder"
1) Make sure a file/folder to be ignored is not committed to svn repository.
If it is there, remove it from svn repository
2) Create a file "ignore.txt" in the "MyFolder" with the following content:
3) Go to the folder "MyFolder"
4) Run the following command to apply the rules
5) Commit the changes
To remove svn:ignore property for the folder "MyFolder".
1) Go to "MyFolder"
2) Run the following command to remove all the ignore rules.
2) Commit the changes
To do it recursively for all subfolders add "-R" to the command.
Monday 15 February 2010
Apache Shindig: Java vs. PHP
I've spent a lot of time trying to understand what Shindig does and how it works. Well, I am close to it now, I believe. Another point that I was concerned about is Java or PHP? Shindig is known to be available as both java and php code. I need to use shindig to redirect the OpenSocial API calls inside gadget to my database. For this I need to write some interface methods. So which Shindig to choose: php or java?
Since I am more confident with php rather than java, I've chosen to look into php version. Partuza project that provides an example of social application based on PHP version of Shindig turned out to be very helpful.
At first I ran into some problems with php shindig, but it seems as I found the answers and those are not really problems.
Problem 1:
First of all the common todo gadget in php version of Shindig has a layout completely different from that of java version, which seems to be strange. Well it's not. Why it is different is explained here by Chris Chabot.
Problem 2:
Gadget default user preferences are not shown in shindig (php version),
but shown in java version.
It seems as it is the container implementations issue.
If those values are passed over url parameters it works:
http://shindig/gadgets/ifr?url=http://your_hosting/gadget.xml&up_myname=Evgeny
Gadget example is taked from Google:
http://code.google.com/apis/gadgets/docs/basic.html
Problem 3:
Gadget Friends gadget doesn't work in SimpleContainer.
It seems that those examples are not supported in PHP Shindig (found it on shindig emails list)
This gadget seems to work ok with partuza!!
Problem 3 was the biggest issue for me.
It seems it works properly in Partuza. Thus I will try to
implement interface methods to allow this gadget to request people from my database. If it works for Friends widget I will most probably stay with PHP if not, I guess I'll have to switch to Java version.
Since I am more confident with php rather than java, I've chosen to look into php version. Partuza project that provides an example of social application based on PHP version of Shindig turned out to be very helpful.
At first I ran into some problems with php shindig, but it seems as I found the answers and those are not really problems.
Problem 1:
First of all the common todo gadget in php version of Shindig has a layout completely different from that of java version, which seems to be strange. Well it's not. Why it is different is explained here by Chris Chabot.
Problem 2:
Gadget default user preferences are not shown in shindig (php version),
but shown in java version.
It seems as it is the container implementations issue.
If those values are passed over url parameters it works:
http://shindig/gadgets/ifr?url=http://your_hosting/gadget.xml&up_myname=Evgeny
Gadget example is taked from Google:
http://code.google.com/apis/gadgets/docs/basic.html
Problem 3:
Gadget Friends gadget doesn't work in SimpleContainer.
It seems that those examples are not supported in PHP Shindig (found it on shindig emails list)
This gadget seems to work ok with partuza!!
Problem 3 was the biggest issue for me.
It seems it works properly in Partuza. Thus I will try to
implement interface methods to allow this gadget to request people from my database. If it works for Friends widget I will most probably stay with PHP if not, I guess I'll have to switch to Java version.
Subscribe to:
Posts (Atom)