It’s a bit late to tell this but at June’09 we have finished the development of MuzikMekan and won the 3rd prize at Middle East Technical University, Computer Engineering Department, Senior Design Projects Contest.
Today all members of Praeda&Co. has gone in separate directions, Eray and Murat at Europe for Msc. study, Cansin is still at Ankara,Turkey for Msc. study and Gokhan is at Ankara,Turkey to work for TCMB.
Last week, as a whole team we focused on the last updates on database and determined the friendship and the suggestion system functions.
Then each member tried on to patch the failures because of the changes. I focused on the comment part. Next week, I am going to try to implement turkcell support for our project.
Signup part is completed except for security checks. Now signup consists of two parts.In first part, tags insertions are enabled and in second part, user’s other network accounts are added to database.
Venue Selection part is completed in low-level code. After getting the necessary information from google map, user’s status will be updated on the database and if exist, twitter account will be updated. Moreover, if venue does not exist on the database, user are able to add it to the database(Google map integration is not fully completed).After selecting or adding venue, user will be directed to comment page.In which, users are able to comment about the venue.However, comment venue page is just implemented with database insertion.
While I am searching for the usage of named query with JPA controller, I found this tutorial. It clearly shows the usage of entity manager with named query or sql queries. Also other tutorials may also be very useful and it worths to take a look at
Together with our team partner, the base of login and signup functionalities are completed and their internalization integrations work correctly. Error checks do exist and shown and they are also internalizated.
However, controlling the authentication system and in case of the failures, opening new ticket will be very beneficial for the security and maintenance considerations.
“authentication” verifies who you are and “authorization” verifies what you are authorized to do.
What types of authentication systems exist? We can roughly say there are two types. Basic and form based model. Form-based systems get rid of the implementation of authentication system by themselves. At first glance, this type may seem difficult to maintain however it shows its benefits very soon. A kind of implementation is available at:
Filtering the user input is another important topic in authentication system. If we want every operation that is performed by current user to be authenticated, we may ensure that every action that is performed by user to be passed from filter. It is surely more efficient way than checking the status of user in each page. An example of authentication filter:
I uploaded some sample files to SVN repository as they may be necessary to reach from SVN and to make them independent from my PC.
In a simple login page, mainly we should create and configure three parts. First “login.jsp” for visual design and calling validating function. Second “login Bean”( Simple Java Class) for getting information from jsp page and creating this bean instance and also this java file includes the validation function. Third, “faces-config.xml” file for managing bean and redirecting the client according to the result of the validate function.
Then how should we check the logged-in status of the clients? One way is the check the attribute of a session object. Another way, which is proper to JSF, is to use “PhaseListener”.
How about session objects? Session Objects live on the server and are automatically associated with clients. Session objects are not travelled along networks only unique identifiers are used. “request.getSession” is enough to get the session object, we do not need to use our own cookies and hash tables, url-rewriting or hidden form fields.
The Praeda & Co. did a progress evaluation meeting in order to specify roadmap of the Prototype Demo. The division of labor is as follow:
- Eray takes the GUI development responsibility on Android. He will prepare pages with links to each other.
- Gokhan will setup the Database according to our diagrams and he will develop Database connection classes.
- Cansın will make a field research. He will try to embed the Webkit in Android with a native appearance. If he can achieve this task we will develop our GUI for Android with web technologies instead of a native GUI.
- Murat will make a deep investigation about Google Maps and he is also responsible for GPS functionalities.
Moreover, the team decided on using the Blog in a more efficient way. Everyone will try to prepare Tutorials and other type of documents about the work done.
The next meeting will be held on Jan 12 at 21.00.
I made configuration of apache-tomcat 6.0 on eclipse 3.4(ganymede) in Windows platform and server is running succesfully.
I worked over sample application using JSP and Servlet. I managed to build some sample applications succesfully on my server. I think using JSP together with Servlet will be more beneficial for the understandability and developability of the project.
Slightly I looked over the usage of JavaBean in JSP. Next week, mainly I will focus on the MVC architecture, JDBC connection of a simple application and How we can use JSF in the project.