The IdleWorx Blog

Welcome to the IdleWorx blog

noreply@blogger.com (IdleWorx) — Sat, 22 Dec 2012 00:56:00 +0000

This is the official blog of idleworx.com. A blog covering Android, JSP, Servlets, Tomcat, JavaScript, Ruby and other web development stuff.

The Do Not Track movement is useless

noreply@blogger.com (IdleWorx) — Mon, 06 Feb 2012 00:50:00 +0000

... or why privacy is your own responsibility

The Do Not Track movement (donottrack.us) is, according to their website

"a technology and policy proposal that enables users to opt out of tracking by websites they do not visit"

and from a recent article in USA Today, How Facebook tracks you across the web we find out the following

"Facebook's efforts to track the browsing habits of visitors to its site have made the company a player in the "Do Not Track" debate, which focuses on whether consumers should be able to prevent websites from tracking the consumers' online activity."

Companies like Facebook, Google, etc have a vested interest in finding out as much information about EVERYTHING you do. That's how they make money. So any movement that proposes these companies self-regulate and take more care of our privacy needs is simply useless.

Even if regulation was passed forcing these companies to allow users to opt out of tracking, that doesn't mean it wouldn't still occur.

The donottrack.us website also mentions that

"Several large third parties have already committed to honor Do Not Track ... "

So what? Does that mean anything really?

What do you know about what they do with this information even if they "committed" to work against their own self and business interests by not tracking you?

I'll tell you. Absolutely nothing!

Do you have a signed contract with them that says they can never track you? Is there an actual law that prevents them from tracking you? No? Then stop daydreaming.

When it comes to personal privacy and security, you can't outsource it (especially to those who have an interest in your lack of privacy). There's no easy way.

So if you care about your privacy, educate yourself and protect yourself.

Goodbye Delicious, Hello Pinboard

noreply@blogger.com (IdleWorx) — Thu, 02 Feb 2012 06:22:00 +0000

Goodbye Delicious

There are two types of people in the world, those who rarely save bookmarks, and those who have thousands. If you're like me, you probably have thousands or at least a few hundred. For me it's more exactly 4466 bookmarks at last count. (If you're not like me, a bookmark hoarder, then you probably want to skip this article.)

Over the past 10-15 years I've collected tons of bookmarks because I like to keep track of cool, useful and interesting things I find online so if I ever want to go back to them I can.

I've spent countless hours over the years keeping things clean, ordered and organized so I can actually make use of this information. As you can imagine if you don't keep this many bookmarks organized and neat there's absolutely no point in saving them in the first place, since you won't be able to find anything if you so choose at a later time.

Bookmarks, when used correctly are nothing more than a self maintained cache of the things you've found most interesting or useful. Thus they are a treasure trove of data for various services such as delicious or various others which have capitalized on this.

Delicious was founded in 2003, and was essentially the company that introduced social bookmarking and tagging to the masses. That said and done I didn't really get on board with them until a few years ago when I outgrew my bookmarking needs. Trying to manage several thousand bookmarks across multiple browsers and multiple computers does that to you.

But delicious has not delivered and has recently started to fall short, in part due to Yahoo firing the delicious team, and its subsequent purchase by Youtube founders.

Here's just a few problems I found:

Slow syncing of bookmarks in browser
Having to sometimes log in every day
Firefox addons would stop working after upgrading to certain version of Firefox
The pain and waste of time trying to find a way to mark all my bookmarks private when bookmarking through a browser plugin. Why, delicious? Why?
Inconsistent tag naming - You could use spaces in an older versions of the Firefox plugin, but only commas in newer versions. Because it wasn't made clear, myself and I'm sure plenty of others, had had to go through tons of delicious bookmarks and convert tags like "programming jsp reference useful" into the 4 separate tags they should have been in the first place. Not cool)

And there were other unhappy campers.

Hello Pinboard

As delicious was going down, I learned of other social bookmarking sites, pinboard.in being one that caught my attention.

Throughout the years, I had migrated over from IE Favorites to Firefox Bookmarks to delicious bookmarks. I had hand curated my bookmarks and cleaned them up with link checkers to remove expired ones. It was time to move on to something better.

So last night, I finally made the switch and created an account on pinboard.in. It's not free mind you (there is a one time fee of about $9), but from everything I read it's worth it Not to mention the guy behind it seems like a great chap and has his stuff together.

And from the first looks, I love it.

Importing almost 4500 bookmarks from both firefox and delicious was painless. Took a few minutes.
Interface is great, simple, minimal and quick, exactly what I wanted
Great default privacy settings give you the ability to 'add bookmarks as private by default'
'enable public profile' is OFF by default
and more

I did notice there was no easy way to rename a tag in pinboard (there is a way though), but I'm planning to play around with the Pinboard API soon and see what I can cook up.

I'm sure pinboard is not perfect, but hey, it is the best I've found so far for my bookmarking needs.

A simple birthday reminder app

noreply@blogger.com (IdleWorx) — Wed, 18 Jan 2012 03:31:00 +0000

Are you looking for an easy breazy birthday reminder app to keep track of all your friends' birthdays that you seem to forget every year? Well, look no further.

The time has come for you to get your self organized and never forget another birthday again. Check out http://beta.birthdayduck.com a simple, clean and useful birthday reminder service from IdleWorx

Here's a screenshot

It has the essential features you need in a birthday reminder application:

Reminders by email
Reminders by SMS/text message
A simple way to add names ands birthdays
Import contacts from Facebook

No bells and whistles. birthdayduck.com aims to help you organize your life, by making it very easy to remember people's birthdays.

It works like a birthday reminder calendar, except you won't need to worry about it all the time. The application will send you reminders by email and sms before someone's birthday.

We're currently in beta, and getting ready to launch soon.

If you sign up now at http://beta.birthdayduck.com and you are one of the first 50 sign-ups you'll receive a free lifetime account on birthdayduck.com once we launch.

How algorithms shape our world (video)

noreply@blogger.com (IdleWorx) — Thu, 29 Dec 2011 00:35:00 +0000

Kevin Slavin argues that we're living in a world designed for -- and increasingly controlled by -- algorithms. In this riveting talk from TEDGlobal, he shows how these complex computer programs determine: espionage tactics, stock prices, movie scripts, and architecture.

Your time is not worth that much

noreply@blogger.com (IdleWorx) — Wed, 21 Dec 2011 02:05:00 +0000

I noticed a lot of people in the startup/programming/HN community seem to measure their time in the equivalent of how much money they could be making during that time.

For example, you ask a friend to do something for you that takes 2 hours, and they tell you that in those 2 hours they could be making 300$ because that's their hourly rate if they were doing freelance work. So essentially if they aren't paid for these 2 hours they are basically loosing 300$.

I say this way of estimating how much your time is worth is flawed.

The only time this estimate is true is when you have a guy waiting at your door 24/7 for you to open it and give you work, and let you charge him 150$/hr for that work (per the example above).

Given any other time, your time estimate is probably way off. Because if you don't have work available NOW at the rate you're estimating yourself to be worth, your time is just not worth as much as you think it is. In fact, if you don't have any work lined up for that rate, your time is worth almost nothing. It's free time.

Could you be making money during your free time? Yes, however if you are not ready at that very moment to take on the work at your going rate, your lost opportunity cost is not 150$/hr, but 0$.

The other problem with correctly estimating what your time is worth is how easy it is easy to overestimate. I mean hey, in this next hour that I don't do anything I could be making a million dollars by winning the lottery. So my hourly rate is a million dollars. Just like the example above, that rate IS possible, but highly unprobable not to mention ridiculously unsustainable.

To dig in further, the wiki informs us that:

"The notion of opportunity cost plays a crucial part in ensuring that scarce resources are used efficiently"

And that's a good thing. If you're wasting your time on the couch picking your nose, you could be doing much better things with your time (Eg. creating something useful for others and getting paid for it too)

Some people however have the tendency to put a dolar value on EVERYTHING in their lives. And sadly it's a rather limited world view when everything has a dollar value and an opportunity cost.

News Flash: Not everything in life has a dollar value

The wiki has a fairly straight forward example of this

"Opportunity costs are not always measured in monetary units or being able to produce one good over another. For instance, an individual could choose not to mow his or her lawn, in an attempt to create a prairie land for additional wild life. Neighbors of this individual may see this as unsightly, and want the lawn to be mowed. In this case, the opportunity cost of additional wild life is unhappy neighbors."

We are not robots and life is not a well written ruby script (as some would like to believe).

You can always look at everything in terms of the lost opportunity cost (and the dollar value associated with it), however, often the lost opportunity cost in dollars is far less valuable as an indicator of how much your time is really worth, and in some cases it can't even be used to accurately describe the lost opportunity cost, such as the opportunity cost of non-tangible things.

For example, spending 2 hours playing with your kids or volunteering and genuinely helping out another human being, is INFINITELY more important, beneficial and fulfilling than your lost opportunity cost of 300$ that you could be making doing freelance work.

So to sum it up, while it's good to have a perspective about how much your time is worth, don't over do it.

There are obvious cases when estimating your time makes perfect sense, but breaking down your entire waking time into lost opportunity costs is a bit too much in my opinion.

Just like with most things in life, aim for moderation.

Agile Hitler is not Happy

noreply@blogger.com (IdleWorx) — Sat, 01 Oct 2011 16:16:00 +0000

MyBatis DAO Example Code Tutorial

noreply@blogger.com (IdleWorx) — Sat, 24 Sep 2011 01:01:00 +0000

This tutorial will show how how to integrate MyBatis with the Data Access Object pattern (DAO) and MySQL for use in Java Web Apps.

In case you're not familiar, MyBatis is the new version of the iBatis Data Mapper Java Framework, which allows you to use a relational database with object-oriented applications.

If you're not familiar with the DAO pattern or the benefits of using it read more about it here Generic implementation of the DAO pattern.

Full code of this mybatis dao example tutorial is available on github here.

Step 1 - Define the interface

Create an IParentDAO interface to define the main method calls for all objects. This interface can be used as the parent for various DAO implementations. Here are the default CRUD methods that all objects will have

get(id)
getByName(name)
getAll()
create(obj)
update(object)
delete(id)

Create the IParentDAO.java class


public interface IParentDAO<T, PK>{
 public T get(PK id) throws PersistenceException;//get obj of type T by the primary key 'id' 
 public T getByName(String name) throws PersistenceException;//get obj of type T by the 'name' field, if one exists for that table
 public ArrayList<T> getAll() throws PersistenceException;//get all objects of type T
 public int create(T objInstance) throws PersistenceException;//insert an object of type T into the database
 int update(T transientObject) throws PersistenceException; //update an object of type T    
 int delete(PK id)  throws PersistenceException;//delete an object of type T
}

Step 2 - Create the base class

Create the MyBatisDAO abstract base class. This will be the default MyBatis implementation of the DAO. You can of course write a different one for JDBC, Spring etc. Feel free to remove the logging code if you don't need it. I used Logback for that.


import java.util.ArrayList;

import org.apache.ibatis.exceptions.PersistenceException;
import org.apache.ibatis.session.SqlSession;
import org.apache.ibatis.session.SqlSessionFactory;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

/** 
 *  Class contains all the basic CRUD related methods which are inherited by all objects
 *  Children daos should generally not overwrite these method but add extra ones as needed.  
 */
public abstract class MyBatisDAO<T, PK> implements IParentDAO<T, PK>{
 
 private static Logger log = LoggerFactory.getLogger(MyBatisDAO.class);
 private static final String NAMESPACE = "mappers"; 
 
 private SqlSessionFactory sf; //reference to mybatis session factory 
 private Class<T> type;
  
 /** 
  * Define prefixes for easier naming convetions between XML mapper files and the DAO class 
  **/ 
 public static final String PREFIX_SELECT_QUERY = "get";     //prefix of select queries in mapper files (eg. getAddressType) 
 public static final String PREFIX_INSERT_QUERY = "create"; //prefix of create queries in mapper files (eg. createAddressType)
 public static final String PREFIX_UPDATE_QUERY = "update";  //prefix of update queries in mapper files (eg. updateAddressType)
 public static final String PREFIX_DELETE_QUERY = "delete";  //prefix of delete queries in mapper files (eg. deleteAddressType)
 
 /** Default Constructor */
    public MyBatisDAO(Class<T> type,SqlSessionFactory sf) {
        this.type = type;
        this.sf = sf;
        if(sf==null)
   log.error("Error: Could not instantiate MyBatisDAO. Loading myBatis sessionFactory failed.");  
    }
    
    /** Use this method to get a session factory for using in any methods impelmented in child dao classes */
    protected SqlSessionFactory getSessionFactory() {
  return sf;
 }

    /** 
     *  Default get by id method. 
     *  </br></br> 
     *  Almost all objects in the db will 
     *  need this (except mapping tables for multiple joins, which you 
     *  probably shouldn't even have as objects in your model, since proper 
     *  MyBatis mappings can take care of that).
     *  </br></br>
     *  Example: 
     *  </br>
     *  If your DAO object is called CarInfo.java, 
     *  the corresponding mapper query id should be: &lt;select id="getCarInfo" ...  
     */
    public T get(PK id) throws PersistenceException {
        
     SqlSession session = sf.openSession(); 
     T obj = null;
  try
  {  
   String query = NAMESPACE+"."+PREFIX_SELECT_QUERY+this.type.getSimpleName();  //If the object's calls name is AddressType.java, this matches the mapper query id: "namespace.getAddressType"
   obj = (T)session.selectOne(query,id);      
  }
  finally
  {
   session.close();
  }
  return obj;
    }
    
    /** 
     *  Method returns all rows for this object.
     *  </br></br>  
     *  Example:
     *  </br>  
     *  If your DAO object is called CarInfo.java, 
     *  the corresponding mapper query id should be: &lt;select id="getAllCarInfo" ...  
     *  </br></br>  
     *  SQL Executed: select * from [tablename]
     *  </br></br>  
     *  Notes:
     *  </br>   
     *  Consider overdiding this method in order to handle large numbers of objects 
     *  with multiple references.  
     *  LAZY LOADING should be enabled in this case, otherwise you might run out of memory (eg. get all UserAccounts if the table has 1,000,000 rows)
     *  look into the aggresiveLazyLoading property 
     *  */
    public ArrayList<T> getAll() throws PersistenceException {
        
     SqlSession session = sf.openSession(); 
     ArrayList<T> list = null;
  try
  {     
   String query = NAMESPACE+"."+PREFIX_SELECT_QUERY+"All"+this.type.getSimpleName();
   list = (ArrayList<T>)session.selectList(query); 
  }
  finally
  {
   session.close();
  }   
  return list;
    }
    
    /** 
     *  Method returns first object which matches the given name (exact match).
     *  </br></br>  
     *  It's up to you to decide what constitutes an object's name. Typically you would have a 
     *  NAME column in the table, but not all objects have this. Generally this method should be overriden (if you need it at all)
     *  in the child dao class.
     *  </br></br>
     *  Example:
     *  </br>  
     *  If your DAO object is called CarInfo.java, 
     *  the corresponding mapper query id should be: &lt;select id="getCarInfoByName" ...  
     *  </br></br>  
     *  SQL Executed (example): select * from [tablename] where NAME = ? 
     *  
     */
    public T getByName(String name) throws PersistenceException {
        
     SqlSession session = sf.openSession();
     T obj = null;
  try
  { 
   String query = NAMESPACE+"."+PREFIX_SELECT_QUERY+this.type.getSimpleName()+"ByName";
   obj = (T)session.selectOne(query,name);   
  }
  finally
  {
   session.close();
  }
  return obj;
    }
    
    
    /** 
     *  Method inserts the object into the table.
     *  </br></br>
     *  You will usually override this method, especially if you're inserting associated objects.
     *  </br> 
     *  Example:
     *  </br>  
     *  If your DAO object is called CarInfo.java, 
     *  the corresponding mapper query id should be: &lt;insert id="createCarInfo" ...  
     *  </br></br>  
     *  SQL Executed (example): insert into [tablename] (fieldname1,fieldname2,...) values(value1,value2...) ... 
     *  
     */
    public int create(T o) throws PersistenceException{        
     SqlSession session = sf.openSession();
     Integer status = null;
     try
  {   
      String query = NAMESPACE+"."+PREFIX_INSERT_QUERY+o.getClass().getSimpleName();
   status = (Integer)session.insert(query,o);
   session.commit();   
  }
  finally
  {
   session.close();
  }  
  return status;
    }
    
    
    /** 
     *  Method updates the object by id.
     *  </br></br>
     *  You will usually override this method. But it can be used for simple objects.
     *  </br> 
     *  Example:
     *  </br>  
     *  If your DAO object is called CarInfo.java, 
     *  the corresponding mapper query id should be: &lt;update id="updateCarInfo" ...  
     *  </br></br>  
     *  SQL Executed (example): update [tablename] set fieldname1 = value1 where id = #{id} 
     *  
     */
    public int update(T o)throws PersistenceException {
        
     SqlSession session = sf.openSession();
  Integer status = null;
     try
  {   
   String query = NAMESPACE+"."+PREFIX_UPDATE_QUERY+o.getClass().getSimpleName();
      status = session.update(query,o);
   session.commit();
   
  }
  finally
  {
   session.close();
  } 
  return status;
     
    }

    
    /** 
     *  Method deletes the object by id.
     *  </br></br>
     *  Example:
     *  </br>  
     *  If your DAO object is called CarInfo.java, 
     *  the corresponding mapper query id should be: &lt;delete id="deleteCarInfo" ...  
     *  </br></br>  
     *  SQL Executed (example): update [tablename] set fieldname1 = value1 where id = #{id} 
     *  
     */
    public int delete(PK id)  throws PersistenceException{
  SqlSession session = sf.openSession();
  Integer status = null;
  try
  {   
   String query = NAMESPACE+"."+PREFIX_DELETE_QUERY+this.type.getSimpleName();
   status = session.delete(query,id);
   session.commit();
  } 
  finally
  {
   session.close();
  } 
  return status;
  
    }
}

Naming Convetions

You'll notice there are four prefix constants defined in the class above.

The reason for this is to keep consistency between the sql query ids you will define in the mybatis mapper.xml files (see Step 4) and the method names defined in the MyBatisDAO class we're implementing.

This won't work exactly like ActiveRecord or similar frameworks where there is a pluralization engine but it will still simplify things a lot.

For example, if you have an object called Status for which you will create a DAO, you will have to define the following mybatis querries

Java Method	MyBatis Query Id	Convention
dao.get(1)	<select id="getStatus" ...	getClassName
dao.getAll()	<select id="getAllStatus" ...	getAllClassName
dao.getByName(String name)	<select id="getStatusByName" ...	getClassNameByName
dao.create(obj)	<insert id="createStatus" ...	createClassName
dao.update(obj)	<update id="updateStatus" ...	updateClassName
dao.delete(id)	<delete id="deleteStatus" ...	deleteClassName

Don't worry, this will make a lot more sense once you get to Step 4

Step 3 - Write the actual DAO classes

Now you need to implement your concrete DAO classes.

Let's say you have a simple object called Status which maps to a simple table, and has 2 attributes, an ID and a NAME. Think of it as an object you could use to represent the status of a task. I chose this to illustrate a very basic example here

The table for this object would look like this

ID	NAME
1	Done
2	In Progress
3	Not Started

And the java class (or DTO object) would look like this (Status.java)


public class Status 
{
 private int id;
 private String name;
 
 public int getId() {
  return id;
 }
 public void setId(int id) {
  this.id = id;
 }
 public String getName() {
  return name;
 }
 public void setName(String name) {
  this.name = name;
 }
 
 @Override
 public String toString() {  
  return "[Status] " + "(" + id + ") " + name;
 }
}

Writing the DAO class for the Status object now becomes trivial since you're inheriting all the default CRUD methods from MyBatisDAO.java defined above.

Here's how the StatusDAO.java should look:


import org.apache.ibatis.session.SqlSessionFactory;

import com.idleworx.mybatisdao.MyBatisDAO;
import com.idleworx.mybatisdao.tests.objects.Status;

public class StatusDAO extends MyBatisDAO<Status,Integer>{
 
 //Don't forget to define the default custom constructor when implementing a new 
 //child DAO class, and set the class type accordingly 
 public StatusDAO(Class<Status> type,SqlSessionFactory containerSessionFactory) {
  super(type,containerSessionFactory);
 }
 
}

You'll notice here that all you need to do is call the constructor from the parent MyBatisDAO.java class. Now all the default CRUD methods are available for the StatusDAO.java class.

You are free of course to add any additional methods as needed here that go beyond the CRUD methods that were defined. For example something like

getStatusForBlog(Integer blogId).

See the full code example.
Both the MyBatisDAO.java and IParentDAO.java classes are included.

Of course you will still have to define the MyBatis mapper SQL statements for the default CRUD methods defined in MyBatisDAO.java, as well as additional SQLs for other DAO methods you choose to implement. Which brings us to the next step ...

Step 4 - Defining the mybatis mapper

The last major step in the puzzle, is writing the actual SQL that will implement all the default CRUD methods and any other methods you've implemented for the Status object.

Your code may differ of course, but note the use of the naming conventions for naming the sql statements which I talked about earlier.

That is the key to this whole thing, and it will make your life a lot easier when writing other DAOs which extend the MyBatisDAO class.

Here is an example of how the mapper file for the StatusDAO object would look like.

StatusMapper.xml


<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE mapper PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN" "http://mybatis.org/dtd/mybatis-3-mapper.dtd">

<mapper namespace="mappers">
 
 <select id="getStatus" parameterType="int" resultType="Status">
  select 
   status_id as "id",
   status_name as "name"
  from daohelper.status where status_id = #{id}
 </select>
 
 <select id="getAllStatus" parameterType="int" resultType="Status">
  select 
   status_id as "id",
   status_name as "name"
  from daohelper.status order by status_id
 </select>
 
 <select id="getStatusByName" parameterType="int" resultType="Status">
  select 
   status_id as "id",
   status_name as "name"
  from daohelper.status where status_name = #{name}
 </select>
 
 <insert id="createStatus" keyColumn="status_id" useGeneratedKeys="true" parameterType="Status">
  insert into daohelper.status (status_name)
  values (#{name})  
 </insert>
 
 <update id="updateStatus" parameterType="Status">
  update daohelper.status set status_name = #{name} where status_id = #{id}  
 </update>
 
 <delete id="deleteStatus" parameterType="int">
  delete from daohelper.status where status_id = #{id}  
 </delete> 
 
</mapper>

Note here the use of the mapper namespace which is the same as referenced by the MyBatisDAO abstract class.

It's used for convenience in this case, and generally you should be able to use multiple mapper files with the same namespace as long as the you don't have multiple queries with the same id across several xml mapper files (which would be a bad idea anyway)

Errors

Just a side note on some errors you may encounter.

If you call one of the default CRUD methods but don't define the appropriate query in the mapper.xml file, you will get an error like this:

org.apache.ibatis.exceptions.PersistenceException: 
### Error querying database.  Cause: java.lang.IllegalArgumentException: Mapped Statements collection does not contain value for mappers.getAllFrog
### Cause: java.lang.IllegalArgumentException: Mapped Statements collection does not contain value for mappers.getAllFrog

Wrapping it up

By this point I hope you've managed to build yourself a small but working DAO implementation based on the MyBatisDAO abstract class.

You can download the full code example for more a better overview.

It also contains a jUnit example, the mybatis configuration file (mybatis.config.xml) as well as the simple DDL statments for setting up the MySQL table.

Note:If you need to use this from a Servlet or Spring controller, see my other blog post about defining a servletcontextlistener

Hope you found this useful. Improvements or suggestions are welcome.

Creating a simple android app with 2 buttons

noreply@blogger.com (IdleWorx) — Wed, 29 Jun 2011 00:59:00 +0000

How do I build a very simple android app you ask? It's easy, building a basic android application is not that hard. Making something really useful, cool and bug free, now that takes a good developer.

This is a brief tutorial will show you how to code a very basic two button android application (with a start button and a stop button).

You can use this code as an android project template or starting point for simple projects.

Two Button Application Use Case

A simple two button application, can be your starting point for various android projects. It can be useful for example when you have an application that starts and stops a service from the click of a button Watch for tutorial on this soon.

Note:This tutorial assumes you have completed the HelloWorld Tutorial in the Android docs and you are a little familiar with Eclipse and ADT. The tutorial is aimed at developers who are very new to Android.

Creating a two button app

1) Create the project

In Eclipse create a new Android project and define the properties as shown below. Feel free to use your own package names.

2) Create a simple layout

For our main activity we're going to define a very basic layout consisting of one TextView and two Buttons (a start button and a stop button).

Modify your project/res/layout/main.xml file to this:


<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:orientation="vertical"
    android:layout_width="fill_parent"
    android:layout_height="fill_parent"
    >
<TextView  
    android:layout_width="fill_parent" 
    android:layout_height="wrap_content" 
    android:text="This is a simple two button app. \r\n \r\n Tell your user what your app does here \r\n \r\n \r\n \r\n"
    android:padding="10dp"
    android:textColor="#FFFFFF"
    />
<Button
 android:id="@+id/buttonStart"
 android:layout_width="fill_parent"
 android:layout_height="wrap_content"
 android:text="Start"/>
<Button
 android:id="@+id/buttonStop"
 android:layout_width="fill_parent"
 android:layout_height="wrap_content"
 android:text="Stop"/>
</LinearLayout>

If you run your project in the emulator it should look like this

3) Adding onClickListeners to the buttons

In order for the buttons to actually do something useful, and to provide a template for where you can put future functionality, we'll need to define onClickListeners for each button.

Let's update the TwoButtonApp.java main activiy with the following code:


package com.idleworx.android.twobuttonapp;

import android.app.Activity;
import android.os.Bundle;
import android.util.Log;
import android.view.View;
import android.view.View.OnClickListener;
import android.widget.Button;
import android.widget.Toast;

public class TwoButtonApp extends Activity {
    
 private static String logtag = "TwoButtonApp";//for use as the tag when logging 
  
 /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.main);
        
        Button buttonStart = (Button)findViewById(R.id.buttonStart);        
     buttonStart.setOnClickListener(startListener); // Register the onClick listener with the implementation above
      
     Button buttonStop = (Button)findViewById(R.id.buttonStop);        
     buttonStop.setOnClickListener(stopListener); // Register the onClick listener with the implementation above
    }
    
    //Create an anonymous implementation of OnClickListener
    private OnClickListener startListener = new OnClickListener() {
        public void onClick(View v) {
          Log.d(logtag,"onClick() called - start button");              
          Toast.makeText(TwoButtonApp.this, "The Start button was clicked.", Toast.LENGTH_LONG).show();
          Log.d(logtag,"onClick() ended - start button");
        }
    };
    
    // Create an anonymous implementation of OnClickListener
    private OnClickListener stopListener = new OnClickListener() {
        public void onClick(View v) {
         Log.d(logtag,"onClick() called - stop button"); 
         Toast.makeText(TwoButtonApp.this, "The Stop button was clicked.", Toast.LENGTH_LONG).show();
          Log.d(logtag,"onClick() ended - stop button");
        } 
    };
    
    
    @Override
 protected void onStart() {//activity is started and visible to the user
  Log.d(logtag,"onStart() called");
  super.onStart();  
 }
 @Override
 protected void onResume() {//activity was resumed and is visible again
  Log.d(logtag,"onResume() called");
  super.onResume();
  
 }
 @Override
 protected void onPause() { //device goes to sleep or another activity appears
  Log.d(logtag,"onPause() called");//another activity is currently running (or user has pressed Home)
  super.onPause();
  
 }
 @Override
 protected void onStop() { //the activity is not visible anymore
  Log.d(logtag,"onStop() called");
  super.onStop();
  
 }
 @Override
 protected void onDestroy() {//android has killed this activity
   Log.d(logtag,"onDestroy() called");
   super.onDestroy();
 }
}

Notes

As you can see, each button (or any resource for that matter) can be retrieved by the id was associated with in the layout:
```
@+id/buttonStart 

can be retreived with:

Button buttonStart = (Button)findViewById(R.id.buttonStart);  
```
We have attached two anonymous OnClickListeners() to each of our two buttons
Each listener displays a simple Toast (a brief message to the user).
Logging is very important especially during debugging, so make sure you use it where ever you need
Not the logtag variable defined in the very top. It's a quick shortcut to save time when logging statements in your app with the Log.X methods. I usually use the same name as the class name and use the Create Filter option in the LogCat view to filter my code out.
For easier debugging I've added logging of all the other lifecycle methods in the Activity. When you do debugging of your apps it's very important to understand the lifecycle of an android app, and even more important to see how it's called in relation to your code.

So this is it, Introduction to Android 101. You should now have a very basic android app running.

For reference here is how your AndroidManifest.xml file should look (you should not have had to modify this file so far if you have followed this tutorial):


<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
      package="com.idleworx.android.twobuttonapp"
      android:versionCode="1"
      android:versionName="1.0">
    <uses-sdk android:minSdkVersion="8" />

    <application android:icon="@drawable/icon" android:label="@string/app_name">
        <activity android:name=".TwoButtonApp"
                  android:label="@string/app_name">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>

    </application>
</manifest>

First Android App Goes Live

noreply@blogger.com (IdleWorx) — Mon, 20 Jun 2011 02:55:00 +0000

I've taken an interest in Android App Development a few months ago, and tonight I decided to launch the first android app I created.

It's a very simple taxi finder app targeted for people in Bucharest, Romania.

If you ever find yourself in Bucharest, Romania and you need a taxi, and you happen to have an android phone, make sure to install this app. It may just be what you need. From the Android market you can search for "vreau taxi" or check out the link below:

VreauTaxi

The goal of this was to learn the whole process of android app development from top to bottom and I think it went rather well despite a few painful hours dealing with Windows 7 Android USB device installation issues.

I will write more about Android soon, as some new blog post ideas have been rolling through my head.

RubyNation 2011

noreply@blogger.com (IdleWorx) — Wed, 30 Mar 2011 20:33:00 +0000

Going to the RubyNation conference this weekend. Cool stuff.

The IdleWorx Monster MyBatis Tutorial

noreply@blogger.com (IdleWorx) — Fri, 04 Feb 2011 03:35:00 +0000

Building an entire Java web application with MyBatis 3, Tomcat, MySQL and Eclipse (on Windows 7)

This is a multi part tutorial which will show you how to build a Servlet/JSP based web application from scratch, using MySQL, Tomcat and MyBatis (the new version of the iBatis framework) on a windows platform using Eclipse.

You will make the most of this tutorial if

You have built at least a few small webapplications in the past.
You know how to setup Tomcat 5.x or higher version
You are somewhat familiar with the Eclipse IDE
You are familiar with SQL.
You know how to set-up MySQL on your development box and integrate it with your java web application.

Let's get started

To see how Tomcat, MyBatis and MySQL work together we're going to create a tiny java web application in Eclipse, called ModelingAgency.

If you don't want to follow the whole tutorial, you can skip through to the different sections below and pick out the information you need, otherwise continue to Part 1 - The Setup

At the end of this tutorial you will hopefully be able to create a basic Java JSP/Servlet based webapp with MyBatis, MySQL and Tomcat in an Eclipse environment.

You can download a full version of finished ModelingAgency webapp here.

This tutorial took me a long time to write, so if you found it useful in any way, if you found errors with it or you think something is missing, please let me know and I will do my best to improve it.

Part 11: Finalizing the Interface

noreply@blogger.com (IdleWorx) — Fri, 04 Feb 2011 00:32:00 +0000

If you have followed this tutorial so far, you will probably remember that in Part 2 I had shown you how the GUI will look when we're done. Here it is again:

We have put together everything except our interface, so it's time to modify our index.jsp to finalize the interface. Here's how your index.jsp file should look right now:

<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
 <title>Modeling Agency Index</title>
</head>
<body>

<h1>The IdleWorx Modeling Agency</h1>
<hr>

<div style="width:300px;float:left;">
 
 <h2>Available Clients</h2>
 <c:forEach items="${all_clients}" var="client">
  <a href="client.do?id=${client.id}">${client.name}</a><br>
 </c:forEach> 
</div>

<div style="width:300px;float:left;">
 <h2>Available Models</h2>
 <c:forEach items="${all_models}" var="model">
  <a href="model.do?id=${model.id}">${model.name}</a><br>
 </c:forEach> 
</div>

<div style="clear:both;">
 <h2>Bookings</h2>
 <table border="1">
 <tr>
  <th>Client</th>
  <th>Model</th>
  <th>Time</th>
  <th>Place</th>
 </tr>
 <c:forEach items="${all_bookings}" var="booking">
 <tr>
  <td>${booking.client.name}</td>
  <td>${booking.model.name}</td>
  <td>${booking.time}</td>
  <td>${booking.location}</td>
  <td></td>
 </tr>
 </c:forEach> 
 </table>
</div>

</body>
</html>

Open up: http://localhost:8080/ModelingAgency/test.do. You should now have an interface very similar to the image above.

You'll notice I used the JSTL and EL libraries to nicely write our output (please don't use scriptlets in your JSP classes).

Also if you haven't noticed so far, in your ModelingAgency web application folder, you should have a file called sql.log wich has logged all of the SQL statements that MyBatis generated. You may find it useful when debugging your MyBatis apps

Congrats

If you got this far, I hope you now feel more comfortable about MyBatis,Tomcat and MySQL. You should now have all the basics to get a very simple app started in Eclipse using these technologies.

You can download a full version of the app here.

This tutorial took me a long time to write, so if you found it useful in any way, if you found errors with it or you think something is missing, please let me know and I will do my best to improve it.

Go back to the IdleWorx Monster MyBatis Tutorial

Part 10: Initializing MyBatis on Application Startup

noreply@blogger.com (IdleWorx) — Fri, 04 Feb 2011 00:30:00 +0000

If you've been following Part 9 of this tutorial, we now need to make sure our application has an sqlSessionVariable available ready to go when the TestServlet is invoked.

I had recently written a more detailed article about how to initialize MyBatis when a web application starts up. You can read that here.

For this part of the tutorial, I'm just going to summarize what you need to do to get MyBatis to automatically initialize when the ModelingAgency webapp starts.

Setting up a ServletContextListener

A ServletContextListener is useful when you want to do something when a java application starts up, more specifically, when a ServletContext is initalized.

In our case, we're going to use a ServletContextListener to set a MyBatis SqlSessionan application scoped varible. This will allow us to instantiate our ModelingAgencyDAO object from our TestServlet. Here's how to do it:

1) Register the listener in web.xml

Add the following code to web.xml

<listener>
   <listener-class>
  com.modelingagency.listeners.CustomServletContextListener
   </listener-class>
 </listener>

2) Create the Listener class

Create the class CustomServletContextListener.java under the com.modelingagency.listeners package:


package com.modelingagency.listeners;
 
import java.io.Reader;
import javax.servlet.ServletContext;
import javax.servlet.ServletContextEvent;
import javax.servlet.ServletContextListener;
 
import org.apache.ibatis.io.Resources;
import org.apache.ibatis.session.SqlSessionFactory;
import org.apache.ibatis.session.SqlSessionFactoryBuilder;
 
public class CustomServletContextListener implements ServletContextListener
{
 public void contextInitialized(ServletContextEvent event)
 {  
  ServletContext ctx = event.getServletContext(); 
        
     String resource = "mybatis.config.xml";
     try{      
      Reader reader = Resources.getResourceAsReader(resource);     
      SqlSessionFactory sqlSessionFactory = new SqlSessionFactoryBuilder().build(reader); //this will load the default environment configured in mybatis.config.xml
      ctx.setAttribute("sqlSessionFactory", sqlSessionFactory); //set the sqlSessionFactory as an application scoped variable
     }
     catch(Exception e){
      System.out.println("FATAL ERROR: myBatis could not be initialized");
      System.exit(1);
     }    
 }
 
 @Override
 public void contextDestroyed(ServletContextEvent event){
   //nothing to do here right now
 }
}

If everything went well so far, you should be able to run the application again. Going to http://localhost:8080/ModelingAgency/test.do however will show the same things as before. So we need to finalize our interface.

Part 11: Finalizing the Interface

Part 9: Creating the DAO Layer

noreply@blogger.com (IdleWorx) — Fri, 04 Feb 2011 00:26:00 +0000

Now that both our Java Data Model and our Database Model are connected through a MyBatis mapper file, we will add a Data Access Object class so we can abstract the calling of SQL statements, and keep our servlet clean of database related code.

I know it's not a 'pure' implementation of the DAO pattern however it serves the main purpose of decoupling servlet code from database related code.

If you want to see a better way to integrate MyBatis and basic DAO classes, check out my other blog post MyBatis DAO Example Code Tutorial

ModelingAgencyDAO.java

ModelingAgencyDAO is going to be a Java class which encapsulates all the 'logical' database functionality we need, such as getting a list of all clients, models and bookings in our database. It will accomplish this by using the MyBatis framework.

For now, create the file ModelingAgencyDAO.java under the com.modelingagency.db package, with the following content:


package com.modelingagency.db;

import java.util.ArrayList;

import org.apache.ibatis.exceptions.PersistenceException;
import org.apache.ibatis.session.SqlSession;
import org.apache.ibatis.session.SqlSessionFactory;
import org.junit.Test;

import com.modelingagency.objects.Booking;
import com.modelingagency.objects.Client;
import com.modelingagency.objects.Model;

public class ModelingAgencyDAO {

 private SqlSessionFactory sf;
 
 //constructor will receive a myBatis sessionFactory object
 public ModelingAgencyDAO(SqlSessionFactory containerSessionFactory) {
  if(containerSessionFactory==null)
   System.err.println("Error: could not load myBatis sessionFactory");  
  sf = containerSessionFactory;
 }
   
 public ArrayList<Client> getClients() throws PersistenceException{
    
  SqlSession session = sf.openSession();
  try
  {   
   ArrayList<Client> clients = (ArrayList<Client>)session.selectList("com.modelingagency.objects.SimpleMappers.allClients");    
   return clients;  
  }
  finally
  {
   session.close();
  }
  
 }
  
 public ArrayList<Model> getModels() throws PersistenceException{
    
  SqlSession session = sf.openSession();
  try
  {   
   ArrayList<Model> models = (ArrayList<Model>)session.selectList("com.modelingagency.objects.SimpleMappers.allModels");    
   return models;
  }
  finally
  {
   session.close();
  }
  
 }
 
 @Test
 public ArrayList<Booking> getBookings() throws PersistenceException{
    
  SqlSession session = sf.openSession();
  try
  {   
   ArrayList<Booking> bookings = (ArrayList<Booking>)session.selectList("com.modelingagency.objects.SimpleMappers.allBookings");    
   return bookings;   
  }
  finally
  {
   session.close();
  }
  
 }
 
}

You will notice the methods in this DAO class are very similar to the ones we defined in the MyBatisTest class in Part 8. It's a good idea to have a test case setup for your DAO classes.

Now in order to use the DAO from a servlet, all you have to do is create a new object and pass in a MyBatis SqlSessionFactory through the constructor.

Let's modify our TestServlet so we can make use of our DAO class to retreive a list of all clients, a list of all models, and a list of all bookings. Your TestServlet.java class should now look like this:


package com.modelingagency.servlets;

import java.io.IOException;
import java.util.ArrayList;

import javax.servlet.RequestDispatcher;
import javax.servlet.ServletContext;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;

import org.apache.ibatis.exceptions.PersistenceException;
import org.apache.ibatis.session.SqlSessionFactory;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import com.modelingagency.db.ModelingAgencyDAO;
import com.modelingagency.objects.*;

public class TestServlet  extends HttpServlet{
 
 private static Logger log = LoggerFactory.getLogger(TestServlet.class);
 
 protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException 
 {
  HttpSession session = request.getSession();   
  ServletContext sc = getServletContext();
  
  SqlSessionFactory sf = (SqlSessionFactory)getServletContext().getAttribute("sqlSessionFactory");
  ModelingAgencyDAO dao = new ModelingAgencyDAO(sf);
  
  try
  {
   ArrayList<Client> clients = dao.getClients();    
   ArrayList<Model> models = dao.getModels();    
   ArrayList<Booking> bookings = dao.getBookings();    
   
   request.setAttribute("all_clients", clients); 
   request.setAttribute("all_models", models);
   request.setAttribute("all_bookings", bookings);
       
  }
  catch(PersistenceException p)
  {
   p.printStackTrace();  
  }
  finally
  {
   request.setAttribute("message","Welcome to the modeling agency MyBatis tutorial");
   log.info("The message attribute has been set");
  } 
                
  RequestDispatcher view = request.getRequestDispatcher("index.jsp");
  view.forward(request, response);
 }
 
 protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
  doPost(request,response);
 }
 
}

But before you can run the web application, you'll need to make sure that MyBatis has been initalized and available to the ModelingAgency app.

Part 10: Initializing MyBatis on application startup

Part 8: Testing MyBatis with jUnit

noreply@blogger.com (IdleWorx) — Fri, 04 Feb 2011 00:24:00 +0000

To be certain that the MyBatis configuration and Mapper files you setup in Part 7 are working properly, let's create a jUnit test to make sure.

First, you will need to add the jUnit library to your Eclipse project:

Right Click on the ModelingAgency project in Project Explorer
Go to Properties -> Java Build Path -> Libraries Tab -> Add Library (button)
Select jUnit4 and click Finish

Second, create a new package under your webapp called com.modelingagency.tests.
We will keep our jUnit test classes in here.

Third, add the file MyBatisTest.java to the com.modelingagency.tests package:

package com.modelingagency.tests;

import static org.junit.Assert.*;

import java.io.Reader;
import java.util.ArrayList;

import org.apache.ibatis.io.Resources;
import org.apache.ibatis.session.SqlSession;
import org.apache.ibatis.session.SqlSessionFactory;
import org.apache.ibatis.session.SqlSessionFactoryBuilder;
import org.junit.AfterClass;
import org.junit.BeforeClass;
import org.junit.Test;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import com.modelingagency.objects.Booking;
import com.modelingagency.objects.Client;
import com.modelingagency.objects.Model;

public class MyBatisTest {
 
 private static Logger log = LoggerFactory.getLogger(MyBatisTest.class);
 private static SqlSessionFactory sf;
 
  
 @BeforeClass
 public static void setUp() throws Exception {
  log.info("starting up myBatis tests");
  String resource = "mybatis.config.xml";
  Reader reader = Resources.getResourceAsReader(resource);  
  sf = new SqlSessionFactoryBuilder().build(reader,"testing"); //we're using the 

'testing' 
 }
 
 @AfterClass
 public static void tearDown() throws Exception {  
  log.info("closing down myBatis tests");
 }
 
 @Test
 public void getClients(){
    
  SqlSession session = sf.openSession();
  try
  {   
   ArrayList client = (ArrayList)session.selectList

("com.modelingagency.objects.SimpleMappers.allClients");    
   assertNotNull("Client list is null",client);   
  }
  finally
  {
   session.close();
  }
  
 }
  
 @Test
 public void getModels(){
    
  SqlSession session = sf.openSession();
  try
  {   
   ArrayList model = (ArrayList)session.selectList

("com.modelingagency.objects.SimpleMappers.allModels");    
   assertNotNull("Model list is null",model);
  }
  finally
  {
   session.close();
  }
  
 }
 
 @Test
 public void getBookings(){
    
  SqlSession session = sf.openSession();
  try
  {   
   ArrayList bookings = (ArrayList)session.selectList

("com.modelingagency.objects.SimpleMappers.allBookings");    
   assertNotNull("Booking is null",bookings);   
  }
  finally
  {
   session.close();
  }
  
 }
 
 
}

I'm not going into detail into what the MyBatisTest class does, but it should be self explanatory. It loads the MyBatis configuration we have defined, using the 'test' environment, and then runs some test methods against the queries we have defined in the SimpleMappers.xml mapper file.

To run the test, right click on the MyBatisTest.java, and select
Run As -> jUnit Test

If everything went well, you should see the following output in the jUnit window:

Now you're ready to move on.

Part 9: Creating the DAO Layer

Part 7: Configuring MyBatis

noreply@blogger.com (IdleWorx) — Fri, 04 Feb 2011 00:18:00 +0000

If you have followed the first parts of this tutorial Part 1 to Part 6 you should now have a very simple MySQL database setup and the java layer ready for the ModelingAgency web application.

Now I'm going to show you how to integrate your database and java model layer with MyBatis 3

Setting up the MyBatis configuration file
Configuring the mapper file

The MyBatis configuration file

First it's time to add the main MyBatis configuration file to your web application. You can call this file anything you want, but let's use mybatis.config.xml for now.

This file will hold all the MyBatis configuration info and references to all the other sql mapping files we will define.

Create the following file /src/mybatis.config.xml:


<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE configuration PUBLIC "-//mybatis.org//DTD Config 3.0//EN" 
 "http://mybatis.org/dtd/mybatis-3-config.dtd">
<!-- Created by 2011: http://blog.idleworx.com http://www.idleworx.com -->
<configuration>
 
 <properties resource="dbcp.properties"/>
  
 <settings>
  <setting name="useGeneratedKeys" value="true"/>
 </settings>
    
 <typeAliases>  
  <typeAlias alias="Client" type="com.modelingagency.objects.Client"/>
  <typeAlias alias="Model" type="com.modelingagency.objects.Model"/>
  <typeAlias alias="Booking" type="com.modelingagency.objects.Booking"/>  
 </typeAliases>
  
 <environments default="development">
  
  <environment id="development">
   <transactionManager type="JDBC"/>
   <dataSource type="JNDI">
    <property name="initial_context" value="java:comp/env"/>
    <property name="data_source" value="/jdbc/mydb"/> 
   </dataSource>
  </environment>
  
  <environment id="testing">
   <transactionManager type="JDBC"/>
   <dataSource type="POOLED">
    <property name="driver" value="${db.driver}"/>
    <property name="url" value="${db.url}"/>
    <property name="username" value="${db.user}"/>
    <property name="password" value="${db.pass}"/>
   </dataSource>
  </environment>
    
 </environments>

 <mappers>
  <mapper resource="com/modelingagency/objects/SimpleMappers.xml"/>
 </mappers>

</configuration>

Also, create the following file /src/dbcp.properties:

db.url=jdbc:mysql://localhost/modeling_agency
db.driver=com.mysql.jdbc.Driver
db.user=test
db.pass=test

Notes

You'll notice we have a 'testing' environment setup. We'll use that for testing our app with jUnit.
Using the useGeneratedKeys property will allow MyBatis to make use of the autogenerated row id values from the database, as we defined in the SQL in Part 2: client_id INTEGER NOT NULL AUTO_INCREMENT
typeAliases will simplify things for you, by helping MyBatis identify fully qualified java class names. This way you won't have to type the fully qualified names of your objects in MyBatis mapper files
In a typical application there are usually many SQL mapper files, however for our simple application we only really need one, the SimpleMappers.xml file
The mybatis.config.xml file should go under /src/mybatis.config.xml (this is because the file should be on the application's classpath)

Tip:If you're wondering how to setup multiple environments in MyBatis see my other blog posting: Initializing MyBatis Using a ServletContextListener

Configuring the Mapper file

MyBatis SQL mappers allow us to map our java data model to our database model.

The mapper file holds all the sql statments you need to interact with your database, so it's pretty important, and it also happens to be a critical element of the MyBatis framework, which will simplify your life a lot, once you pass the learning curve :)

The mapper file also stores definitions of objects that will be used to retrieve data from the database. By doing this MyBatis abstracts most of the hard work of writing tons of sql statements, and most importantly jdbc code.

Since we've configured this file's location (com/modelingagency/objects/SimpleMappers.xml) in the mybatis.config.xml file above, MyBatis now knows to load this resource whenever it is initialized.

The main functionality we're going to need now in the SimpleMapper.xml file is this:

1) Getting a list of clients
2) Getting a list of models
3) Getting a list of all bookings

Create the following file: /src/com/modelingagency/objects/SimpleMappers.xml:


<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE mapper PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN" "http://mybatis.org/dtd/mybatis-3-mapper.dtd">
<!-- Created by: http://blog.idleworx.com, http://www.idleworx.com -->
<mapper namespace="com.modelingagency.objects.SimpleMappers">
 
 <resultMap id="clientResultMap" type="Client">
  <id property="id" column="client_id" />  
  <result property="name" column="client_name" />  
 </resultMap>
 
 <resultMap id="modelResultMap" type="Model">
  <id property="id" column="model_id" />  
  <result property="name" column="model_name" /> 
 </resultMap>
  
 <resultMap id="bookingResultMap" type="Booking">
  <id property="id" column="booking_id" />  
  <result property="time" column="booking_time" />    
  <result property="location" column="booking_location" />
  <association property="client" column="booking_client_id" javaType="Client" resultMap="clientResultMap"/>
  <association property="model" column="booking_model_id" javaType="Model" resultMap="modelResultMap"/>
 </resultMap> 
  
 <select id="allClients" parameterType="string" resultMap="clientResultMap">
  select  * from client order by 1  
 </select>
 
 <select id="allModels" parameterType="string" resultMap="modelResultMap">
  select  * from model order by 1
 </select>
 
 <select id="allBookings" parameterType="string" resultMap="bookingResultMap">
  select * from client, model, booking
  where booking_client_id = client_id and booking_model_id = model_id
  order by 1
 </select>
 
</mapper>

Notes

The name of each query is identified by the 'id' parameter
parameterType indicates what type of parameter you will pass into the sql statement (for simple queries there is only one parameter or none), for queries which require multiple parameters you can use the 'hashmap' parameterType to pass in name value pairs. In our case the parameter is not actually used.
By defining result maps for each of our objects, MyBatis knows how to automatically map a column from the database table directly to the javabean property name (in our case the Client,Model and Booking classes)
If you don't use Result Maps in your mapper files, you can use the resultType attribute instead which specifies the Java Bean class name we want to map, and which is defined in mybatis.config.xml. Normally you have to put a fully qualified class name here like com.modelingagency.objects.Model, but because if you defined the typeAliases element in the mybatis.config.xml you can just use the short name
The allBookings query makes use of MyBatis associations. Associations are what MyBatis uses to retrieve one-to-many relationships from your database into java objects. To learn more about this read: Understanding MyBatis' Multiple Table Joins

To make sure the MyBatis configuration and mapper files are all setup correctly, before we create our DAO layer and use it from our Servlet, we need to do a quick test.

Part 8: Testing MyBatis with jUnit

Part 6: The Java POJO model

noreply@blogger.com (IdleWorx) — Fri, 04 Feb 2011 00:13:00 +0000

If you've been following IdleWorx's Tutorial on Building a Web Application with MyBatis,MySQL,Tomcat and Eclipse , you should be now ready to setup the database layer of the ModelingAgency webapp.

In order to be able to interact with the database we setup in Part 2 we will create a simple java model made of POJOs (simple JavaBeans that is).

These Plain Old Java Objects (POJOs) will serve as the model, or in other words, a way to transfer data between the database and the ModelingAgency webapp.

At this point we're not concerned about how we'll actually retrieve the data from the database into our model classes, that is where MyBatis will come in later on and take care of that for us.

If you remember our database layout from Part 2, we have 3 business objects in our application that we need to model:

Client
Model
Booking

So let's add the following classes to the com.modelingagency.objects package:

Client.java


package com.modelingagency.objects;

/**
 * Copyright 2011: http://blog.idleworx.com, http://www.idleworx.com   
 */
public class Client {
 private Integer id;
 private String name;
 
 public Client(){}
 
 public Integer getId() {
  return id;
 }
 public void setId(Integer id) {
  this.id = id;
 }
 public String getName() {
  return name;
 }
 public void setName(String name) {
  this.name = name;
 }
 
 @Override
 public String toString() {
  return "[client] " + "(" + id + ")" + " " + name;
 }
}

Model.java

package com.modelingagency.objects;

/**
 * Copyright 2011: http://blog.idleworx.com, http://www.idleworx.com   
 */
public class Model {

 private Integer id;
 private String name;
 
 public Model() {}
 
 public Integer getId() {
  return id;
 }
 public void setId(Integer id) {
  this.id = id;
 }
 public String getName() {
  return name;
 }
 public void setName(String name) {
  this.name = name;
 }
 
 @Override
 public String toString() {
  return "[model] " + "(" + id + ")" + " " + name;
 }
}

Booking.java

package com.modelingagency.objects;

import java.sql.Timestamp;
import java.util.Date;

/**
 * Copyright 2011: http://blog.idleworx.com, http://www.idleworx.com   
 */
public class Booking {

 private Integer id;
 private Client client;
 private Model model;
 private Timestamp time;
 private String location;
 
 public Booking(){}
 
 public Integer getId() {
  return id;
 }
 public void setId(Integer id) {
  this.id = id;
 }
 public Client getClient() {
  return client;
 }
 public void setClient(Client client) {
  this.client = client;
 }
 public Model getModel() {
  return model;
 }
 public void setModel(Model model) {
  this.model = model;
 }
 public Timestamp getTime() {
  return time;
 }
 public void setTime(Timestamp time) {
  this.time = time;
 }
 public String getLocation() {
  return location;
 }
 public void setLocation(String location) {
  this.location = location;
 }
 
 @Override
 public String toString() {
  return "[booking] " + "(" + id + ")" + " where: " + location + " when: " + new Date(time.getTime());
 }
 
}

Note that the Booking model class doesn't have getters for the booking_client_id and booking_model_id fields which are part of the booking table.

We're not going to model each field directly into our java beans, instead we're going to let MyBatis retrieve the actual Client and Model objects whenever a Booking object is returned from the database. And we're going to accomplish this through the use of MyBatis Result Maps, as you will shortly see.

Before we do that however, we need to setup MyBatis.

Part 7: Configuring MyBatis

Part 5: Setting up Logging

noreply@blogger.com (IdleWorx) — Fri, 04 Feb 2011 00:10:00 +0000

If you've followed Part 4 of this tutorial, we're about to setup logging for the ModelingAgency webapp in order to learn how to use MySQL, MyBatis and Tomcat togather.

If you're familiar with Log4J you can use that library. However for the ModelingAgency webapp we're going to setup the Logback library, which is the new Log4J.

You have probably already downloaded the Logback jars in Part 1. If not, you can download all of the jars required for the ModelingAgency app here.

Configuring Logback

Configuring Logback with a Java web application is relatively simple. Once you have the required jars in /WEB-INF/lib, create a file called logback.xml and put it under your project's /src folder.

Here is the logback.xml file we we will use for this project:

<?xml version="1.0" encoding="UTF-8"?>
<configuration scan="true" debug="false" > <!-- set debug to true to dump logback status info when library is loaded -->
 
  <contextName>ModelingAgency</contextName>
  
  <!-- APPENDERS -->
  
  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">    
    <!-- encoders are assigned the type ch.qos.logback.classic.encoder.PatternLayoutEncoder by default -->
    <encoder> 
      <pattern>[%contextName] %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
    </encoder>
  </appender>
  
  <appender name="SQLDUMP" class="ch.qos.logback.core.FileAppender">
    <file>sql.log</file>
    <append>false</append>
    <encoder>
      <!-- <pattern>%date %level [%thread] %logger{10} [%file:%line] %msg%n</pattern> -->
      <pattern>[%contextName] [%c] [%d{dd MMM yyyy - hh:mm:ss}] %5p - %m %n</pattern>      
    </encoder>
  </appender>
  
  <appender name="FILE" class="ch.qos.logback.core.FileAppender">
    <file>application.log</file>
    <encoder>
      <!-- <pattern>%date %level [%thread] %logger{10} [%file:%line] %msg%n</pattern> -->
      <pattern>[%contextName] [%c] [%d{dd MMM yyyy - hh:mm:ss}] %5p - %m %n</pattern>      
    </encoder>
  </appender>
  
  <appender name="OUT" class="ch.qos.logback.core.ConsoleAppender">    
    <encoder>
    <pattern>[%contextName] [%c] [%d{dd MMM yyyy - hh:mm:ss}] %5p - %m %n</pattern>        
    </encoder>
  </appender>
  
   <appender name="OUT_SIMPLE" class="ch.qos.logback.core.ConsoleAppender">    
    <encoder>
    <pattern>[%c] %5p - %m %n</pattern>        
    </encoder>
  </appender>
        
  <!-- LOGGERS -->  
    
  <!--  loggers inherit the appender from their parent ( the root logger ) -->
  <logger name="java.sql" level="DEBUG" additivity="false"> 
   <appender-ref ref="SQLDUMP" /> 
  </logger>
   
  <logger name="org.apache.ibatis.datasource" level="WARN"/> <!-- removes datasoure debug info from logs --> 
       
  <root level="debug"> <!-- can set level to OFF-->
    <appender-ref ref="OUT" />
  </root>
  
</configuration>

Adding logging to TestServlet

To make sure logback works properly, let's add some simple logging code to the TestServlet we created in Part 4

Add the following logging code to the TestServlet.java file:


package com.modelingagency.servlets;

import java.io.IOException;

import javax.servlet.RequestDispatcher;
import javax.servlet.ServletContext;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

public class TestServlet  extends HttpServlet{
 
 private static Logger log = LoggerFactory.getLogger(TestServlet.class);
 
 protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException 
 {
  HttpSession session = request.getSession();   
  ServletContext sc = getServletContext();
  
  request.setAttribute("message","This is a message from the TestServlet. It works!");
  log.info("The message attribute has been set");
             
  RequestDispatcher view = request.getRequestDispatcher("index.jsp");
  view.forward(request, response); 
 }
 
 protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
  doPost(request,response);
 }
 
}

Restart your project now, by right clicking on the index.jsp file and selecting Run on server.

If you access the TestServlet's url on your local server now, http://localhost:8080/ModelingAgency/test.do you should get an output like this:

[ModelingAgency] [com.modelingagency.servlets.TestServlet] [03 Feb 2011 - 10:38:26] INFO - The message attribute has been set

If you got this far, it means you have setup Logback logging for the ModelingAgency webapp.

Now the fun part,

Part 6: Creating the java pojo model

Part 4: Creating a Test Servlet

noreply@blogger.com (IdleWorx) — Thu, 03 Feb 2011 23:33:00 +0000

If you've been following Part 3 of this tutorial, you are on your way to creating a Java Web Application using MyBatis,MySQL and Tomcat in Eclipse.

Creating a test Servlet

So far we have created the MySQL database for the ModelingAgency application in Part 2 and we have setup the ModelingAgency project in Eclipse in Part 4, but we haven't used any Servlets yet.

Even if you're not familiar with the MVC model (which you should be if you're reading this tutorial), if you're using plain old Servlets these days it's typical to use them as a Controller.

In other words as a java classes responsible for reading request parameters, performing business logic, and passing on the necessary data to a view (eg. a jsp file) in the form of request parameters.

If all this sounds confusing to you, and you're considering learning Java Web Application Development, I would strongly recommend grabbing a copy of Head 1st Servlets.

To take our application to the next level, and help you understand servlets better, we're going to create a test servlet.

The Servlet

Create a new java class called TestServlet.java under the com.modelingagency.servlets package:


package com.modelingagency.servlets;

import java.io.IOException;

import javax.servlet.RequestDispatcher;
import javax.servlet.ServletContext;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;

public class TestServlet  extends HttpServlet{

 protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException 
 {
  HttpSession session = request.getSession();   
  ServletContext sc = getServletContext();
  
  request.setAttribute("message","This is a message from the TestServlet. It works!"); 
             
  RequestDispatcher view = request.getRequestDispatcher("index.jsp");
  view.forward(request, response); 
 }
 
 protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
  doPost(request,response);
 }
 
}

We're going to use this servlet to display a simple text string to make sure things are working, before moving forward.

Don't forget to configure your servlet in the deployment descriptor, so the webapp knows how to 'serve' it.

Your web.xml file should now look like this:


<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
 
 <display-name>ModelingAgency</display-name>
 
 <welcome-file-list>
  <welcome-file>index.html</welcome-file>
  <welcome-file>index.htm</welcome-file>
  <welcome-file>index.jsp</welcome-file>
  <welcome-file>default.html</welcome-file>
  <welcome-file>default.htm</welcome-file>
  <welcome-file>default.jsp</welcome-file>
 </welcome-file-list>
 
 <resource-ref>
      <description>DB Connection</description>
      <res-ref-name>jdbc/mydb</res-ref-name>
      <res-type>javax.sql.DataSource</res-type>
      <res-auth>Container</res-auth>
  </resource-ref>
  
  <servlet>
  <servlet-name>test</servlet-name>
  <servlet-class>com.modelingagency.servlets.TestServlet</servlet-class>  
 </servlet>
 
 <servlet-mapping>
  <servlet-name>test</servlet-name>
  <url-pattern>/test.do</url-pattern>
 </servlet-mapping> 
  
</web-app>

index.jsp

Before we re-start our server and run our application again to see if all this works, don't forget to modify index.jsp so it will display the attribute you set in the servlet

The index.jsp file should now look like this:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
 <title>Modeling Agency Index</title>
</head>
<body>

Things are looking good.
<br>
${requestScope.message}

</body>
</html>

If you run the application again, and go the the servlet url that we setup in the deployment descriptor, http://localhost:8080/ModelingAgency/test.do you should see the output:

Things are looking good.
This is a message from the TestServlet. It works!

What next

If you got so far, you are well on your way to setting up a web application using MySQL,MyBatis and Tomcat using Eclipse. Before we get to the MyBatis part, lets see how to setup logging for the ModelingAgency web application (or any java web application for that matter).

Part 5: Setting up Logging

Part 3: Creating the ModelingAgency project in Eclipse

noreply@blogger.com (IdleWorx) — Thu, 03 Feb 2011 23:29:00 +0000

If you've followed the previous tutorials Part 1 and Part 2 you should now be ready to create a simple java web application called ModelingAgency in Eclipse, in order to learn how MySQL, MyBatis and Tomcat work together.

Creating a new project

Open up Eclipse. Under the Project Explorer tab right click and select New -> Project
Select the Dynamic Web Project and click Next
Enter the project properties. For this project we will use the 2.4 Dynamic Web Module version, and the Tomcat 6.0 Runtime (which you may have to configure manually)
Click Finish. You should now have a project that looks like this:

Setup the java packages

To organize our code a little, let's create the following packages under our /src directory

com.modelingagency.db
com.modelingagency.listeners
com.modelingagency.objects
com.modelingagency.servlets

Click on Java Resources: src -> New -> Package and create the packages above

External jar files

Remember all those jar files you downloaded in Part 1 (the mybatis jar, standard.jar,jstl.jar,etc). Now it's time to make them available to the webapp by placing them under the /WEB-INF/lib folder.

You can download all the jar files you need to place in this folder here.

Configuring the database connection

In order to connect to the database we have setup in Part 2, we have to add a context.xml file under the /META-INF folder.

There are other was to setup a database connection from Tomcat, but placing it in /META-INF/context.xml allows each webapp to be bundled with its database configuration, and is easier to manage in my experience.

context.xml

Create the following file and place it under /META-INF/context.xml

<?xml version="1.0" encoding="UTF-8"?>
<Context docBase="ModelingAgency" path="/ModelingAgency" reloadable="true" >
                        
      <!-- http://commons.apache.org/dbcp/configuration.html -->      
      <Resource name="jdbc/mydb" auth="Container" type="javax.sql.DataSource"
               maxActive="100" 
               maxIdle="5" 
               maxWait="10000"
               
               username="test" password="test" 
               driverClassName="com.mysql.jdbc.Driver"
               url="jdbc:mysql://localhost/modeling_agency" 
               
               removeAbandoned="true"
               removeAbandonedTimeout="10"
      logAbandoned="true"
      validationQuery="SELECT 1" /> 
             
</Context>

Note:The docBase attribute and path map to the same name as your Eclipse project name. Also, If you have a different username or password that you created in Part 2, other than 'test' make sure to use it instead.

web.xml

The deployment descriptor, web.xml, is the most important piece in any Java webapp (but I'm sure you know that already).

In order to make the database connection we defined in context.xml known to your webapp, you should also add a resource entry in web.xml.

Edit your web.xml file so it looks like this:


<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
 
 <display-name>ModelingAgency</display-name>
 
 <welcome-file-list>
  <welcome-file>index.html</welcome-file>
  <welcome-file>index.htm</welcome-file>
  <welcome-file>index.jsp</welcome-file>
  <welcome-file>default.html</welcome-file>
  <welcome-file>default.htm</welcome-file>
  <welcome-file>default.jsp</welcome-file>
 </welcome-file-list>
 
 <resource-ref>
      <description>DB Connection</description>
      <res-ref-name>jdbc/mydb</res-ref-name>
      <res-type>javax.sql.DataSource</res-type>
      <res-auth>Container</res-auth>
  </resource-ref>
  
</web-app>

Starting the app

Just to make sure we're on the right track and things are working fine, let's create an index page and start our server:

First, create the following index.jsp file under the /WebContent folder.

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
 <title>Modeling Agency Index</title>
</head>
<body>

Things are looking good.

</body>
</html>

Now to start the ModelingAgency web application on a tomcat server,
right click the index.jsp file, select Run As -> Run on server

Make sure the Server's host name is localhost and the Server runtime environment is associated with your Tomcat 6.0 installation. Click Finish.

If all is well, the server should be running in Eclipse and you will see this:

Your project layout at this point should be looking like this:

Now you are ready to move on to

Part 4: Creating a Test Servlet

Part 2: The ModelingAgency Application

noreply@blogger.com (IdleWorx) — Thu, 03 Feb 2011 23:22:00 +0000

Part 1: The Setup

To see how Tomcat, MyBatis and MySQL work together, we're going to create a small Java web application in Eclipse called ModelingAgency.

The Modeling Agency web app does the following:

It lets a photographer (a client object) book a model (a model object) for a photography shoot at a particular place and time (a booking object).

The Interface

Our interface is going to look something like this when we're done:

You can think of the application as an appointment organizer for photographers. I'm sure this will make more sense when you see the actual tables.

The Tables

The client table

The model table

The booking table

The SQL

Here is the sql to create the MySQL database for our ModelingAgency, and populate with the data above:


create database modeling_agency;
use modeling_agency;
grant all on modeling_agency.* to 'test'@'localhost' identified by 'test' #feel free to rename this to whatever you want

CREATE TABLE modeling_agency.client
(
  client_id INTEGER NOT NULL AUTO_INCREMENT,
  client_name VARCHAR(45) NOT NULL DEFAULT '',
  PRIMARY KEY(client_id)
);

CREATE TABLE modeling_agency.model
(
  model_id INTEGER NOT NULL AUTO_INCREMENT,
  model_name VARCHAR(45) NOT NULL DEFAULT '',
  PRIMARY KEY(model_id)
);

CREATE TABLE modeling_agency.booking
(
 booking_id INTEGER NOT NULL AUTO_INCREMENT,
 booking_client_id INTEGER,
 booking_model_id INTEGER,
 booking_time TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
 booking_location VARCHAR(100) NOT NULL DEFAULT '##NO LOCATION SELECTED##', 
 PRIMARY KEY (booking_id),
 CONSTRAINT `FK_booking_client` FOREIGN KEY (booking_client_id)
  REFERENCES modeling_agency.client (client_id),
 CONSTRAINT `FK_booking_model` FOREIGN KEY (booking_model_id)
  REFERENCES modeling_agency.model (model_id) 
);

insert into modeling_agency.client (client_name) values ("Michelangelo");
insert into modeling_agency.client (client_name) values ("Rafaelo");
insert into modeling_agency.client (client_name) values ("Leonardo");
insert into modeling_agency.client (client_name) values ("Donatello");

insert into modeling_agency.model (model_name) values ("Monalisa");
insert into modeling_agency.model (model_name) values ("Plain Jane");
insert into modeling_agency.model (model_name) values ("Funky Susan");
insert into modeling_agency.model (model_name) values ("Mary");

insert into booking (booking_client_id,booking_model_id,booking_location) values ((select client_id from client where client_name = 'Michelangelo'),(select model_id from model where model_name = 'Monalisa'),"Somewhere in Italy");
insert into booking (booking_client_id,booking_model_id,booking_location) values ((select client_id from client where client_name = 'Leonardo'),(select model_id from model where model_name = 'Plain Jane'),"Near the river");
insert into booking (booking_client_id,booking_model_id,booking_location) values ((select client_id from client where client_name = 'Donatello'),(select model_id from model where model_name = 'Mary'),"On the beach");

Note:Keep in mind the mysql test user we setup in the SQL above, as it will be the same you will use when you configure how Tomcat will work with your database

Now we're ready to setup the ModelingAgency project as a DynamicWeb project in eclipse.

Part 3: Creating the ModelingAgency project in Eclipse

Part 1: The Setup

noreply@blogger.com (IdleWorx) — Thu, 03 Feb 2011 23:12:00 +0000

Installing Eclipse

Chances are you already have Eclipse installed by now. Just make sure you have the Java EE version of Eclipse or at least the Web Tools Project installed.

For this tutorial I used Java EE Eclipse (Helios) SR1

If you are installing eclipse for the first time use this link: Download Java EE Eclipse Helios

Installing Tomcat 6

Go to: http://tomcat.apache.org/index.html and download the appropriate Tomcat distribution you need.
Tomcat 5.5 or 6 should both work with this tutorial.

For this tutorial I used Tomcat 6.0.29.
You can download this version here.

Installing MySQL

It's assumed at this point that you have a working MySQL database instance setup already. Ideally MySQL version 5.1 or above. If you already have the MySQL driver setup with your Tomcat server you can skip this section, if not, read on.

To use MySQL from your Java web application you will first need to download the MySQL Java Driver, also known as the JDBC Driver for MySQL (Connector/J)

1) Go to: http://www.mysql.com/downloads/connector/j/ and download JDBC Driver for MySQL (Connector/J) zip archive.

2) Extract the driver .jar file into your Tomcat installation:

CATALINA_HOME/common/lib folder (Tomcat 5) or CATALINA_HOME/lib (Tomcat 6)

For this tutorial I used the mysql-connector-java-5.1.13-bin.jar but any version above that should also work.

Tip: Avoid putting your MySQL driver jar under WEB-INF/lib as it may cause issues down the road when you want to use mysql with other webapps. You'll probably forget about it and it will cause class path conflicts. So the best bet is to leave it in the shared libraries folder of your Tomcat server. That way all webapps will have access to it.

Jar libraries for this tutorial

To make things quicker for you, you can download all the jar files you will need for this tutorial here. Once we setup the eclipse project in Part 3: Creating the ModelingAgency project in Eclipse, you can just extract all the jars here under the /WEB-INF/lib folder

However if you want to do it manually follow the rest of this tutorial.

Installing MyBatis

Go to: http://www.mybatis.org/java.html.
Click on Download the Persistence Framework and download the zipped archive mybatis-3.0.4-bundle.zip (direct link)

Once we have setup the ModelingAgency web application in Eclipse in Part 3: Creating the ModelingAgency project in Eclipse, you will extract the mybatis-3.0.4.jar to the /WEB-INF/lib folder of your application. Don't worry, I'll remind you about that later.

Tip:Before you go any futher, I would strongly suggest you go through the very well written MyBatis documentation before you continue with this tutorial (Especially if you've never used iBatis or MyBatis). It will take about 30 minutes to skim through it, and will give you an excellent foundation of the basics.

download the documentation

Installing JSTL/EL

One last thing. In our project we are going to use the JSTL library to make things easier a bit. With a combination of the JSP Expression Language and the JSTL library you should almost never need to write 'java' code inside your jsp files anymore. To learn more about this read The Evolution of Servlets and JSP.

To make use of Java's JSTL library and the JSP Expression Language in our project, you will need to download jstl.jar and standard.jar from the Jakarta Taglibs Project extract them to the /WEB-INF/lib folder of your application. Don't worry, I'll remind you about this later as well..

These jars can be found here:

Go to: http://jakarta.apache.org/site/downloads/downloads_taglibs-standard.cgi and download the 1.1.2.zip binary.
For direct link click here.

Installing LogBack (the new Log4j)

If you want to be able to log things to the console for this project you should also install LogBack, the successor of Log4J

Download logback-0.9.28.zip. You will need to extract the following files to the /WEB-INF/lib folder of the webapp we will setup in Part 3: Creating the ModelingAgency project in Eclipse.

logback-core-0.9.28.jar
logback-classic-0.9.28.jar

There is also an additional depndency which logback needs, which you can download from here: slf4j-api-1.6.1.jar

If you feel like everything here is setup correctly, let's move on to

Part 2: The ModelingAgency Application

Problems with Foundation Rails 2 by Eldon Almeda

noreply@blogger.com (IdleWorx) — Tue, 01 Feb 2011 22:21:00 +0000

If you've been going through the Foundation Rails 2 book and ran into some problems with the sample rails apps, you're not alone. Here's some common errors I ran into and some solutions I found digging around the web.

If you have any version other than rails 2.1.0 installed, I would suggest uninstalling rails and all it's dependencies and reinstalling this version, as rails 2.1.0 seems to work best with the exercises in this book. The solutions described here apply to ruby 1.9.1 [1.9.1p430] and rails 2.1.0

If however, you do have a version of Rails > 2.1.0 [not reccomended], and you're trying to get it to work, try updating the config/environment.rb rails version to whatever of Rails you are using:

RAILS_GEM_VERSION = 'x.x.x' unless defined? RAILS_GEM_VERSION
but in this case, some of the solutions in this post may not work for you.

Problems

PROBLEM: Problems related to sqlite or sqlite3.dll.

Possible solution:
- First, make sure you have installed the sqlite3-ruby library: 'gem install sqlite3-ruby'
  
  And place the sqlite.dll into ruby_installation_directory/bin folder prior to running any of the example apps
PROBLEM: You run ruby script/server and get the following

boot.rb:86:in `load_rubygems': undefined method `>=' for nil:NilClass (NoMethodError)

Possible solution:
- In confing/boot.rb, inside the load_rubygems method replace:
  unless (rubygems_version) = 'x.x.x'
  with
  unless (rubygems_version || Gem::RubyGemsVersion) >= '1.3.7' #or whatever gems version you have.
PROBLEM: You run ruby script/server and get the following

no such file to load -- test/unit/error (MissingSourceFile)

Possible solution:
- Make sure you have the test-unit library installed: 'gem install test-unit'
- You might also want to try 'gem clean'
PROBLEM: You are trying to use the
<%= error_messages_for :post %> or a similar helper

And you get the following message:

{{count}} errors prohibited this {{model}} from being saved

Possible solution:
- It seems that the i18n library version 0.5.0 might cause problems. Try uninstalling it (gem uninstall i18n -v=0.5.0) and install the 0.4.2 version (gem install i18n -v=0.4.2).
  
  If you already installed Rails 2.1.0 it might complain that another library depends on i18n version 0.5.0, so in that case re-install rails 2.1.0 and all its dependencies.
- You might also want to try 'gem clean'

My current 'gem list' command, dumps this:

actionmailer (2.1.0)
actionpack (2.1.0)
activerecord (2.1.0)
activeresource (2.1.0)
activesupport (2.1.0)
archive-tar-minitar (0.5.2)
arel (2.0.6)
builder (2.1.2)
columnize (0.3.2)
i18n (0.4.2)
ibm_db (2.5.5 mswin32)
nokogiri (1.4.4.1 x86-mingw32)
rack (1.1.0)
rails (2.1.0)
rake (0.8.7)
ruby_core_source (0.1.4)
sqlite3 (1.3.3 x86-mingw32)
sqlite3-ruby (1.3.3)
test-unit (2.1.2)
tzinfo (0.3.23)

So if you have something similar, you should hopefully be able to resolve the issues described in this post.

Friendly CSS Error Messages for Java Web Applications

noreply@blogger.com (IdleWorx) — Sun, 28 Nov 2010 17:48:00 +0000

A while ago I had discovered Richard O'Neil's article on Designing Message Boxes. I highly recommend reading the article first.

It's a great tutorial for adding a simple but really nice styles to your web application's error messages using CSS and the now ubiquitous FamFamFam Silk Icons pack.

Here is how it looks

Recently however I decided to improve upon it a little for use in my own applications. So here are the modifications I made:

Added better color/display of fonts
Added onclick dismissal/hiding of alerts using jQuery

Installation

1. Download the following images from the FamFamFam Silk Icons pack and save them in your /images folder or something similar:
- msg_ok.png
- msg_info.png
- msg_warning.png
- msg_error.png

2. Save the following CSS file as alerts.css and put it in your application's directory structure

/* Friendly CSS Error Messages
   Original idea by http://www.richardoneill.com.au/tags/web_design 
   Improved by IdleWorx @ http://blog.idleworx.com
   http://blog.idleworx.com/2010/11/friendly-css-error-messages-for-java.html
*/

.msgOK{
 color:#69A150;
 font-size:1.2em;
 font-family: 'helvetica', Georgia, arial, sans-serif;
 font-weight:bold; 
}

.msgInfo{
 color:#5C7CA0;
 font-size:1.2em;
 font-family: 'helvetica', Georgia, arial, sans-serif;
 font-weight:bold; 
}

.msgWarn{
 color:#BF9E1B;
 font-size:1.2em;
 font-family: 'helvetica', Georgia, arial, sans-serif;
 font-weight:bold; 
}

.msgError{
 color:#AD5E5C; 
 font-size:1.2em;
 font-family: 'helvetica', Georgia, arial, sans-serif;
 font-weight:bold; 
}

.msgOK{
   cursor:pointer;
   cursor:hand;
   background: #E7FFD6 url('../images/msg_ok.png') center no-repeat;
   background-position: 15px 50%;
   text-align: left;
   padding: 5px 5px 5px 45px;
   border-top: 2px solid #8CD76B;
   border-bottom: 2px solid #8CD76B;
   border:2px solid #8CD76B;
   overflow:auto;
   font-size:1.4em;
   font-family:Verdana;
}

.msgInfo{
   cursor:pointer;
   cursor:hand;
   background: #E7F3FF url('../images/msg_info.png') center no-repeat;
   background-position: 15px 50%;
   text-align: left;
   padding: 5px 5px 5px 45px;
   border-top: 2px solid #7BA6D6;
   border-bottom: 2px solid #7BA6D6;
   border:2px solid #7BA6D6;
   overflow:auto;
   font-size:1.4em;
   font-family:Verdana;
}

.msgWarn {
   cursor:pointer;
   cursor:hand;
   background: #fff6bf url('../images/msg_warning.png') center no-repeat;
   background-position: 15px 50%;
   text-align: left;
   padding: 5px 5px 5px 45px;
   border-top: 2px solid #ffd324;
   border-bottom: 2px solid #ffd324;
   border:2px solid #ffd324;
   overflow:auto;   
   font-size:1.4em;
   font-family:Verdana;
}

.msgError {
   cursor:pointer;
   cursor:hand;
   background: #FFE7E7 url('../images/msg_error.png') center no-repeat;
   background-position: 15px 50%;
   text-align: left;
   padding: 5px 5px 5px 45px;
   border-top: 2px solid #E77D7B;
   border-bottom: 2px solid #E77D7B;
   border:2px solid #E77D7B;
   overflow:auto;
   font-size:1.4em;
   font-family:Verdana;
}

3. Update the CSS file to use the location of the images you saved in step 1 (based on your applications folder structure)

4. Use the following html code anywhere you want to display these messages (client side)

 
 
  OK message
  
 
 
  Error Message
 
 
 
  Warning Message
 
 
 
  Info Message

If you did everything correctly you should now see something like this:
[image here]

For Java Web Applications

To simplify things a little if you're dealing with a Java Web Application do the following:

Extract the html code into a jsp file called alerts.jsp:

 
 
  OK message
  
 
 
  Error Message
 
 
 
  Warning Message
 
 
 
  Info Message

Include alerts.jsp into any other jsp where you need alert messages

This code however won't be too useful in a Java Web Application unless you only display the appropriate messages as needed. To do that here is an improved version of the alerts.jsp file above that only displays the appropriate messages based on request or session attributes set on the server side (eg. in a servlet). You can modify it as needed based on your setup.


 
 
  
   ${okMessage}
   
 
 
 
  
   ${errorMessage}
  
 
 
 
  
   ${warningMessage}
  
 
 
 
  
   ${infoMessage}

If you plan to use this approach don't forget to include the appropriate JSTL taglib directive:

<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>

Hiding alerts on click with jQuery

Displaying the alerts is ok, but sometimes you want to hide them once the user has seen the message. If you are using jQuery in your application here's how to hide messages (alerts,errors,info or ok messages) by clicking on them:

1. Save the following script in alerts.js

function enableClickableAlerts(){
 $(".msgOK").click(function(){
    $(this).hide();
 });
 $(".msgInfo").click(function(){
    $(this).hide();
 });
 $(".msgWarn").click(function(){
    $(this).hide();
 });
 $(".msgError").click(function(){
    $(this).hide();
 });
}

2. Add the following script tag to the header element
3. Add the following code to jQuery's ready() method (placed in a script tag inside the header element)
```
$(document).ready(function() 
     { 
   enableClickableAlerts();
   ...
  }
 ); 
```

You can also adapt the code to be more fancy, like only display each message for 3-5 seconds and then automatically hiding it. You know better what you need for your webapp.

The IdleWorx Blog

Welcome to the IdleWorx blog

The Do Not Track movement is useless

... or why privacy is your own responsibility

Goodbye Delicious, Hello Pinboard

Goodbye Delicious

Hello Pinboard

A simple birthday reminder app

How algorithms shape our world (video)

Your time is not worth that much

News Flash: Not everything in life has a dollar value

Agile Hitler is not Happy

MyBatis DAO Example Code Tutorial

Step 1 - Define the interface

Step 2 - Create the base class

Naming Convetions

Step 3 - Write the actual DAO classes

Step 4 - Defining the mybatis mapper

Errors

Wrapping it up

Hope you found this useful. Improvements or suggestions are welcome.

Creating a simple android app with 2 buttons

Two Button Application Use Case

Creating a two button app

1) Create the project

2) Create a simple layout

3) Adding onClickListeners to the buttons

Notes

First Android App Goes Live

RubyNation 2011

The IdleWorx Monster MyBatis Tutorial

Building an entire Java web application with MyBatis 3, Tomcat, MySQL and Eclipse (on Windows 7)

You will make the most of this tutorial if

Let's get started

Table of Contents

This tutorial took me a long time to write, so if you found it useful in any way, if you found errors with it or you think something is missing, please let me know and I will do my best to improve it.

Part 11: Finalizing the Interface

Congrats

This tutorial took me a long time to write, so if you found it useful in any way, if you found errors with it or you think something is missing, please let me know and I will do my best to improve it.

Part 10: Initializing MyBatis on Application Startup

Setting up a ServletContextListener

1) Register the listener in web.xml

2) Create the Listener class

Part 9: Creating the DAO Layer

ModelingAgencyDAO.java

Part 8: Testing MyBatis with jUnit

Part 7: Configuring MyBatis

The MyBatis configuration file

Notes

Configuring the Mapper file

Notes

Part 6: The Java POJO model

Part 5: Setting up Logging

Configuring Logback

Adding logging to TestServlet

Part 4: Creating a Test Servlet

Creating a test Servlet

The Servlet

index.jsp

What next

Part 3: Creating the ModelingAgency project in Eclipse

Creating a new project

Setup the java packages

External jar files

Configuring the database connection

context.xml

web.xml

Starting the app

Part 2: The ModelingAgency Application

The Interface

The Tables

The SQL

Part 1: The Setup

Installing Eclipse

Installing Tomcat 6

Installing MySQL

Jar libraries for this tutorial

Installing MyBatis

Installing JSTL/EL

Installing LogBack (the new Log4j)