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 Istanbul,Turkey to work for a national bank.

Please feel free to use the Contact section if you want to contact with one of us.

The main features of this component is that it supports multiple location adding / updating / deleting. This means clients can indicate more than one location and adjust the size of those areas whatever and whenever they want.

I plan to write a how to for handling polygons on Google Maps asap.

There are two known libraries to use to be able to handle multipart form data; Apache Commons’ FileUpload and OReilly’s COS. I have found latter easy to use. At COS, there are two approaches to handle multipart request; push and pull model. You can either use MultipartRequest class  to handle the request (push model) just like you do at a regular request (i.e. using req.getParameter()); or use MultipartParser class to do the job by iterating among request objects (pull model).

You can download the .war file which contains source codes and classes mentioned below at here.

For today’s example, I will use MultipartRequest class to do the uploading, since it has the same logic as HttpServletRequest class. But first we need to include COS’s jar to our war project. You can do it easily at Netbeans by right-clicking at Libraries at Projects view under your project and hitting Add JAR/Folder…. That’s it, you’re ready to go now.

If you want to be able to see javadocs of COS, you should hit Add Library… and Create… a new Class Library, then you can give the path of COS’s jar, javadoc and source. A little bit trickier than adding just a jar, but really worth it.

To be able to upload a file, we need to have a JSP to render the upload form, and a Servlet to handle incoming requests. Lets first start with our servlet. At this servlet, Upload, we’re receiving incoming request at processRequest(req,res) method. At this method, incoming HttpServletRequest is cast to MultipartRequest. If casting can be done, it means form is submitted (i.e an actual multipart request has arrived) and we’re ready to handle our uploaded file. If casting throws an IOException, it means our form is not yet submitted (i.e user just tries to see upload form) and we should show upload form to the user.

protected void processRequest(HttpServletRequest request, HttpServletResponse response)
        throws ServletException, IOException {
    response.setContentType("text/html;charset=UTF-8");
    try {
        /**
         * Parse request using MultiparRequest since it is a multipart/form-data
         * throws IOException if request is not multipart
         *
         * So, if form is not yet submitted Upload servlet will show upload.jsp as response
         * if form is submitted Upload servlet will process the request at upload() function
         */
        MultipartRequest multipartRequest = new MultipartRequest(request, getServletContext().getRealPath("/tmp/"), /* 1MB */ 1024 * 1024, new DefaultFileRenamePolicy());
        if (multipartRequest.getParameter("save") != null) {
            upload(request, response, multipartRequest);
        } else {
            throw new IOException("Display Upload Dialogue");
        }
    } catch (IOException ex) {
        displayUpload(request, response);
    }
}

Showing the upload form is trivial, we’re just forwarding the Servlet’s response to upload.jsp file. The form element at upload.jsp is a minimal file upload form (i.e. you should always include method and enctype attributes as it is, and have at least one file typed input).

private void displayUpload(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
    /**
     * Display upload.jsp as response.
     * It is a good convention to use JSPs as Views (i.e. to show response)
     * and Servlets as Controllers (i.e. to catch request and process)
     */
    getServletContext().getRequestDispatcher("/WEB-INF/jspf/upload.jsp").forward(request, response);
}

<form action="Upload" enctype="multipart/form-data" method="post">
<input name="uploaded" type="file" />
<input name="save" type="submit" value="Upload" />
</form>

Now all we have to do is to handle incoming uploaded file. MultipartRequest, when first initialized, stores every uploaded file to a temporary location that you gave (In our case it’s under tmp/ folder). Than you can manipulate those temporary files by any way you want. In this example we’re just moving the uploaded file from tmp/ folder to data/ folder, and changing it’s name to uploaded while keeping the original file format.

private void upload(HttpServletRequest request, HttpServletResponse response, MultipartRequest multipartRequest) throws IOException {
 
    /**
     * Get uploaded file
     */
    File tmpFile = multipartRequest.getFile("uploaded");
 
    /**
     * Do whatever adjustment you want to this temporary file
     * .
     * .
     * .
     */
 
    /**
     *  Move temporary file to actual destination
     */
    File dirToMove=new File(getServletContext().getRealPath("/data"));
    String newFileName= "uploaded"+tmpFile.getName().substring(tmpFile.getName().lastIndexOf('.'));
    File fileToMove=new File(dirToMove,newFileName);
    tmpFile.renameTo(fileToMove);
 
    /**
     * Delete temporary file
     */
    tmpFile.delete();
 
    /**
     * Display newly uploaded file
     */
    response.sendRedirect("data/"+newFileName);
}

I think I have covered some basics of file uploading. If you need more information (especially about pulling method which I didn’t cover at all), I recommend you to look at O’Reily’s COS’s javadocs at here.

Have a good day.

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.

One of these features was Tag Cloud. Before this week, our tags had no importance values so they are all treated equally. But now, thanks to database modifications, I have implemented a Tag Cloud logic for tags. I used jquery tagcloud to represent the information.

Also, our sign-up system had still some issues that are needed to be fixed. And I decided that it will be easier to re-implement it than try to bug-fix, since we have some flow control modifications as well. So, I have implemented sign-up again. Hopefully next week, I will finish EditProfile, EditNetworkAccounts and EditVenue features.

You can get the plugin and its documentation by following:
http://www.fyneworks.com/jquery/star-rating

Moreover we, as all of the group members, did a meeting and we have adjusted database that can handle our new plans. And also we have decided into detailed suggestion system. Next week I am going to work on the suggestion algorithm

So this week I have worked on this issue. After fixing a tiny css bug, I have finalized the representation aspects of search results for Users, Venues and Events. I believe it is much more informative now.

Also I have finished Venue Profile View. What I did was basically to provide insiders information which was missing, to add a view which shows a map of the current venue and to provide links to ’see event’, ‘read comment’ views.

I think that we now have a solid, well integrated application; the only missing part of the project is edit views (user profile, venue etc.) and friendship,networking issues.